Skip to main content
Glama

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
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
echoA

Return the message plus the Proto-OS name to confirm the MCP session is alive.

Use as a liveness probe before mux_mount. Read-only, no network, no payment.

list_protocolsA

List protocol families this kernel can govern.

Inventory only. Mounted servers are list_mounted_servers. Read-only.

list_mounted_serversA

List MCP servers currently mounted on the in-process mux.

Use after mux_mount. Read-only.

mux_mountA

Register an empty named MCP server on the in-process mux.

Idempotent upsert. No child process, no URL. Local write only.

openapi_stubA

Return a stub MCP server derived from a caller-supplied OpenAPI title.

Offline scaffold only. Does not fetch a spec URL. Not mux_mount.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a clearly distinct target: liveness, protocol inventory, mounted-server inventory, mounting, and OpenAPI stub generation. The descriptions explicitly cross-reference differences (e.g., list_protocols points to list_mounted_servers, openapi_stub says 'Not mux_mount'), so an agent should not confuse them.

Naming Consistency2/5

Only list_protocols and list_mounted_servers follow a clear verb_noun pattern. echo is a bare verb, mux_mount is an object-first compound, and openapi_stub is a noun phrase with no verb. The names are readable but do not form a predictable naming convention across the set.

Tool Count5/5

Five tools is a well-scoped size for this focused MCP mux/kernel utility. Each tool earns its place and none feel redundant.

Completeness3/5

The set covers liveness, inventory, mounting, and stub scaffolding, but lacks an unmount/remove operation and offers no way to mount or apply the OpenAPI stub through the mounted-server lifecycle. This leaves a notable create/list-without-delete gap that could cause agent dead ends.

Maintenance

ActivityMaintained
ResponsivenessNo issues