mtdt — Salesforce DevOps

mtdt — MCP server for your AI agent

Salesforce DevOps in any MCP-capable coding agent. One remote endpoint:

https://mcp.mtdt.io

Streamable HTTP + OAuth 2.0 (browser sign-in, Dynamic Client Registration) — no API keys, no tokens to copy. Works with Claude Code, Cursor, OpenAI Codex, OpenCode, and anything else that speaks MCP.

What your agent gets

Deploy metadata between Salesforce orgs through mtdt.io: find orgs and deployment sources (git repos, metadata backups, uploaded archives), create a deployment and edit its components and test level, browse metadata, run the pre-deploy checks (missing dependencies, target conflicts, profile & permission warnings, record-backup recommendations, Apex test recommendations), validate with tests, and deploy: use execute_deployment for the current saved draft or execute_quick_deployment for an explicitly selected validation package. A zip the agent already has (SFDX project or Metadata API package) can be uploaded straight to mtdt and deployed whole. Compare two orgs, back up org metadata, and move Work Items through a project's environments. Every launch answers at once with the run's state; your agent follows it with get_deployment_run.

Deploy-capable tools require the Run (mtdt:deploy) consent scope and always respect your team's mtdt roles — approval-gated targets stay approval-gated.

Claude Code plugin — connection + built-in skills

The plugin is more than the connection: it ships the deployment know-how as skills, so Claude doesn't just *have* the tools — it knows the playbook.

• `mtdt-deploy` — the full promotion workflow: resolve the target safely (production targets get confirmed, never assumed), browse & pick components, the pre-flight battery (the same checks a human gets in the Deploy modal), validation-first flow, quick-deploy, deploying a local zip, and the guardrails: the 75% coverage rule, rollback snapshots, approval gates.
• `mtdt-troubleshoot` — reading failed runs: component vs test vs coverage failures, quick-deploy prerequisites and expiry, stuck retrievals, auth pitfalls — each with the fix, not just the diagnosis.

/plugin marketplace add mtdt-io/mcp

/plugin install mtdt@mtdt

On first use Claude Code opens your browser to sign in to mtdt (OAuth) — no config files.

Connect (any MCP client)

Verified copy-paste configs per client (and the type-field gotchas between them): [CONNECT.md](CONNECT.md). Every client receives the deployment playbook at connection time (MCP instructions) and can pull the mtdt-deploy / mtdt-troubleshoot prompts; the plugin above ships the same know-how as skills, applied without being asked.

Quick versions:

Notes

• Requires an mtdt.io account with at least one connected Salesforce org.

Privacy and support

The connector processes requested Salesforce metadata and deployment/backup information through the MTDT service. Scope consent, team roles and target approval policies apply to the signed-in account. Review the privacy policy and terms of service before connecting. For support, email support@mtdt.io or use the contact form.

Directory packages

Maintainers can build the OpenAI/Codex and Claude distribution ZIPs with python3 publishing/package.py build. Submission materials and instructions are in publishing/README.md.