Bring Serverless
to Claude Code
Learn how to connect YepCode to Claude Code and start using 6 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the YepCode MCP Server?
Connect your YepCode account to any AI agent and simplify how you automate complex data integrations and serverless workflows through natural conversation.
What you can do
- Process Control — List and trigger serverless processes with custom parameters directly from your agent.
- Execution Monitoring — Track the history and status of your workflow runs to ensure reliability.
- Secret Management — List and verify account secrets used in your automations without exposing values.
- Team Coordination — Query available teams and workspaces to understand your development environment.
How it works
1. Subscribe to this server
2. Enter your YepCode API Key
3. Start running and monitoring your serverless automations from Claude, Cursor, or any MCP client
Who is this for?
- DevOps Engineers — quickly trigger maintenance workflows or data syncs via simple AI commands.
- Data Analysts — monitor the status of recurring ETL processes and verify secret availability.
- Software Developers — test and run serverless functions during the development cycle without leaving the IDE.
Built-in capabilities (6)
Get details for a specific process
List recent process executions
List YepCode processes
List account secrets
List available teams
Trigger a process execution
Why Claude Code?
Claude Code registers YepCode as an MCP server in a single terminal command. Once connected, Claude Code discovers all 6 tools at runtime and can call them headlessly. ideal for CI/CD pipelines, cron jobs, and automated workflows where YepCode data drives decisions without human intervention.
- —
Single-command setup:
claude mcp addregisters the server instantly. no config files to edit or applications to restart - —
Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks
- —
Claude Code runs headlessly, enabling unattended batch processing using YepCode tools in cron jobs or deployment scripts
- —
Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features
YepCode in Claude Code
YepCode and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect YepCode to Claude Code through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for YepCode in Claude Code
The YepCode MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 6 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Code only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
YepCode for Claude Code
Every tool call from Claude Code to the YepCode MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I provide input parameters when running a process?
Yes, the run_process tool accepts an optional JSON object for parameters, allowing you to pass dynamic data to your serverless functions.
How do I check if a process execution failed?
Use the list_executions query. It will return a history of recent runs along with their final status (e.g., success, error, pending).
Is it possible to see the code of my processes via AI?
Yes, you can use the get_process_details tool to retrieve the complete metadata and code configuration for any specific process ID.
How do I add an MCP server to Claude Code?
Run claude mcp add --transport http "" in your terminal. Claude Code registers the server and discovers all tools immediately.
Can Claude Code run MCP tools in headless mode?
Yes. Claude Code supports non-interactive execution, making it ideal for scripts, cron jobs, and CI/CD pipelines that need MCP tool access.
How do I list all connected MCP servers?
Run claude mcp in your terminal to see all registered servers and their status, or type /mcp inside an active Claude Code session.
Command not found: claude
Ensure Claude Code is installed globally: npm install -g @anthropic-ai/claude-code
Connection timeout
Check your internet connection and verify the Edge URL is reachable