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.

INSTANT PLUG AND PLAY

YepCode MCP Server for VS Code CopilotGive VS Code Copilot instant access to 6 tools to Get Process Details, List Executions, List Processes, and more

Name: YepCode
Availability: InStock
Author: Vinkius

Built by Vinkius GDPR 6 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Use with Your AI Agent

Ask AI about this App Connector for VS Code Copilot

Open in ChatGPT Open in Claude Open in Perplexity

The YepCode app connector for VS Code Copilot is a standout in the Ship It category — giving your AI agent 6 tools to work with, ready to go from day one.

Vinkius delivers Streamable HTTP and SSE to any MCP client

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install YepCode and 3,400+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

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

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

About 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.

GitHub Copilot Agent mode brings YepCode data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 6 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

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.

The YepCode MCP Server exposes 6 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 6 YepCode tools available for VS Code Copilot

When VS Code Copilot connects to YepCode through Vinkius, your AI agent gets direct access to every tool listed below — spanning serverless, workflow-automation, data-integration, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.

get_process_details

Get details for a specific process

list_executions

List recent process executions

list_processes

List YepCode processes

list_secrets

List account secrets

list_teams

List available teams

run_process

Trigger a process execution

Connect YepCode to VS Code Copilot via MCP

Follow these steps to wire YepCode into VS Code Copilot. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using YepCode

Ask Copilot: "Using YepCode, help me...". 6 tools available

Why Use VS Code Copilot with the YepCode MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with YepCode through the Model Context Protocol.

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

YepCode + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the YepCode MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Example Prompts for YepCode in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with YepCode immediately.

"Show me all available processes in my YepCode account."

"Run the 'Data Export' process with the parameter { "format": "csv" }."

"Check the status of my recent process executions."

Troubleshooting YepCode MCP Server with VS Code Copilot

Common issues when connecting YepCode to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

YepCode + VS Code Copilot FAQ

Common questions about integrating YepCode MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.