mcp-server-js

mcp-server-js

Enable secure, AI-driven process automation and code execution on YepCode via Model Context Protocol.

31
Stars
13
Forks
31
Watchers
2
Issues
YepCode MCP Server acts as a Model Context Protocol (MCP) server that facilitates seamless communication between AI platforms and YepCode’s workflow automation infrastructure. It allows AI assistants and clients to execute code, manage environment variables, and interact with storage through standardized tools. The server can expose YepCode processes directly as MCP tools and supports both hosted and local installations via NPX or Docker. Enterprise-grade security and real-time interaction make it suitable for integrating advanced automation into AI-powered environments.

Key Features

MCP-compliant server for YepCode integration
Secure remote and local code execution
Direct AI-accessible execution of YepCode processes
Environment variable management tools
File storage upload, download, and management APIs
Customizable authentication via API tokens and headers
Support for SSE and HTTP connections
Configurable via NPX or Docker for local deployments
Process tagging for dynamic tool exposure
Debugging support with MCP Inspector

Use Cases

Allowing AI assistants to automate and control YepCode processes
Securely executing user-provided code from AI agents in isolated environments
Dynamically exposing business workflows to AI tools through process tagging
Managing sensitive configuration and environment variables for automated jobs
Integrating custom data storage workflows accessible by AI systems
Enabling real-time log and result tracking for automated executions
Providing multi-platform compatibility with both cloud and on-premise installations
Supporting seamless AI platform integrations like Cursor or Claude Desktop
Automating scheduled or event-driven tasks initiated by AI processes
Centralizing process, code, and storage management for AI-driven applications

README

YepCode MCP Server Preview

NPM version NPM Downloads GitHub Workflow Status

Trust Score smithery badge

What is YepCode MCP Server?

An MCP (Model Context Protocol) server that enables AI platforms to interact with YepCode's infrastructure. Run LLM generated scripts and turn your YepCode processes into powerful tools that AI assistants can use directly.

Why YepCode MCP Server?

  • Seamless AI Integration: Convert YepCode processes into AI-ready tools with zero configuration
  • Real-time Process Control: Enable direct interaction between AI systems and your workflows
  • Enterprise-Grade Security: Execute code in YepCode's isolated, production-ready environments
  • Universal Compatibility: Integrate with any AI platform supporting the Model Context Protocol

Integration Guide

YepCode MCP server can be integrated with AI platforms like Cursor or Claude Desktop using either a remote approach (we offer a hosted version of the MCP server) or a local approach (NPX or Docker installation is required).

For both approaches, you need to get your YepCode API credentials:

  1. Sign up to YepCode Cloud
  2. Visit Settings > API credentials to create a new API token.

Remote Approach using SSE Server

  • If your MCP Client doesn't support authentication headers, just use the SSE server URL that includes the API Token. Use a configuration similar to the following:
typescript
{
  "mcpServers": {
    "yepcode-mcp-server": {
      "url": "https://cloud.yepcode.io/mcp/sk-c2E....RD/sse"
    }
  }
}
  • If your MCP Client supports authentication headers, you can use the HTTP server URL that includes the API Token. Use a configuration similar to the following:
typescript
{
  "mcpServers": {
    "yepcode-mcp-server": {
      "url": "https://cloud.yepcode.io/mcp/sse",
      "headers": {
        "Authorization": "Bearer <sk-c2E....RD>"
      }
    }
  }
}

Local Approach

Using NPX

Make sure you have Node.js installed (version 18 or higher), and use a configuration similar to the following:

typescript
{
  "mcpServers": {
    "yepcode-mcp-server": {
      "command": "npx",
      "args": ["-y", "@yepcode/mcp-server"],
      "env": {
        "YEPCODE_API_TOKEN": "your_api_token_here"
      }
    }
  }
}

Using Docker

  1. Build the container image:
bash
docker build -t yepcode/mcp-server .
  1. Use a configuration similar to the following:
typescript
{
  "mcpServers": {
    "yepcode-mcp-server": {
      "command": "docker",
      "args": [
        "run",
        "-d",
        "-e",
        "YEPCODE_API_TOKEN=your_api_token_here",
        "yepcode/mcp-server"
      ]
    }
  }
}

Debugging

Debugging MCP servers can be tricky since they communicate over stdio. To make this easier, we recommend using the MCP Inspector, which you can run with the following command:

bash
npm run inspector

This will start a server where you can access debugging tools directly in your browser.

YepCode MCP Tools Reference

The MCP server provides several tools to interact with YepCode's infrastructure:

Code Execution

run_code

Executes code in YepCode's secure environment.

typescript
// Input
{
  code: string;                          // The code to execute
  options?: {
    language?: string;                   // Programming language (default: 'javascript')
    comment?: string;                    // Execution context
    settings?: Record<string, unknown>;  // Runtime settings
  }
}

// Response
{
  returnValue?: unknown;                 // Execution result
  logs?: string[];                       // Console output
  error?: string;                        // Error message if execution failed
}
MCP Options

YepCode MCP server supports the following options:

  • Disable the run_code tool: In some cases, you may want to disable the run_code tool. For example, if you want to use the MCP server as a provider only for the existing tools in your YepCode account.
  • Skip the run_code cleanup: By default, run_code processes source code is removed after execution. If you want to keep it for audit purposes, you can use this option.

Options can be passed as a comma-separated list in the YEPCODE_MCP_OPTIONS environment variable or as a query parameter in the MCP server URL.

typescript
// SSE server configuration
{
  "mcpServers": {
    "yepcode-mcp-server": {
      "url": "https://cloud.yepcode.io/mcp/sk-c2E....RD/sse?mcpOptions=disableRunCodeTool,runCodeCleanup"
    }
  }
}

// NPX configuration
{
  "mcpServers": {
    "yepcode-mcp-server": {
      "command": "npx",
      "args": ["-y", "@yepcode/mcp-server"],
      "env": {
        "YEPCODE_API_TOKEN": "your_api_token_here",
        "YEPCODE_MCP_OPTIONS": "disableRunCodeTool,runCodeCleanup"
      }
    }
  }
}

Environment Management

set_env_var

Sets an environment variable in the YepCode workspace.

typescript
// Input
{
  key: string;                           // Variable name
  value: string;                         // Variable value
  isSensitive?: boolean;                 // Whether to mask the value in logs (default: true)
}

remove_env_var

Removes an environment variable from the YepCode workspace.

typescript
// Input
{
  key: string;                           // Name of the variable to remove
}

Storage Management

YepCode provides a built-in storage system that allows you to upload, list, download, and delete files. These files can be accessed from your code executions using the yepcode.storage helper methods.

list_files

Lists all files in your YepCode storage.

typescript
// Input
{
  prefix?: string;                       // Optional prefix to filter files
}

// Response
{
  files: Array<{
    filename: string;                    // File name or path
    size: number;                        // File size in bytes
    lastModified: string;                // Last modification date
  }>;
}

upload_file

Uploads a file to YepCode storage.

typescript
// Input
{
  filename: string;                      // File path (e.g., 'file.txt' or 'folder/file.txt')
  content: string | {                   // File content
    data: string;                        // Base64 encoded content for binary files
    encoding: "base64";
  };
}

// Response
{
  success: boolean;                      // Upload success status
  filename: string;                      // Uploaded file path
}

download_file

Downloads a file from YepCode storage.

typescript
// Input
{
  filename: string;                      // File path to download
}

// Response
{
  filename: string;                      // File path
  content: string;                       // File content (base64 for binary files)
  encoding?: string;                     // Encoding type if binary
}

delete_file

Deletes a file from YepCode storage.

typescript
// Input
{
  filename: string;                      // File path to delete
}

// Response
{
  success: boolean;                      // Deletion success status
  filename: string;                      // Deleted file path
}

Process Execution

The MCP server can expose your YepCode Processes as individual MCP tools, making them directly accessible to AI assistants. This feature is enabled by just adding the mcp-tool tag to your process (see our docs to learn more about process tags).

There will be a tool for each exposed process: run_ycp_<process_slug> (or run_ycp_<process_id> if tool name is longer than 60 characters).

run_ycp_<process_slug>

typescript
// Input
{
  parameters?: any;                      // This should match the input parameters specified in the process
  options?: {
    tag?: string;                        // Process version to execute
    comment?: string;                    // Execution context
  };
  synchronousExecution?: boolean;        // Whether to wait for completion (default: true)
}

// Response (synchronous execution)
{
  executionId: string;                   // Unique execution identifier
  logs: string[];                        // Process execution logs
  returnValue?: unknown;                 // Process output
  error?: string;                        // Error message if execution failed
}

// Response (asynchronous execution)
{
  executionId: string;                   // Unique execution identifier
}

get_execution

Retrieves the result of a process execution.

typescript
// Input
{
  executionId: string;                   // ID of the execution to retrieve
}

// Response
{
  executionId: string;                   // Unique execution identifier
  logs: string[];                        // Process execution logs
  returnValue?: unknown;                 // Process output
  error?: string;                        // Error message if execution failed
}

License

This project is licensed under the MIT License - see the LICENSE file for details.

Star History

Star History Chart

Repository Owner

yepcode
yepcode

Organization

Repository Details

Language TypeScript
Default Branch main
Size 834 KB
Contributors 3
License MIT License
MCP Verified Sep 1, 2025

Programming Languages

TypeScript
92.84%
JavaScript
5.38%
Dockerfile
1.78%

Tags

Topics

agent ai ai-agent ai-agents mcp-server yepcode

Join Our Newsletter

Stay updated with the latest AI tools, news, and offers by subscribing to our weekly newsletter.

We respect your privacy. Unsubscribe at any time.

Related MCPs

Discover similar Model Context Protocol servers

  • Stape MCP Server

    Stape MCP Server

    An MCP server implementation for integrating Stape with AI model context protocols.

    Stape MCP Server provides an implementation of the Model Context Protocol server tailored for the Stape platform. It enables secure and standardized access to model context capabilities, allowing integration with tools such as Claude Desktop and Cursor AI. Users can easily configure and authenticate MCP connections using provided configuration samples, while managing context and credentials securely. The server is open source and maintained by the Stape Team under the Apache 2.0 license.

    • 4
    • MCP
    • stape-io/stape-mcp-server
  • Pica MCP Server

    Pica MCP Server

    A Model Context Protocol (MCP) server for seamless integration with 100+ platforms via Pica.

    Pica MCP Server provides a standardized Model Context Protocol (MCP) interface for interaction with a wide range of third-party services through Pica. It enables direct platform integrations, action execution, and intelligent intent detection while prioritizing secure environment variable management. The server also offers features such as code generation, form and data handling, and robust documentation for platform actions. It supports multiple deployment methods, including standalone, Docker, Vercel, and integration with tools like Claude Desktop and Cursor.

    • 8
    • MCP
    • picahq/mcp
  • QuantConnect MCP Server

    QuantConnect MCP Server

    Official bridge for secure AI access to QuantConnect's algorithmic trading cloud platform

    QuantConnect MCP Server enables artificial intelligence systems such as Claude and OpenAI to interface with QuantConnect's cloud platform through an official, secure, and dockerized implementation of the Model Context Protocol (MCP). It facilitates automated project management, strategy writing, backtesting, and live deployment by exposing a comprehensive suite of API tools for users with valid access credentials. As the maintained official version, it ensures security, easy deployment, and cross-platform compatibility for advanced algorithmic trading automation.

    • 50
    • MCP
    • QuantConnect/mcp-server
  • mcp

    mcp

    Universal remote MCP server connecting AI clients to productivity tools.

    WayStation MCP acts as a remote Model Context Protocol (MCP) server, enabling seamless integration between AI clients like Claude or Cursor and a wide range of productivity applications, such as Notion, Monday, Airtable, Jira, and more. It supports multiple secure connection transports and offers both general and user-specific preauthenticated endpoints. The platform emphasizes ease of integration, OAuth2-based authentication, and broad app compatibility. Users can manage their integrations through a user dashboard, simplifying complex workflow automations for AI-powered productivity.

    • 27
    • MCP
    • waystation-ai/mcp
  • Make MCP Server (legacy)

    Make MCP Server (legacy)

    Enable AI assistants to utilize Make automation workflows as callable tools.

    Make MCP Server (legacy) provides a Model Context Protocol (MCP) server that connects AI assistants with Make scenarios configured for on-demand execution. It parses and exposes scenario parameters, allowing AI systems to invoke automation workflows and receive structured JSON outputs. The server supports secure integration through API keys and facilitates seamless communication between AI and Make's automation platform.

    • 142
    • MCP
    • integromat/make-mcp-server
  • Authenticator App MCP Server

    Authenticator App MCP Server

    Secure MCP server for AI-assisted access to 2FA codes and passwords.

    Authenticator App MCP Server provides a secure Model Context Protocol (MCP) server enabling AI agents to interact with authentication credentials, such as 2FA codes and passwords. It facilitates automated login processes for AI assistants while maintaining robust security by requiring access tokens and integrating with the Authenticator App desktop client. This solution streamlines the management of user credentials across multiple platforms and websites, ensuring seamless and secure credential retrieval by AI agents.

    • 27
    • MCP
    • firstorderai/authenticator_mcp
  • Didn't find tool you were looking for?

    Be as detailed as possible for better results