openserverless-mcp
OfficialThis server lets you create, configure, and invoke OpenServerless serverless API endpoints (actions) via the Model Context Protocol.
action_new: Scaffold a new action with a__main__.pyand module file, optionally marking it as public or private.action_invoke: Run an existing action with optional key=value parameters.action_requirements: Add a Python library to an endpoint'srequirements.txt(skips preinstalled libraries automatically).action_add_secret: Wire a secret from.envinto an endpoint's context asctx.<SECRET_NAME>.action_add_s3: Connect an endpoint to S3, providingctx.S3_CLIENT,ctx.S3_DATA,ctx.S3_WEB, andctx.S3_PUBLIC.action_add_postgresql: Connect an endpoint to a PostgreSQL database viactx.POSTGRESQL.action_add_redis: Connect an endpoint to Redis, providingctx.REDISandctx.REDIS_PREFIX.action_add_milvus: Connect an endpoint to a Milvus vector database viactx.MILVUS.
Adds Milvus vector database to an endpoint's context as ctx.MILVUS.
Adds PostgreSQL database to an endpoint's context as ctx.POSTGRESQL.
Adds Redis cache to an endpoint's context as ctx.REDIS and ctx.REDIS_PREFIX.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@openserverless-mcpcreate a new hello world endpoint"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
openserverless mcp
An MCP server for OpenServerless. It exposes the OpenServerless action tools
(previously the @opencode-ai/plugin tools under trustable-app/tools/) over the
Model Context Protocol so any MCP-capable agent can drive them.
Tools
Tool | Description |
| Create a new API endpoint ( |
| Run |
| Add a library to an endpoint's |
| Wire a |
| Add S3 to an endpoint's context ( |
| Add PostgreSQL ( |
| Add Redis ( |
| Add Milvus vector DB ( |
| Add MongoDB ( |
The endpoint argument is either name (uses the v1 package) or package/name.
Related MCP server: anyapi-mcp-server
Working directory
All path-based tools operate on paths relative to the process working
directory: they read/write packages/<pkg>/<name>/... and .env. The server
must therefore be launched with the user's app checkout as its CWD (this is how
opencode launches type: "local" MCP servers).
Layout
src/
index.ts entrypoint — registers every tool over stdio
lib.ts shared helpers (endpoint parsing, connector injection, types)
tools/
new.ts action_new
invoke.ts action_invoke
requirements.ts action_requirements
add-secret.ts action_add_secret
add-s3.ts action_add_s3
add-postgresql.ts action_add_postgresql
add-redis.ts action_add_redis
add-milvus.ts action_add_milvus
add-mongodb.ts action_add_mongodbEach file under tools/ default-exports a Tool (defineTool({ name, config, handler }));
index.ts imports them all and registers them in a loop. To add a tool, drop a
file in tools/ and add it to the array in index.ts.
Run
Requires Node 18+ and ops on the PATH. TypeScript runs directly via tsx.
npm install
npm start # tsx src/index.ts — speaks MCP over stdioWire into opencode
Add to the app's opencode.json:
{
"mcp": {
"openserverless": {
"type": "local",
"command": ["npx", "tsx", "/path/to/mcp/src/index.ts"],
"enabled": true
}
}
}Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/apache/openserverless-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server