YepCode MCP — Instalar & Demo ao vivo

Name: YepCode MCP MCP Server
Author: yepcode

Por que usar

Principais recursos

Every YepCode process appears as a typed MCP tool
Built-in secret store — no API keys in the conversation
Versioned + auditable execution history
Run Node or Python with full npm/pip ecosystem
Self-host or use the managed cloud

Demo ao vivo

Como fica na prática

yepcode-mcp.replay ▶ pronto

0/0

Instalar

Escolha seu cliente

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "yepcode-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@yepcode/mcp-server"
      ]
    }
  }
}

Abra Claude Desktop → Settings → Developer → Edit Config. Reinicie após salvar.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "yepcode-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@yepcode/mcp-server"
      ]
    }
  }
}

Cursor usa o mesmo esquema mcpServers que o Claude Desktop. Config de projeto vence a global.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "yepcode-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@yepcode/mcp-server"
      ]
    }
  }
}

Clique no ícone MCP Servers na barra lateral do Cline, depois "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "yepcode-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@yepcode/mcp-server"
      ]
    }
  }
}

Mesmo formato do Claude Desktop. Reinicie o Windsurf para aplicar.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "yepcode-mcp",
      "command": "npx",
      "args": [
        "-y",
        "@yepcode/mcp-server"
      ]
    }
  ]
}

O Continue usa um array de objetos de servidor em vez de um map.

~/.config/zed/settings.json

{
  "context_servers": {
    "yepcode-mcp": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "@yepcode/mcp-server"
        ]
      }
    }
  }
}

Adicione em context_servers. Zed recarrega automaticamente ao salvar.

claude mcp add yepcode-mcp -- npx -y @yepcode/mcp-server

Uma linha só. Verifique com claude mcp list. Remova com claude mcp remove.

Casos de uso

Usos do mundo real: YepCode MCP

Give Claude controlled access to internal services without exposing secrets

👤 Platform teams ⏱ ~15 min intermediate

Quando usar: You want Claude to call internal systems (CRM, payment, etc.) without putting credentials in the model context.

Pré-requisitos

Server/skill installed and authenticated — See repo README

Fluxo

Build a YepCode process

(in YepCode UI) Write a process refund-order that calls your payment provider. Store the API key in YepCode secrets.✓ Copiado

→ Process available in MCP
Call from Claude

Refund order #12345 with reason 'damaged in shipping'.✓ Copiado

→ YepCode executes refund-order; Claude reports success/failure

Resultado: Claude gets a typed, auditable interface to your internal systems — no secrets in chat.

Armadilhas

Every YepCode call costs execution minutes — Every YepCode call costs execution minutes — keep processes idempotent so retries are safe.

Combine com: github

Combinações

Combine com outros MCPs para 10× de alavancagem

yepcode-mcp + github

Pair with github for complementary capabilities

Use this server together with github to complete a multi-step task.✓ Copiado

Ferramentas

O que este MCP expõe

Ferramenta	Entradas	Quando chamar	Custo
list_processes	(none)	Discover what processes are exposed	free
run_process	slug, input	Execute a specific business process	Per YepCode plan

Custo e limites

O que custa rodar

Cota de API: See provider docs for rate limits
Tokens por chamada: Varies by tool
Monetário: See repo README for pricing details
Dica: Cache tool results and avoid repeated identical calls.

Segurança

Permissões, segredos, alcance

Armazenamento de credenciais: Use environment variables; never commit secrets

Saída de dados: Tool calls go to the provider's API as documented

Solução de problemas

Erros comuns e correções

401 Invalid API token

Create a YepCode API token in Settings → API and set YEPCODE_API_TOKEN.

Verificar: list_processes returns your processes

process failed mid-run

Open the YepCode UI execution log — it has full stack + secret-redacted inputs.

Verificar: Re-run with the same input from the UI

Alternativas

YepCode MCP vs. outros

Alternativa	Quando usar	Troca
Pipedream MCP	You want a no-code workflow builder layer	Different programming model

Mais

Recursos

📖 Leia o README oficial no GitHub

🐙 Ver issues abertas

🔍 Ver todos os 400+ servidores MCP e Skills