YepCode MCP — Installer & Démo en direct

Name: YepCode MCP MCP Server
Author: yepcode

Pourquoi l'utiliser

Fonctionnalités clés

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

Démo en direct

Aperçu en pratique

yepcode-mcp.replay ▶ prêt

0/0

Installer

Choisissez votre client

~/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"
      ]
    }
  }
}

Ouvrez Claude Desktop → Settings → Developer → Edit Config. Redémarrez après avoir enregistré.

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

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

Cursor utilise le même schéma mcpServers que Claude Desktop. La config projet l'emporte sur la globale.

VS Code → Cline → MCP Servers → Edit

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

Cliquez sur l'icône MCP Servers dans la barre latérale Cline, puis "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

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

Même format que Claude Desktop. Redémarrez Windsurf pour appliquer.

~/.continue/config.json

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

Continue utilise un tableau d'objets serveur plutôt qu'une map.

~/.config/zed/settings.json

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

Ajoutez dans context_servers. Zed recharge à chaud à la sauvegarde.

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

Une seule ligne. Vérifiez avec claude mcp list. Supprimez avec claude mcp remove.

Cas d'usage

Usages concrets : YepCode MCP

Give Claude controlled access to internal services without exposing secrets

👤 Platform teams ⏱ ~15 min intermediate

Quand l'utiliser : You want Claude to call internal systems (CRM, payment, etc.) without putting credentials in the model context.

Prérequis

Server/skill installed and authenticated — See repo README

Déroulement

Build a YepCode process

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

→ Process available in MCP
Call from Claude

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

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

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

Pièges

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

Combiner avec : github

Combinaisons

Associez-le à d'autres MCPs pour un effet X10

yepcode-mcp + github

Pair with github for complementary capabilities

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

Outils

Ce que ce MCP expose

Outil	Entrées	Quand appeler	Coût
list_processes	(none)	Discover what processes are exposed	free
run_process	slug, input	Execute a specific business process	Per YepCode plan

Coût et limites

Coût d'exécution

Quota d'API: See provider docs for rate limits
Tokens par appel: Varies by tool
Monétaire: See repo README for pricing details
Astuce: Cache tool results and avoid repeated identical calls.

Sécurité

Permissions, secrets, portée

Stockage des identifiants : Use environment variables; never commit secrets

Sortie de données : Tool calls go to the provider's API as documented

Dépannage

Erreurs courantes et correctifs

401 Invalid API token

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

Vérifier : list_processes returns your processes

process failed mid-run

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

Vérifier : Re-run with the same input from the UI

Alternatives

YepCode MCP vs autres

Alternative	Quand l'utiliser	Compromis
Pipedream MCP	You want a no-code workflow builder layer	Different programming model

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills