GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
Descripción del creador (original en inglés)
Native mcdev through AI: retrieve, build, deploy, command discovery and offline docs.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"mcdev": {
"command": "npx",
"args": [
"-y",
"mcp-server-mcdev"
]
}
}
}Ejecuta esto en tu terminal
claude mcp add mcdev -- npx -y mcp-server-mcdevPégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"mcdev": {
"command": "npx",
"args": [
"-y",
"mcp-server-mcdev"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"mcdev": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"mcp-server-mcdev"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub JoernBerkefeld, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (2.0.0) llegó al registro hace 11 días.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Node.js en tu computadora.
En la misma categoría: GitHub, Desktop Commander, Cloudflare MCP
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
Use [Accenture SFMC DevTools](https://github.com/Accenture/sfmc-devtools) (mcdev) through AI: execute native metadata workflows, discover command syntax, troubleshoot failures, and search the bundled project wiki offline. The server runs locally through MCP stdio; native credentials stay in mcdev's storage.
Pair with [mcp-server-sfmc](https://www.npmjs.com/package/mcp-server-sfmc) for AMPscript / SSJS language validation and lookups.
Node.js ^22.22.2 || >=24.15.0 is required. This server uses the npm mcdev 10.1.1 release line; no separate global mcdev installation is required.
Registered as `io.github.JoernBerkefeld/mcp-server-mcdev` (quickstart). Registry hosts metadata only; the server runs locally via stdio.
Verify after publish:
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.JoernBerkefeld/mcp-server-mcdev"
CI publishes npm artifacts and registry metadata using GitHub OIDC (Actions doc) — see .github/workflows/npm-publish.yml. After npm publish succeeds, CI waits five minutes for npm registry propagation before publishing MCP Registry metadata.
The server exposes the 20 tools listed below. `run_mcdev_command` is the native execution route for supported noninteractive commands; reconcile_mcdev_operation releases an uncertain-operation latch only after operator reconciliation. The other 18 tools provide inspection, diagnostics and guidance. Previews are not dry runs or approval for execution. Catalog entries distinguish executable noninteractive cases from unsupported/prompt-dependent cases.
| Tool | Purpose |
|---|---|
run_mcdev_command | Execute an explicitly requested supported native mcdev command with exact argv tokens and explicit targets/choices; supports long-running operations, cancellation and bounded diagnostics. Native local/remote effects apply; completion is not independent remote verification. |
reconcile_mcdev_operation | Release an uncertain native-operation latch after operator confirmation that related processes have stopped and partial effects have been reconciled. Does not perform or verify reconciliation, retry a command or authorize another operation. |
mcdev_search_docs | Search bundled sfmc-devtools wiki Markdown by keywords, with an optional result limit. |
mcdev_get_doc_section | Page through an unreviewed bundled wiki section using a search Source ID and UTF-16 offsets; retrieved claims are not endorsements. |
mcdev_explain_config_key | Explain config topics (markets, marketList, createDeltaPkg, …) with summaries and wiki hints. |
mcdev_component_checklist | Return component questions and typical dependent metadata types (journey, automation, …). |
mcdev_list_metadata_types | List types from Mcdev.explainTypes() in silent JSON mode, optionally filtering by name or API name. |
mcdev_list_commands | List reviewed command declarations and aliases as guidance, not executable commands or an argv allowlist. |
mcdev_get_command | Look up an exact, case-sensitive command name or alias for guidance, not execution or approval. |
read_mcdev_project_config | Return complete, UNREDACTED original .mcdevrc.json text, including credentials and custom fields, from a canonical absolute project root; never reads .mcdev-auth.json. |
diagnose_mcdev_project_config | Provide partial static config findings and recommend the visual MCDev Pipeline Builder first; no writes, native validation or execution-readiness assessment. |
preview_mcdev_project_config | Compare current config with a complete proposed JSON document, not a patch; return full unredacted changes and partial static diagnosis within a whole-result byte budget, without applying changes. |
inspect_mcdev_git_policy | Inspect local Git status/ref metadata and remote-tracking ancestry; branch conventions, remote freshness and BU synchronization remain unverified. Separate from auth-protection checks. |
inspect_mcdev_git_range | Compare two explicit refs using local Git metadata; optionally annotate one caller-declared promotion/back-promotion edge. No inferred policy, branch roles or verified remote freshness/BU synchronization. |
inspect_mcdev_project | Return complete unredacted config and independently check Git ignore/index metadata for auth protection; no auth-content/history reads, repairs, staging or untracking. |
inventory_mcdev_project_artifacts | Inventory configured retrieve/deploy paths with bounded metadata-only traversal; no artifact-content reads or dependency confirmation. |
resolve_mcdev_project_artifact | Resolve one explicit root/credential/BU/type/key identity to local query, script or bounded asset-email paths and editable companions; no dependency confirmation or remote-freshness guarantee. |
read_mcdev_artifact_source | Hand off complete original UTF-8 editable source and its original-byte SHA-256 for a qualified query, script or bounded asset-email identity; explicit email sourceRole selects HTML/preheader/text when needed. No rendering, validation or execution; the host coordinates companion validators, with text/SQL validation not established. |
preview_mcdev_project_command | Give guidance-only retrieve/deploy previews for an explicit config mapping, reviewed type, literal key and supported options; paths and execution readiness remain unknown. No subprocess or dry-run. |
diagnose_mcdev_retrieve_logs | Read bounded historical normal logs for one exact query/Script retrieve and explicit UTC window; return finite observations and basename/time provenance only, never raw logs or remote completeness. No rerun. |
Config inspection uses bounded reads, path checks and sanitized failure responses; these are not redaction. Callers must prevent concurrent filesystem mutation: these checks are not an atomic filesystem sandbox. .mcdev-auth.json is excluded from content reads.
Call mcdev_list_commands / mcdev_get_command to discover native signatures and execution availability. Then call run_mcdev_command with an absolute workspaceRoot, canonical command, and args containing exact argv tokens after the command. Shell metacharacters are literal arguments; no shell is started. The installed npm mcdev owns selectors, type/subtype support, validation, formatting, templating and deployment.
For example, to retrieve a query:
{
"workspaceRoot": "F:\\Projects\\marketing", "command": "retrieve", "args": ["development/Main", "query", "welcome-query"] }
Other native workflows use the same envelope:
retrieve, args ["development/Main", "asset-email", "welcome-email"].deploy, args ["development/Main", "automation", "nightly-import", "--fromRetrieve"].build, args ["--buFrom", "development/Main", "--buTo", "production/Main", "--marketFrom", "development", "--marketTo", "production", "--metadata", "query:welcome-query", "--no-purge"]. Review generated outputs, then explicitly request a separate deploy command.buildTemplate, buildDefinition or buildDefinitionBulk with native positional and market/list arguments. Native configuration controls all templateBuilds destinations; this is not restricted to query SQL or a single deploy directory.clone with explicit --buFrom, --buTo, --metadata and boolean --purge or --no-purge choices. Native clone markets and build behavior apply.badKeys and document write native local reports. explainTypes --json returns a bounded struSolo se muestra el principio; lee el resto en el repo