openserverless-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| action_newA | Create a new API endpoint. Creates the action folder with main.py and module file. |
| action_invokeA | Invoke an API action and return its JSON result. Executes |
| action_requirementsA | Add a library to an endpoint's requirements.txt. Skips if the library is preinstalled. |
| action_add_secretB | Add a secret to an endpoint's context. The secret must exist in .env. |
| action_add_s3A | Add a bucket-scoped S3 connection to an endpoint's context. Provides ctx.S3_CLIENT, ctx.S3_DATA, ctx.S3_WEB, ctx.S3_PUBLIC. Never call list_buckets; verify read/write with put_object, get_object plus content comparison, and delete_object in ctx.S3_DATA. |
| action_add_postgresqlA | Add PostgreSQL connection to an endpoint's context. Provides ctx.POSTGRESQL. |
| action_add_redisA | Add Redis to one endpoint as ctx.REDIS and ctx.REDIS_PREFIX. For authenticated pages, every login/registration, me/session, protected-resource, and logout endpoint must be wired; use auth_setup to configure the complete set atomically. Authentication uses opaque random tokens stored server-side in prefix-safe Redis keys with a bounded TTL, never JWT or an application signing secret. |
| action_add_milvusA | Add Milvus vector DB connection to an endpoint's context. Provides ctx.MILVUS. |
| action_add_mongodbB | Add MongoDB connection to an endpoint's context. Provides ctx.MONGODB_CLIENT and ctx.MONGODB. |
| secret_statusA | Report whether a secret exists and is bound to selected endpoints without reading or returning its value. |
| secret_bindA | Atomically bind one existing .env secret to multiple OpenServerless endpoints as ctx.. |
| secret_unbindA | Atomically remove one generated secret binding from multiple OpenServerless endpoints without deleting the secret value. |
| auth_setupA | Atomically add Redis session wiring to the complete authentication surface: token issuers (login/registration), token validators (me/session and every protected resource), and logout. This tool never reads or writes .env. Generated auth must use bcrypt password verification plus a cryptographically random opaque token stored as a prefix-safe ctx.REDIS_PREFIX key with a bounded TTL; protected endpoints derive identity from Redis and logout deletes the record. JWT and application signing secrets are forbidden. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Most tools are clearly separated by integration target or resource: Milvus, S3, Postgres, Redis, MongoDB, secret status/bind/unbind, invoke, and auth setup. The main overlap is between action_add_secret and secret_bind, which both attach existing .env secrets to endpoint contexts; their descriptions clarify single vs. multi-endpoint scope, but the boundary could still cause misselection.
The action_ and secret_ prefixes create a readable grouping, and action_add_* is used consistently for integration setup. However, action_new and action_requirements break the verb_noun pattern, and action_add_secret sits awkwardly alongside the secret_* family, making the naming somewhat mixed though still understandable.
With 13 tools, the server is well scoped for an OpenServerless configuration platform. Each tool covers a distinct setup, invocation, secret-management, or auth task, and there are no obvious filler or redundant tools.
The set covers creating and invoking endpoints, adding dependencies and data connections, managing secret bindings, and setting up auth. However, there are notable gaps: no way to list, update, or delete endpoints, and no way to remove an added integration or connection, which can leave agents in dead ends.