How to Use the YepCode MCP in Cline

Q: Can YepCode run processes inside Cline?

Yes. The runprocess tool lets your agent trigger serverless code snippets for complex automations in the cloud. It's perfect for simulating backend actions during your local development cycle.

Q: Does YepCode help me track process history with Cline?

Yep. Use listexecutions to see a log of recent runs, and getprocessdetails if you need the specifics on one failure or success. It keeps your project history clean.

Q: Can I check available teams with YepCode in Cline?

You can use the listteams tool to verify which groups are accessible through the server. This is useful when building multi-tenant components that need scope validation.

Q: What type of data does this YepCode MCP Server touch regarding data privacy?

This server touches account secrets, listed by listsecrets. When running tasks in Cline, always remember to manage those tokens securely within your project environment.

Build and test integrations with YepCode inside Cline.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect YepCode MCP to Cline

Create your Vinkius account to connect YepCode to Cline and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup YepCode with Cline

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Trigger Cloud Code Snippets

When you tell Cline to build something, it doesn't just write code; it runs the whole thing. The `run_process` tool triggers YepCode serverless snippets for backend tasks, so your component can pull live data or execute an integration step. Cline handles the result and shows you a diff, meaning you see exactly how that cloud execution affects your local project.

Inspect Existing Processes

Before writing any test code, check what's already running. The `list_processes` tool lets Cline know about all available YepCode processes. You can then get deep details on a job using `get_process_details`. This eliminates guesswork and helps you accurately scope your component build.

Manage Credentials for Testing

Testing often means needing API keys or tokens. Use the `list_secrets` tool to make sure Cline knows what credentials it can use for authentication. Seeing this list upfront saves you from dependency errors. This gives your end-to-end task execution reliable access to necessary environment variables.

Setup guide

Set up YepCode MCP in Cline

Prerequisites

VS Code with Cline extension installed
Active Vinkius subscription with a valid endpoint token

1

Open Cline MCP settings

Click the Cline icon in the VS Code sidebar to open the Cline panel. Then click the MCP Servers icon (server stack) at the top-right corner of the panel.
2

Add a remote server

Click "Remote Servers" at the top, then click "Add Remote MCP". In the Name field, type yepcode-mcp. In the URL field, paste your Vinkius endpoint: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp. Get your token from cloud.vinkius.com.
3

Enable the server

After saving, the server appears in the Cline MCP panel. Toggle the switch to enable it. The status indicator turns green when the connection is live.
4

Start using tools

Return to the Cline chat and ask: "Check my latest YepCode refund status." Cline will discover the available tools and request your approval before invoking each one — giving you full control over every action.

Cline MCP Settings

{
  "mcpServers": {
    "yepcode-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by YepCode. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect YepCode now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about YepCode MCP in Cline

You can add the server via the Marketplace tab, or if you're advanced, edit `cline_mcp_settings.json` directly under the mcpServers key. Once added, Cline immediately discovers all tools.

Yes. The `run_process` tool lets your agent trigger serverless code snippets for complex automations in the cloud. It's perfect for simulating backend actions during your local development cycle.

Yep. Use `list_executions` to see a log of recent runs, and `get_process_details` if you need the specifics on one failure or success. It keeps your project history clean.

You can use the `list_teams` tool to verify which groups are accessible through the server. This is useful when building multi-tenant components that need scope validation.

This server touches account secrets, listed by `list_secrets`. When running tasks in Cline, always remember to manage those tokens securely within your project environment.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript