mtdt — Salesforce DevOps

io.mtdtPublished by mtdt.ioOfficial publisherv0.3.0Updated Nov 5, 2026

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

The publisher's own server: mtdt — Salesforce DevOps

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Remote mtdt.io connector that lets an AI agent deploy, validate, compare and back up Salesforce org metadata through the mtdt DevOps platform.

What you can do
  • Find orgs and deployment sources such as git repos, metadata backups and uploaded archives
  • Browse metadata, create deployments, edit components and test level, and run pre-deploy checks
  • Validate with tests, then execute a saved draft or a quick deployment of a selected package
  • Upload and deploy an existing SFDX or Metadata API zip
  • Compare two orgs, back up org metadata, and move Work Items across project environments
  • Follow each launch with a run-state lookup
When to use it
Use it when an assistant should handle Salesforce release work: promoting metadata between orgs, running pre-flight checks and validation, comparing or backing up orgs, or troubleshooting failed deployment runs.
Requirements
A remote streamable HTTP endpoint with OAuth 2.0 browser sign-in and Dynamic Client Registration; no API keys or tokens to copy. An mtdt.io account with at least one connected Salesforce org. Deploy-capable tools need the mtdt:deploy consent scope.
Before you install
The connector sends requested Salesforce metadata and deployment/backup information through the MTDT service. Deploy tools change orgs and are gated by the mtdt:deploy scope, team roles and target approval policies; production targets should be confirmed rather than assumed. Review the privacy policy and terms of service before connecting.

Installation

In SourceWeft

  1. Open mtdt — Salesforce DevOps in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.mtdt%2Fsalesforce-devops/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "mtdt-salesforce-devops": {
      "type": "http",
      "url": "https://mcp.mtdt.io/"
    }
  }
}

README

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. 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[Add mtdt to 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.

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 [email protected] 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.

Source: README.md at commit fea6d19

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.3.0LatestNov 5, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Mtdt integrations

mtdt — Salesforce DevOps

io.mtdtOfficial publisher

Remote MCP connector for the mtdt.io Salesforce DevOps platform, letting an assistant plan, validate and run metadata deployments between Salesforce orgs.

Streamable HTTPWeb executableAuth
Cloud & InfrastructureCredential requiredNov 4, 2026