Skip to main content
ClaudeWave

mtdt.io MCP server — Salesforce DevOps for any MCP-capable AI agent (Claude Code, Cursor, Codex, OpenCode)

MCP ServersRegistry oficial0 estrellas0 forksActualizado today
ClaudeWave Trust Score
62/100
· OK
Passed
  • ✓Actively maintained (<30d)
  • ✓Clear description
  • ✓Documented (README)
Flags
  • !No standard license detected
Last scanned: 9/27/2026
Install in Claude Code / Claude Desktop
Method: Manual
Claude Code CLI
git clone https://github.com/mtdt-io/mcp
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "mcp": {
      "command": "node",
      "args": ["/path/to/mcp/dist/index.js"]
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
💡 Clone https://github.com/mtdt-io/mcp and follow its README for install instructions.
Casos de uso

Resumen de MCP Servers

# mtdt — MCP server for your AI agent

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

```
https://mcp.mtdt.io/mcp
```

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](https://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. 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, 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:

| Client | One-liner |
|---|---|
| Claude Code | `claude mcp add --transport http mtdt https://mcp.mtdt.io/mcp` |
| Cursor | [![Add mtdt to Cursor](https://cursor.com/deeplink/mcp-install-dark.svg)](https://cursor.com/en/install-mcp?name=mtdt&config=eyJ1cmwiOiJodHRwczovL21jcC5tdGR0LmlvL21jcCJ9) |
| OpenAI Codex | `codex mcp add mtdt --url https://mcp.mtdt.io/mcp` |
| OpenCode | `"mcp": { "mtdt": { "type": "remote", "url": "https://mcp.mtdt.io/mcp" } }` |

## Notes

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

Lo que la gente pregunta sobre mcp

¿Qué es mtdt-io/mcp?

+

mtdt-io/mcp es mcp servers para el ecosistema de Claude AI. mtdt.io MCP server — Salesforce DevOps for any MCP-capable AI agent (Claude Code, Cursor, Codex, OpenCode) Tiene 0 estrellas en GitHub y su última actualización registrada es del 2026-09-26.

¿Cómo se instala mcp?

+

Puedes instalar mcp clonando el repositorio (https://github.com/mtdt-io/mcp) o siguiendo las instrucciones del README en GitHub. ClaudeWave también te ofrece bloques de instalación rápida en esta misma página.

¿Es seguro usar mtdt-io/mcp?

+

Nuestro agente de seguridad ha analizado mtdt-io/mcp y le ha asignado un Trust Score de 62/100 (tier: OK). Revisa el desglose completo de comprobaciones superadas y flags en esta página.

¿Quién mantiene mtdt-io/mcp?

+

mtdt-io/mcp es mantenido por mtdt-io. La última actividad registrada en GitHub es del 2026-09-26, con 0 issues abiertos.

¿Hay alternativas a mcp?

+

Sí. En ClaudeWave puedes explorar mcp servers similares en /categories/mcp, ordenados por popularidad o actividad reciente.

Despliega mcp en tu cloud

Lleva este repo a producción en minutos. Cada plataforma genera su propio entorno con variables de entorno editables.

¿Mantienes este repo? Añade un badge a tu README

Pega el badge en tu README de GitHub para mostrar que está auditado por ClaudeWave. Cada badge enlaza de vuelta a esta página y muestra el Trust Score actual.

Featured on ClaudeWave: mtdt-io/mcp
[![Featured on ClaudeWave](https://claudewave.com/api/badge/mtdt-io-mcp)](https://claudewave.com/repo/mtdt-io-mcp)
<a href="https://claudewave.com/repo/mtdt-io-mcp"><img src="https://claudewave.com/api/badge/mtdt-io-mcp" alt="Featured on ClaudeWave: mtdt-io/mcp" width="320" height="64" /></a>

Más MCP Servers

Alternativas a mcp