MCP Server Mcdev

mcp-server-mcdev

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.

Requirements

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.

MCP Registry

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.

Tools

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.

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.

Native execution

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:

• Asset/email retrieval: command retrieve, args ["development/Main", "asset-email", "welcome-email"].
• Automation deployment from retrieved sources: command deploy, args ["development/Main", "automation", "nightly-import", "--fromRetrieve"].
• Market-based build: command 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.
• Template and definition workflows: use 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.
• Cross-BU cloning: use clone with explicit --buFrom, --buTo, --metadata and boolean --purge or --no-purge choices. Native clone markets and build behavior apply.
• Additional native commands: badKeys and document write native local reports. explainTypes --json returns a bounded stru