mtdt — Salesforce DevOps

Registre officiel Cloud et DevOps

mtdt.io MCP: Salesforce DevOps platform connector (metadata deployments, backups and more)

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

Remote (streamable-http)
Claude Code
claude mcp add --transport http mtdt-salesforce-devops 'https://mcp.mtdt.io'
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "mtdt-salesforce-devops": {
            "type": "http",
            "url": "https://mcp.mtdt.io"
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. mtdt — MCP server for your AI agent
  2. What your agent gets
  3. Claude Code plugin — connection + built-in skills
  4. Connect (any MCP client)
  5. Notes

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: list orgs, create deployments, browse/retrieve metadata, pre-deploy checks (impact analysis, target conflicts, profile & permission warnings, record-backup recommendations), Apex test recommendations, validate with tests, quick-deploy. A zip the agent already has (SFDX project or Metadata API package) can be uploaded straight to mtdt and deployed whole. Long-running deploys are awaitable server-side (await_deploy_status) so your agent doesn't busy-poll.

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. 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:

ClientOne-liner
Claude Codeclaude mcp add --transport http mtdt https://mcp.mtdt.io
Cursor
OpenAI Codexcodex mcp add mtdt --url https://mcp.mtdt.io
OpenCode"mcp": { "mtdt": { "type": "remote", "url": "https://mcp.mtdt.io" } }

Notes

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

Questions fréquentes

Qu'est-ce que mtdt — Salesforce DevOps ?

mtdt.io MCP: Salesforce DevOps platform connector (metadata deployments, backups and more)

Comment installer mtdt — Salesforce DevOps ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http mtdt-salesforce-devops 'https://mcp.mtdt.io'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour mtdt — Salesforce DevOps ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

mtdt — Salesforce DevOps est-il open source ?

Son code est public sur GitHub, mais le dépôt ne déclare pas de licence standard.

Qui maintient mtdt — Salesforce DevOps ?

Il est publié par mtdt-io. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.