mcdev MCP: wiki search, .mcdevrc help, journey checklists, metadata types via mcdev.
MCP (Model Context Protocol) server for Accenture SFMC DevTools (mcdev): search the project wiki offline, learn .mcdevrc.json concepts (markets, marketList, createDeltaPkg, validations), walk component checklists (e.g. journeys), and list metadata types via the installed mcdev package.
Pair with mcp-server-sfmc for AMPscript / SSJS language validation and lookups.
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.
| Tool | Purpose |
|---|---|
mcdev_search_docs | Search bundled sfmc-devtools wiki Markdown |
mcdev_explain_config_key | Short explanations for config topics (markets, marketList, createDeltaPkg, …) |
mcdev_component_checklist | Questions + dependent metadata types (journey, automation, …) |
mcdev_list_metadata_types | Types from Mcdev.explainTypes() (silent JSON mode — safe for MCP stdio) |
read_mcdev_project_config | Read .mcdevrc.json with credentials stripped (never reads .mcdev-auth.json) |
Register mcp-server-mcdev with the same patterns as other stdio MCP servers (package name in args).
.vscode/mcp.json{
"servers": {
"mcdev": {
"type": "stdio",
"command": "npx",
"args": ["-y", "mcp-server-mcdev@latest"]
}
}
}
~/.cursor/mcp.json or project .cursor/mcp.json{
"mcpServers": {
"mcdev": {
"command": "npx",
"args": ["-y", "mcp-server-mcdev@latest"]
}
}
}
~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows) — use the same mcpServers object shape as Cursor.
~/.codeium/windsurf/mcp_config.json — same mcpServers shape as Cursor.
npm install -g mcp-server-mcdev
Then use "command": "mcp-server-mcdev", "args": [] (or the binary name from this package’s bin field).
The SFMC DevTools extension documents optional MCP setup for AI-assisted mcdev workflows (see that repo’s README).
From this package directory, with the wiki checkout next to the repo (or set SFMC_DEVTOOLS_WIKI):
npm run bundle-wiki
npm run build
MIT © Jörn Berkefeld
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y mcp-server-mcdevMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-joernberkefeld-mcp-server-mcdev": {
"command": "npx",
"args": [
"-y",
"mcp-server-mcdev"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencemcp-server-mcdevnpmio.github.JoernBerkefeld/mcp-server-mcdev works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.