Bring Serverless
to Windsurf
Learn how to connect YepCode to Windsurf 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 Windsurf?
Windsurf's Cascade agent chains multiple YepCode tool calls autonomously. query data, analyze results, and generate code in a single agentic session. Paste Vinkius Edge URL, reload, and all 6 tools are immediately available. Real-time tool feedback appears inline, so you see API responses directly in your editor.
- —
Windsurf's Cascade agent autonomously chains multiple tool calls in sequence, solving complex multi-step tasks without manual intervention
- —
Purpose-built for agentic workflows. Cascade understands context across your entire codebase and integrates MCP tools natively
- —
JSON-based configuration means zero code changes: paste a URL, reload, and all 6 tools are immediately available
- —
Real-time tool feedback is displayed inline, so you see API responses directly in your editor without switching contexts
YepCode in Windsurf
YepCode and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect YepCode to Windsurf 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 Windsurf
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 Windsurf 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 Windsurf
Every tool call from Windsurf 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 does Windsurf discover MCP tools?
Windsurf reads the mcp_config.json file on startup and connects to each configured server via Streamable HTTP. Tools are listed in the MCP panel and available to Cascade automatically.
Can Cascade chain multiple MCP tool calls?
Yes. Cascade is an agentic system. it can plan and execute multi-step workflows, calling several tools in sequence to accomplish complex tasks without manual prompting between steps.
Does Windsurf support multiple MCP servers?
Yes. Add as many servers as needed in mcp_config.json. Each server's tools appear in the MCP panel and Cascade can use tools from different servers in a single flow.
Server not connecting
Check Settings → MCP for the server status. Try toggling it off and on.