Skip to main content
Glama
apache

openserverless-mcp

Official
by apache

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
action_newA

Create a new API endpoint. Creates the action folder with main.py and module file.

action_invokeB

Invoke an API action. Executes ops action invoke with the given endpoint and key=value parameters.

action_requirementsB

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 S3 connection to an endpoint's context. Provides ctx.S3_CLIENT, ctx.S3_DATA, ctx.S3_WEB, ctx.S3_PUBLIC.

action_add_postgresqlC

Add PostgreSQL connection to an endpoint's context. Provides ctx.POSTGRESQL.

action_add_redisB

Add Redis connection to an endpoint's context. Provides ctx.REDIS and ctx.REDIS_PREFIX.

action_add_milvusB

Add Milvus vector DB connection to an endpoint's context. Provides ctx.MILVUS.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 8 tools

Disambiguation5/5

Each tool targets a unique purpose: adding specific connection types (Milvus, PostgreSQL, Redis, S3, secret), creating a new action, invoking an action, or adding a library requirement. There is no overlap in functionality, and the descriptions clearly distinguish each tool's role.

Naming Consistency4/5

All tools use a consistent 'action_' prefix and snake_case, but the verb structure varies: some include a noun after 'add' (e.g., action_add_milvus), while others lack a noun (action_invoke, action_new, action_requirements). This minor inconsistency prevents a perfect score, but the pattern is still predictable.

Tool Count5/5

With 8 tools, the set is well-scoped for a server focused on managing OpenServerless actions. It covers creation, invocation, dependency management, and integration with external services without being overwhelming or too sparse.

Completeness3/5

The tool surface covers core action creation and invocation, along with adding various connections and dependencies. However, it lacks tools for deleting, updating, or listing actions, as well as removing connections or secrets. These gaps could hinder agents needing full lifecycle management.

Maintenance

ActivityMaintained
ResponsivenessNo issues