YepCode MCP

Name: YepCode MCP MCP Server
Author: yepcode

為什麼要用

核心特性

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

即時演示

實際使用效果

yepcode-mcp.replay ▶ 就緒

0/0

安裝

選擇你的客戶端

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

開啟 Claude Desktop → Settings → Developer → Edit Config。儲存後重啟應用。

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

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

Cursor 使用與 Claude Desktop 相同的 mcpServers 格式。專案級設定優先於全域。

VS Code → Cline → MCP Servers → Edit

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

點擊 Cline 側欄中的 MCP Servers 圖示，然後選 "Edit Configuration"。

~/.codeium/windsurf/mcp_config.json

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

格式與 Claude Desktop 相同。重啟 Windsurf 生效。

~/.continue/config.json

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

Continue 使用伺服器物件陣列，而非映射。

~/.config/zed/settings.json

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

加入 context_servers。Zed 儲存後熱重載。

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

一行命令搞定。用 claude mcp list 驗證，claude mcp remove 移除。

使用場景

實戰用法： YepCode MCP

Give Claude controlled access to internal services without exposing secrets

👤 Platform teams ⏱ ~15 min intermediate

何時使用： You want Claude to call internal systems (CRM, payment, etc.) without putting credentials in the model context.

前置條件

Server/skill installed and authenticated — See repo README

步驟

Build a YepCode process

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

→ Process available in MCP
Call from Claude

Refund order #12345 with reason 'damaged in shipping'.✓ 已複製

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

結果： Claude gets a typed, auditable interface to your internal systems — no secrets in chat.

注意事項

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

搭配使用： github

組合

與其他 MCP 搭配，撬動十倍槓桿

yepcode-mcp + github

Pair with github for complementary capabilities

Use this server together with github to complete a multi-step task.✓ 已複製

工具

此 MCP 暴露的能力

工具	輸入參數	何時呼叫	成本
list_processes	(none)	Discover what processes are exposed	free
run_process	slug, input	Execute a specific business process	Per YepCode plan

成本與限制

運行它的成本

API 配額: See provider docs for rate limits
每次呼叫 Token 數: Varies by tool
費用: See repo README for pricing details
提示: Cache tool results and avoid repeated identical calls.

安全

權限、密鑰、影響範圍

憑證儲存： Use environment variables; never commit secrets

資料出站： Tool calls go to the provider's API as documented

故障排查

常見錯誤與修復

401 Invalid API token

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

驗證： list_processes returns your processes

process failed mid-run

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

驗證： Re-run with the same input from the UI

替代方案

YepCode MCP 對比其他方案

替代方案	何時用它替代	權衡
Pipedream MCP	You want a no-code workflow builder layer	Different programming model