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와 조합해 10배 효율

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
호출당 토큰: 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