mcp-server-mcdev
This MCP server lets AI clients execute and inspect Accenture SFMC DevTools (mcdev) metadata workflows locally, with explicit safety and verification limits.
Run supported noninteractive native
mcdevcommands such as retrieve, deploy, build, clone, template/definition workflows, and output-only commands using exact argv tokens, explicit targets, long timeouts, and cancellation.Release an uncertain-operation latch only after an operator confirms processes stopped and partial effects were reconciled.
Discover native commands, aliases, execution availability, metadata types, config topics, and component checklists.
Search and page through bundled offline
sfmc-devtoolswiki documentation.Read complete unredacted
.mcdevrc.jsonfiles and statically diagnose or preview proposed config changes without writing.Inspect Git status/refs/ranges and assess caller-declared promotion or back-promotion containment using local Git metadata.
Inspect project auth-protection ignore/index metadata, inventory configured artifact paths, and resolve qualified query/script/asset-email artifacts.
Read complete editable source for qualified artifacts with original-byte SHA-256, without rendering, validation, or execution.
Provide guidance-only retrieve/deploy previews that are not dry runs and do not authorize execution.
Diagnose bounded historical retrieve logs for exact query/script windows without exposing raw logs or claiming remote completeness.
Limitations: local stdio only, no shell, not a sandbox, no automatic retry/rollback, and no independent remote synchronization verification.
Integrates with Accenture SFMC DevTools (mcdev) by providing tools to search the bundled sfmc-devtools wiki offline, explain .mcdevrc.json configuration concepts such as markets, marketList, createDeltaPkg, and validations, return component checklists for metadata types like journeys and automations, list supported metadata types from the installed mcdev package, and read project .mcdevrc.json configuration with credentials stripped.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-server-mcdev search the wiki for data extensions"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-server-mcdev
Use 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 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.
Related MCP server: sf-architect-mcp
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.
Tool | Purpose |
| 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. |
| 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. |
| Search bundled sfmc-devtools wiki Markdown by keywords, with an optional result limit. |
| Page through an unreviewed bundled wiki section using a search Source ID and UTF-16 offsets; retrieved claims are not endorsements. |
| Explain config topics ( |
| Return component questions and typical dependent metadata types ( |
| List types from |
| List reviewed command declarations and aliases as guidance, not executable commands or an argv allowlist. |
| Look up an exact, case-sensitive command name or alias for guidance, not execution or approval. |
| Return complete, UNREDACTED original |
| Provide partial static config findings and recommend the visual MCDev Pipeline Builder first; no writes, native validation or execution-readiness assessment. |
| 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 local Git status/ref metadata and remote-tracking ancestry; branch conventions, remote freshness and BU synchronization remain unverified. Separate from auth-protection checks. |
| 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. |
| Return complete unredacted config and independently check Git ignore/index metadata for auth protection; no auth-content/history reads, repairs, staging or untracking. |
| Inventory configured retrieve/deploy paths with bounded metadata-only traversal; no artifact-content reads or dependency confirmation. |
| 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. |
| 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 |
| 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. |
| 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.
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 separatedeploycommand.Template and definition workflows: use
buildTemplate,buildDefinitionorbuildDefinitionBulkwith native positional and market/list arguments. Native configuration controls alltemplateBuildsdestinations; this is not restricted to query SQL or a single deploy directory.Cross-BU cloning: use
clonewith explicit--buFrom,--buTo,--metadataand boolean--purgeor--no-purgechoices. Native clone markets and build behavior apply.Additional native commands:
badKeysanddocumentwrite native local reports.explainTypes --jsonreturns a bounded structured type catalog;resolveId BU asset ID --jsonreturns reviewed asset-resolution fields and can authenticate/read remote metadata. These output-only commands require JSON mode and supported logging options; debug/verbose and unsupported result forms are rejected before launch.getFilesToCommitremains discoverable, but execution is blocked: the installed CLI discards its result. Use mcdev's local programmatic API instead. Declaration inventory is not executable coverage.
Supply missing choices before launch. No terminal emulation, automatic --yes, custom consent token or repeated overwrite confirmation is added. Normal MCP-host approval applies to the actual operation. Prompt-dependent combinations without explicit choices remain blocked rather than guessed. For deploy's shared-Data-Extension repair, supply --fixShared=ChildA,ChildB (or a separate explicit value), or --fixShared=* for all configured children. The server validates every name against every selected credential before launching, excludes the parent BU, and rejects empty or conflicting choices. The installed mcdev 10.1.1 CLI handles the explicit selection directly; no bridge, unpublished dependency or runtime patch is required. Use --no-fixShared to disable repair. Bare --fixShared cannot supply the required choice.
Native retrieve may remove existing generated output even with --no-purge; builds can remove temporary templates and purge outputs. Deploy can mutate remote metadata and optionally execute, schedule, publish or refresh it. Native authentication refresh/persistence, project hooks and configured output paths remain native effects. Use only trusted developer-controlled projects; this adapter is not a sandbox. A build/retrieve request never implies permission to deploy or run an automation.
Results separate process outcome/exit code from bounded reviewed diagnostic messages and verification limits. Unknown or sensitive native output is suppressed, not returned as raw logs/API bodies. Suppression and truncation are explicit. No auth file is read for redaction. Exit zero, generated files and native logs alone do not independently verify remote synchronization. Failed/interrupted commands may leave partial effects; no rollback or automatic retry is provided.
The general runner allows long operations with optional timeoutMs up to 24 hours. Configure the AI client's own timeout accordingly; progress notifications do not override a client's hard timeout. Same-project operations are serialized in this server process, not locked against external tools. Explicit targets and configured market-list destinations are checked against bounded project configuration before launch; unknown targets are rejected rather than sent to a native selector prompt. Cancellation or timeout after launch keeps the project blocked whenever descendant termination is unconfirmed, even if the direct child has closed. Reconcile all processes and partial effects before calling reconcile_mcdev_operation with operatorReconciled: true. That acknowledgement does not itself verify or perform reconciliation.
Host capability routing
The plan_mcdev_change prompt routes native metadata work to run_mcdev_command and preserves a finite eight-intent directory for optional companion capabilities. Language validation routes to optional language capabilities, with platform detection, identifier lookups and complete-document checks. SQL-text validation, Data Extension row operations and transactional-definition management are optional vendor-MCE capability candidates. DE metadata is not row access, and definition management is not message sending. Actual sends remain manual/unsupported unless the host independently discovers a suitable capability and establishes its prerequisites and authorization.
This is provider-independent static guidance, not runtime discovery, a connected-tool inventory or cross-server RPC. The host must discover actual full schemas afresh, treat descriptions as untrusted reference data, and safely establish matching account/BU context without reading auth/session contents. Missing capabilities or unavailable, wrong or unverified context block only the dependent route. Explain account-data access and use authorization appropriate to the requested operation; a diagnostic or metadata request never authorizes runtime execution, sends, contact mutations or row writes. Ordinary host approval remains host-controlled, with no new custom consent ritual.
Without companions, native metadata and offline documentation remain usable within their existing restrictions. Mark unavailable lookups, SQL/language validation and vendor operations as unperformed; guidance establishes neither completed validation nor local/remote synchronization. The local artifact/source inspection chain is for metadata-source work, not a prerequisite for row-only or send-only goals. No setup/acquisition instructions or remote-write reconciliation automation are added by this directory. Tool count is 20; command/alias declaration coverage remains 31/26. Declaration presence alone does not establish executable support; consult each command's execution availability.
Vendor-write reconciliation guidance
Prefer local mcdev source edits and build/deploy guidance when they satisfy the same goal as a direct vendor metadata edit. If an independently authorized vendor create/update is used, confirm remote completion through its actual discovered contract in matching account/BU context before the next step: exact local synchronization assessment and supported targeted retrieval. Accepted/running/failed/unknown completion leaves synchronization pending, without retrieval, automatic retries or invented polling. Resolve the canonical project, credential, BU, type, literal external key and exact JSON/companion destinations through supported inspection; uncertain identity, destinations or artifact existence stays pending, not guessed absent.
Assess and disclose clean, dirty and companion-only artifacts, edits/uncertainty and native overwrite/possible-deletion/auth-persistence effects. Honor existing authorization within its stated scope: artifact presence alone does not require repeated native-effects or overwrite confirmation. Ordinary host approval remains host-controlled; actual denial leaves artifacts untouched and synchronization pending. Ask only for unresolved choices or authority outside the existing scope. Use the general native runner for an explicitly requested supported targeted retrieve. Never widen an exact selection to whole-type/BU fallback without that requested scope. Rows, runtime, sends and contacts have no invented metadata equivalent. Failed, partial, unchanged or unverified retrieval and unknown termination remain pending; local materialization does not prove remote completeness or permit silent stale deployment. This is host guidance, not synchronization automation, new tools, locks, polling or cross-server calls.
Explicit Git promotion assessment
inspect_mcdev_git_range still requires only workspaceRoot, sourceRef and targetRef. Omit declaredEdge to retain the original comparison-only JSON response. Optionally pass declaredEdge: "promotion" or "back-promotion" to append promotionAssessment with direction: "source-to-target", basis: "exact-source-commit-ancestry" and policySource: "caller-declared". Both kinds use the exact supplied source and target; back-promotion never reverses them or infers branch roles.
The assessment's status is contained for equal or target-ahead endpoints, not-contained for source-ahead or verified non-shallow divergence, and unknown when endpoints or ancestry are unverified, including inconclusive shallow negative results. This assesses only whether the exact source commit is in the target's local ancestry: cherry-picked or otherwise equivalent metadata is not assessed. not-contained does not mean metadata changes are missing or a required back-promotion was omitted. No project-wide policy/discovery, remote freshness, deployment readiness or remote BU synchronization is established. Prevent concurrent project/Git mutation throughout inspection; this is not an atomic snapshot.
Connecting AI clients
Register mcp-server-mcdev with the same patterns as other stdio MCP servers (package name in args).
VS Code (1.99+) — .vscode/mcp.json
{
"servers": {
"mcdev": {
"type": "stdio",
"command": "npx",
"args": ["-y", "mcp-server-mcdev@latest"]
}
}
}Cursor — ~/.cursor/mcp.json or project .cursor/mcp.json
{
"mcpServers": {
"mcdev": {
"command": "npx",
"args": ["-y", "mcp-server-mcdev@latest"]
}
}
}Claude Desktop
~/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.
Windsurf
~/.codeium/windsurf/mcp_config.json — same mcpServers shape as Cursor.
Global install (faster startup)
npm install -g mcp-server-mcdevThen use "command": "mcp-server-mcdev", "args": [] (or the binary name from this package’s bin field).
Historical retrieve-log diagnosis
diagnose_mcdev_retrieve_logs is a dedicated read-only exception to the prohibition on general log-content readers. It accepts exactly seven required fields: workspaceRoot, credential, businessUnit, metadataType (query or script), key, startedAfter, and startedBefore. Use exact configured aliases and one literal key. Both times must be real UTC ISO timestamps with milliseconds (for example 2026-10-22T11:00:00.000Z), ordered inclusively and no more than 24 hours apart. No caller-supplied paths, flags or budget overrides are accepted.
Historical correlation supports mcdev 10.1.0 and 10.1.1, with canonical joined command spelling retrieve credential/BU query key or retrieve credential/BU script key. Each credential, BU and key must match [A-Za-z0-9_][A-Za-z0-9_.-]{0,127}. Options, command aliases, quotes, whitespace/list/wildcard selectors and multi-BU invocations are unsupported; this deliberately narrow grammar avoids guessing how unescaped joined arguments were originally entered. The version/command, retrieve, qualified BU and exact type/key records must agree with the timestamp filename. Modification time alone cannot select a log.
Only normal timestamp-named .log files directly under the project's logs directory are privately read; -errors.log companions are excluded. Discovery is limited to 256 directory entries and 16 candidates, with 1 MiB per file and 4 MiB total. Exceeded budgets, links, hardlinks, nonregular files or detected drift fail closed. Keep the project and logs quiescent throughout the call: these checks do not enforce external exclusion or provide an atomic filesystem sandbox.
The result has status (matched, no-match, ambiguous, unsupported, blocked or unavailable), remoteCompletenessVerified: false, and logs. Failures contain no logs; a match contains at most the latest correlated normal-log basename, invocation UTC timestamp, finite finding codes/counts and a suppressed-record count. Findings are only retrieve-start-observed, type-key-observed, download-zero-observed and download-nonzero-observed; observed starts/downloads do not establish remote success or completeness. Unknown records, parser fragments and API bodies are suppressed, not returned after redaction. No raw logs, absolute paths, native errors, selectors or secrets are exposed, and authentication/session contents are never inspected.
Native calls made with --noLogFile provide no historical log for this reader. Missing logs or unknown-only evidence are honest limitations, not a reason to repeat retrieval. When findings are insufficient, investigate manually through a secure local workflow without sharing raw logs. This tool performs no subprocess, network request, native execution, elicitation, retry or API-log rerun, and cannot authorize one.
SFMC DevTools VS Code extension
The SFMC DevTools extension documents optional MCP setup for AI-assisted mcdev workflows (see that repo’s README).
Refresh bundled wiki
Ordinary npm run bundle-wiki, builds, hooks and prepublish reuse the committed bundled/wiki without reading a sibling checkout. To deliberately refresh from the sibling ../sfmc-devtools.wiki checkout:
npm run bundle-wiki -- --refreshFor a clean published or otherwise reviewed source directory, set SFMC_DEVTOOLS_WIKI and explicitly request refresh:
export SFMC_DEVTOOLS_WIKI=/absolute/path/to/reviewed-wiki
npm run bundle-wiki -- --refreshIn PowerShell, use $env:SFMC_DEVTOOLS_WIKI = 'F:\path\to\reviewed-wiki'. Ordinary builds, hooks and prepublish do not read this source, even when the variable is set. A missing or empty refresh source fails rather than silently falling back to another checkout. Refresh conflicts with local annotations require exact old/proposed SHA-256 reconciliation through the exported bundleWiki API; there is no force-refresh CLI flag.
The published wiki baseline is clean remote commit 6a87898ba811ba9f5ad3553e72cce97f128a8601 (a commit, not a wiki tag), refreshed for mcdev 10.1.1. bundled/wiki-provenance.json records the published page hashes, the exact refresh reconciliation, and separate final-byte hashes for six locally annotated pages. The source remains marked not-reviewed: importing a clean published snapshot does not endorse every upstream claim.
Getting Started, Updating mcdev, Admin Commands, and Git-based deployments and CI/CD retain explicitly pending/unreleased extension-bundled CLI and optional-Git guidance. Templating Commands and Advanced Configuration retain local behavior/safety corrections. These annotations are not evidence that the pending VS Code extension shipped. The shared Data Extension selection documentation was imported from the published wiki; the initial-push fix and boolean --purge / --no-purge fixes are marked released based on mcdev 10.1.1 release notes. The published wiki still labels the purge fix as pending, so the bundle corrects that stale label locally. Preserve or explicitly reconcile all remaining annotations during future refreshes.
License
MIT © Jörn Berkefeld
Available Tools
20 toolsdiagnose_mcdev_project_configA
Read-only partial static diagnosis of .mcdevrc.json, not native mcdev validation or execution readiness. FIRST use the visual MCDev Pipeline Builder before editing configuration. Returns builder guidance, findings and explicit limitations; never writes files, loads hooks, reads auth or executes native CLI/live checks. Prevent concurrent filesystem mutation.
Inputs: workspaceRoot (required).
diagnose_mcdev_retrieve_logsARead-only
Read-only historical normal-log diagnosis for one exact configured credential/businessUnit and query or script key. Reads only bounded project/logs timestamp files, never error companions or authentication/session contents. Requires caller-managed quiescence. Supports mcdev 10.1.0 and 10.1.1 canonical retrieve credential/BU type key with literal selectors and no options, aliases or quotes, within an explicit UTC ISO millisecond window of at most 24 hours. Returns finite observations and validated basename/time provenance, never raw logs, paths, errors, secrets or remote completeness. No subprocess, network, native execution, elicitation or rerun. Native calls with --noLogFile produce no historical logs; absent evidence is no-match, not a reason to repeat retrieval. Unknown records are suppressed; investigate manually when evidence is insufficient.
Inputs: key (required), credential (required), businessUnit (required), metadataType (required), +3 more.
inspect_mcdev_git_policyA
Read-only Git metadata inspection, not verified policy or execution readiness. Ancestry uses a local remote-tracking snapshot, not fresh remote state. Branch roles, ticket and commit-prefix conventions remain unresolved; remote BU synchronization is unknown. Top-level verified covers status metadata only; refs.verified is independent. Separate from inspect_mcdev_project auth protection checks. No policy persistence, branch changes, commit-message/history/auth/artifact-content reads or native mcdev/live execution. Prevent concurrent project/Git mutation; not an atomic snapshot.
Inputs: workspaceRoot (required).
inspect_mcdev_git_rangeA
Read-only Git metadata comparison of two explicit refs, not promotion policy or execution readiness. Optional declaredEdge assesses only exact-source-commit containment in the target, with the same source-to-target direction for promotion and back-promotion. Local snapshot only; remote freshness and remote BU synchronization are unknown. No inferred branch roles or backpromotions, auth/log/artifact/commit-content reads, branch changes or native mcdev/live execution. Prevent concurrent project/Git mutation; not an atomic snapshot. Separate from inspect_mcdev_project auth protection checks.
Inputs: sourceRef (required), targetRef (required), workspaceRoot (required), declaredEdge.
inspect_mcdev_projectA
Read the complete UNREDACTED project config, including credentials, and independently inspect Git ignore/index metadata for auth protection. Read-only: never reads auth contents or history and never repairs, stages or untracks files.
Inputs: workspaceRoot (required).
inventory_mcdev_project_artifactsB
Read-only, metadata-only inventory of configured retrieve/deploy paths; does not open artifact contents or confirm dependencies. Never reads auth contents or logs. No guarantee of remote freshness or an atomic filesystem sandbox; prevent concurrent filesystem mutation.
Inputs: workspaceRoot (required), maxDepth, maxEntries.
mcdev_component_checklistA
Return a structured checklist of questions and dependent metadata types for authoring or migrating SFMC components with mcdev (e.g. journey, automation).
Inputs: component (required).
mcdev_explain_config_keyA
Explain a .mcdevrc.json concept (markets, marketList, createDeltaPkg, deployment, validations, etc.) with a short summary and wiki file hints.
Inputs: topic (required).
mcdev_get_commandA
Read-only exact, case-sensitive native command or alias lookup. Returns signature, execution availability and effects; use the canonical name with run_mcdev_command when supported. Lookup grants no approval, launches no process and is not a dry run. Project readiness remains unverified.
Inputs: nameOrAlias (required).
mcdev_get_doc_sectionA
Retrieve an unreviewed bundled wiki section by its search Source ID. Returns a JSON page with UTF-16 offsets and nextOffset (null at end); retrieved claims are not semantic endorsements.
Inputs: id (required), limit, offset.
mcdev_list_commandsA
Read-only native mcdev command discovery: signatures, aliases, execution availability and effects. Use run_mcdev_command for supported commands with explicit arguments and ordinary host approval. Listing itself performs no subprocess or dry run; native mcdev has no dry-run mode. Project readiness is not verified.
Inputs: no named parameters.
mcdev_list_metadata_typesB
List metadata types supported by the installed mcdev package (from Mcdev.explainTypes). Optional filter substring.
Inputs: filter.
mcdev_search_docsB
Search bundled sfmc-devtools wiki Markdown (from GitHub wiki) for mcdev configuration, commands, markets, createDeltaPkg, build, validations.
Inputs: query (required), limit.
preview_mcdev_project_commandB
Read-only, guidance-only project-qualified retrieve/deploy preview. Verifies only the explicit credential/businessUnit config mapping; execution readiness and configured paths remain unknown. Generic native effects are not proven project-local effects. No subprocess, hooks, auth/log reads or live checks. Not a dry run: native mcdev has no dry-run mode. Execution remains disabled; this cannot authorize an operation. Prevent concurrent filesystem mutation.
Inputs: key (required), type (required), command (required), credential (required), +3 more.
preview_mcdev_project_configA
Read-only comparison of the current .mcdevrc.json and a complete proposed JSON document, not a patch. FIRST use the visual MCDev Pipeline Builder before editing configuration. Returns full unredacted changes and partial static proposed diagnosis within a whole-result byte budget; no truncation. Inputs are at most 1 MiB each. Hashes describe rawText encoded as UTF-8 without normalization, not independently verified original filesystem bytes. No writes, apply authorization, native validation, execution readiness or atomic filesystem binding. Prevent concurrent filesystem mutation. Never reads auth or logs, loads hooks or performs native/live checks.
Inputs: workspaceRoot (required), proposedConfig (required), maxOutputBytes.
read_mcdev_artifact_sourceA
Read-only full-text editable-source handoff for one qualified query, script or bounded asset-email identity (htmlemail/templatebasedemail matched by customerKey with exact HTML/preheader/text extracts), never a caller-supplied file path. Requires exactly one editable companion unless an explicit sourceRole selects html, preheader or text from resolved email companions; multiple companions need an explicit role or are blocked with no source and no guessed choice. sourceRole accepts no arbitrary filenames or paths and applies only to resolved email companions. Dependencies are not confirmed. Returns complete original UTF-8 text (including BOM) and SHA-256 of original file bytes without truncation; unresolved or blocked results never contain source. No rendering, validation, mutation, native modules or live execution is performed; execution readiness is unknown. The host must discover companion capabilities and coordinate platform detection, identifier lookup and full-document validate_ssjs, validate_sfmc_html or validate_ampscript as appropriate. Email html requires validate_sfmc_html; preheader/text have language text and text-validator-not-established, not an inferred AMPscript validator. SQL validation is not established. Do not claim companion tools were performed. Prevent concurrent filesystem mutation: bounded checks are not atomic or a concurrent-mutation sandbox. Never reads auth contents or logs.
Inputs: rootKind (required), credential (required), externalKey (required), businessUnit (required), +5 more.
read_mcdev_project_configA
Read the complete, UNREDACTED .mcdevrc.json, including credentials and custom fields, from a canonical absolute project root. Returns original raw text; never reads .mcdev-auth.json.
Inputs: workspaceRoot (required).
reconcile_mcdev_operationA
Release an uncertain native-operation latch only after the operator has confirmed all related processes stopped and reconciled partial local/remote effects. This acknowledgement does not perform or verify reconciliation, kill processes, retry commands or authorize a new operation. Never call solely because a server restarted or a timeout elapsed.
Inputs: workspaceRoot (required), operatorReconciled (required).
resolve_mcdev_project_artifactB
Read-only qualified local resolution for query, script and bounded asset-email layouts (htmlemail/templatebasedemail matched by customerKey, with exact HTML/preheader/text extract companions); other types and layouts are unsupported. Returns paths, not arbitrary file contents, and does not confirm dependencies. Blocked/ambiguous results offer no editable companions. Never reads auth contents or logs. No guarantee of remote freshness or an atomic filesystem sandbox; prevent concurrent filesystem mutation.
Inputs: rootKind (required), credential (required), externalKey (required), businessUnit (required), +4 more.
run_mcdev_commandADestructive
Execute an explicitly requested native mcdev command in a developer-controlled project. Use mcdev_get_command for syntax and execution availability. args are exact argv tokens after the canonical command, not a shell string. Supports native metadata selectors, markets, validation hooks and native overwrite/deletion/auth-persistence effects. Supply explicit target/choices; no terminal interaction or automatic defaults. Deploy/runtime effects require the corresponding user request and ordinary host approval; no extra consent ritual. Diagnostics are bounded projections, not raw output. Completion is not independent remote verification; never automatically retry partial/unknown operations. Configure host timeouts for long operations; progress is emitted when requested.
Inputs: args (required), command (required), workspaceRoot (required), timeoutMs.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 20 tools
Several tools read/diagnose the same .mcdevrc.json resource: read_mcdev_project_config, inspect_mcdev_project, diagnose_mcdev_project_config, and preview_mcdev_project_config all overlap heavily, and preview_mcdev_project_command vs diagnose_mcdev_project_config are easily confused. An agent will struggle to pick the right config-inspection tool, and warnings inside descriptions (e.g. 'use the visual MCDev Pipeline Builder FIRST') signal boundary problems rather than resolve them.
Two competing conventions coexist: a mcdev_ prefix pattern (mcdev_get_command, mcdev_list_commands, mcdev_search_docs) and a verb-first pattern (diagnose_mcdev_project_config, read_mcdev_project_config, inspect_mcdev_git_policy). The verb ordering is inconsistent across the set, so a predictable grouping is hard to infer even though everything is snake_case.
20 tools is in the heavy range for a server whose core purpose is mcdev project inspection and command execution. Many are narrow read-only variants (git_policy vs git_range, artifact inventory vs resolve vs read), which inflates the surface more than the domain complexity strictly requires.
run_mcdev_command gives a broad escape hatch for native operations, and doc/command discovery is reasonably covered. However the surface is read/diagnose-heavy with no clear write/apply path for config or artifacts (only previews), and many operations are explicitly declared out of scope, leaving notable gaps for a complete authoring lifecycle.
Maintenance
Related MCP Connectors
Search your AI chat history (ChatGPT, Claude, Codex) from any MCP client. Remote, private, read-only
Hosted markdown project wikis your team's AI assistants read, search, and update over MCP.
Connect AI assistants to your GitHub-hosted Obsidian vault to seamlessly access, search, and analy…
Your org's AI agents, tasks, runs, search, and brain files as MCP tools and resources.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables Salesforce developers to create code and configuration using local documentation, with optional semantic search.9 npm1MIT
- AlicenseAqualityDmaintenanceScrapes, indexes, and serves Salesforce Architect documentation locally, enabling fast offline RAG-powered search and retrieval for AI coding assistants.9MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to search and read offline documentation from synced libraries via MCP tools, providing hybrid keyword and semantic search without network calls.8 npm1MIT
- AlicenseAqualityCmaintenanceEnables AI agents to search, install, read, and navigate DevDocs documentation offline via MCP, with token-efficient search/read/toc tools and local caching.627 npm1MIT