freemcplab / Directory / Playground / YepCode MCP

● Official yepcode ⚡ Instant

YepCode MCP

Name: YepCode MCP MCP Server
Author: yepcode

Expose YepCode processes (serverless Node/Python jobs) as Claude tools.

YepCode is a hosted serverless platform that runs versioned Node/Python jobs with secrets, schedules, and HTTP triggers. This MCP turns each of your YepCode processes into a callable tool — so Claude can call your real backend logic without raw HTTP.

▶ Watch demo 📦 Install 💡 Use Cases

Why use it

Key features

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

Live Demo

What it looks like in practice

yepcode-mcp.replay ▶ ready

0/0

Install

Pick your 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"
      ]
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

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

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

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit

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

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

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

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json

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

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json

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

Add to context_servers. Zed hot-reloads on save.

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

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use YepCode MCP

Give Claude controlled access to internal services without exposing secrets

👤 Platform teams ⏱ ~15 min intermediate

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

Prerequisites

Server/skill installed and authenticated — See repo README

Flow

Build a YepCode process

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

→ Process available in MCP
Call from Claude

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

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

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

Pitfalls

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

Combine with: github

Combinations

Pair with other MCPs for X10 leverage

yepcode-mcp + github

Pair with github for complementary capabilities

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

Tools

What this MCP exposes

Tool	Inputs	When to call	Cost
list_processes	(none)	Discover what processes are exposed	free
run_process	slug, input	Execute a specific business process	Per YepCode plan

Cost & Limits

What this costs to run

API quota: See provider docs for rate limits
Tokens per call: Varies by tool
Monetary: See repo README for pricing details
Tip: Cache tool results and avoid repeated identical calls.

Security

Permissions, secrets, blast radius

Credential storage: Use environment variables; never commit secrets

Data egress: Tool calls go to the provider's API as documented

Troubleshooting

Common errors and fixes

401 Invalid API token

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

Verify: list_processes returns your processes

process failed mid-run

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

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

Alternatives

YepCode MCP vs others

Alternative	When to use it instead	Tradeoff
Pipedream MCP	You want a no-code workflow builder layer	Different programming model

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills