yepcode/mcp-server-js
by Various
MCP server that exposes YepCode processes as callable tools for AI platforms. Securely connect AI assistants to your YepCode workflows, APIs, and automations.
MCP
yepcode/mcp-server-js
Added 1 June 2026
Overview
An MCP server that exposes YepCode processes as callable tools for AI platforms. It uses the Model Context Protocol to let AI assistants securely trigger YepCode workflows, APIs, and automations. Written in TypeScript, it serves as a bridge between AI agents and YepCode's automation engine.
Best for
Best for
Developers using YepCode who want to let AI assistants trigger their workflows and automations
Use cases
- Connecting AI assistants to YepCode automations
- Exposing YepCode workflows as callable tools for LLMs
- Securing AI-triggered execution of YepCode APIs and jobs
Notes
An MCP server that exposes YepCode processes as callable tools for AI platforms. It uses the Model Context Protocol to let AI assistants securely trigger YepCode workflows, APIs, and automations. Written in TypeScript, it serves as a bridge between AI agents and YepCode’s automation engine.
43 stars on GitHub. Last updated 2026-03-17. Licensed MIT.
Use cases
- Connecting AI assistants to YepCode automations
- Exposing YepCode workflows as callable tools for LLMs
- Securing AI-triggered execution of YepCode APIs and jobs
Pros
- Lightweight TypeScript implementation adhering to the MCP standard
- Enables secure, controlled access to YepCode workflows from AI platforms
- Simple integration for developers already using YepCode
Cons
- Small community and limited adoption (43 stars on GitHub)
- Tied exclusively to the YepCode ecosystem, not general-purpose
- No evidence of extensive documentation or frequent updates
Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.
Pros
- Lightweight TypeScript implementation adhering to the MCP standard
- Enables secure, controlled access to YepCode workflows from AI platforms
- Simple integration for developers already using YepCode
Cons
- Small community and limited adoption (43 stars on GitHub)
- Tied exclusively to the YepCode ecosystem, not general-purpose
- No evidence of extensive documentation or frequent updates
Pairs with
Other entries in the index that connect to this one. Click through to see the chain.