# mtdt — Salesforce DevOps

Connects your coding assistant to mtdt.io for Salesforce release management. It handles metadata comparisons, pre-deployment checks, Apex test suites, and cross-org deployments.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI
- Author: mtdt-io
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/mtdt-io/mcp
- Updated: 2026-10-13
- HTML: https://affpapa.org/en/nevibecode/mcp/mtdt-salesforce-devops

## What it does

This remote MCP server connects tools to `https://mcp.mtdt.io` over HTTP with OAuth 2.0 browser sign-in. Your assistant can browse connected orgs, pull metadata components, and dispatch SFDX or Metadata API packages. To avoid polling loops during long promotion jobs, it uses server-side status waiting with `await_deploy_status`.

Safety checks run before payloads touch the destination org. The service highlights target branch conflicts, flags permission warnings, recommends required Apex tests, and suggests record backups. Deploy tools strictly enforce the `mtdt:deploy` consent scope and respect team approval gates.

Connecting this server requires an active mtdt.io account with at least one linked Salesforce organization.

## Requirements
- Remote server: `https://mcp.mtdt.io`
- Works with: Salesforce

## Install

### Claude Code (native platform)

**Platform CLI: remote server**
```bash
claude mcp add --transport http mtdt https://mcp.mtdt.io
```

### Codex

**Platform CLI: remote server**
```bash
codex mcp add mtdt-salesforce-devops --url https://mcp.mtdt.io
```

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "mtdt-salesforce-devops": {
            "url": "https://mcp.mtdt.io"
        }
    }
}
```

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "mtdt-salesforce-devops": {
            "type": "http",
            "url": "https://mcp.mtdt.io"
        }
    }
}
```

### Gemini CLI

**Platform CLI: remote server**
```bash
gemini mcp add -t http mtdt-salesforce-devops https://mcp.mtdt.io
```

## When to use it
- deploy metadata packages and SFDX archives between Salesforce orgs
- detect component conflicts and permission issues prior to deployment
- run Apex validation suites while enforcing code coverage standards
- monitor long-running promotions on the server without busy-polling

## Example prompts
- Inspect metadata differences before pushing changes to our Salesforce sandbox
- Upload the local SFDX project archive and trigger a validation build via mtdt
- Review the failed deployment log and explain the Apex coverage errors

## Similar
- [platform-apex-anonymous-run](https://affpapa.org/en/nevibecode/skills/platform-apex-anonymous-run.md) — skill · 3100 installs
- [dx-org-permission-set-assign](https://affpapa.org/en/nevibecode/skills/dx-org-permission-set-assign.md) — skill · 5700 installs
- [Salesforce Apex & Triggers Development](https://affpapa.org/en/nevibecode/agents/salesforce-apex-triggers-development.md) — subagent · ★ 40478
- [salesforce-flow-design](https://affpapa.org/en/nevibecode/skills/salesforce-flow-design.md) — skill · 839 installs
- [salesforce-development](https://affpapa.org/en/nevibecode/skills/salesforce-development.md) — skill · 90 installs
- [Salesforce Cloud](https://affpapa.org/en/nevibecode/mcp/salesforce-cloud.md) — MCP server · ★ 6

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md