MetaMCP Admin MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| METAMCP_BASE_URL | No | The base URL of the MetaMCP instance (e.g., http://localhost:12008) | |
| METAMCP_INSTANCES | No | JSON array of MetaMCP instances for multi-instance management | |
| METAMCP_INSTANCE_NAME | No | Optional name for the MetaMCP instance | |
| METAMCP_SESSION_COOKIE | No | The session cookie for authentication (format: better-auth.session_token=...) |
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 |
|---|---|
| list_instancesC | List all configured MetaMCP instances |
| list_serversA | List all MCP servers on a MetaMCP instance |
| get_serverB | Get details of a specific MCP server by UUID |
| create_serverC | Create a new MCP server on a MetaMCP instance |
| update_serverC | Update an existing MCP server |
| delete_serverB | Delete an MCP server from a MetaMCP instance |
| bulk_import_serversB | Bulk import MCP servers (Claude Desktop JSON format) |
| list_namespacesC | List all namespaces on a MetaMCP instance |
| get_namespaceB | Get namespace details including its servers |
| create_namespaceC | Create a new namespace |
| update_namespaceC | Update an existing namespace |
| delete_namespaceC | Delete a namespace |
| get_namespace_toolsC | List tools available in a namespace |
| toggle_server_in_namespaceB | Enable or disable a server within a namespace |
| toggle_tool_in_namespaceC | Enable or disable a specific tool within a namespace |
| list_endpointsC | List all endpoints on a MetaMCP instance |
| get_endpointC | Get endpoint details |
| create_endpointC | Create a new endpoint exposing a namespace |
| delete_endpointD | Delete an endpoint |
| list_api_keysB | List all API keys on a MetaMCP instance |
| create_api_keyC | Create a new API key |
| delete_api_keyC | Delete an API key |
| get_server_toolsB | List tools registered for a specific MCP server |
| compare_instancesB | Compare MCP servers across all configured MetaMCP instances |
| health_checkA | Check connectivity to all configured MetaMCP instances |
| clone_serverC | Copy an MCP server config from one instance to another |
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 26 tools
Tools are clearly partitioned by resource type (servers, namespaces, endpoints, api_keys, instances) with distinct action verbs preventing overlap. Minor density exists between get_namespace and list_namespaces, but descriptions clarify that one retrieves detailed server membership while the other provides a simple listing.
Excellent adherence to snake_case with a strict verb_noun pattern throughout all 26 tools (create_server, delete_namespace, list_api_keys, etc.). Compound verbs like bulk_import_servers and health_check follow the same convention without mixing styles or cases.
With 26 tools, the surface exceeds the typical ideal range (3-15) and enters the heavy category (16-25+). While each tool earns its place covering full CRUD for four distinct resource types plus specialized operations (clone, toggle, import), the breadth creates a dense interface that approaches cognitive overload.
Provides comprehensive lifecycle coverage for servers and namespaces, including granular controls like toggling specific tools. Minor gaps exist for endpoints (missing update_endpoint) and API keys (lacking get single key), though these can be worked around via list operations.