MetaMCP Admin MCP

An MCP server for administering MetaMCP instances — manage servers, namespaces, endpoints, and API keys across multiple MetaMCP deployments from any MCP client.

This is not the MetaMCP proxy (which aggregates tools). This is an admin tool that lets AI agents manage MetaMCP itself: add/remove servers, create namespaces, toggle tools, compare instances, and more.

Features

• Multi-instance: Manage multiple MetaMCP deployments from a single MCP server
• Full CRUD: Create, read, update, delete servers, namespaces, endpoints, and API keys
• Bulk import: Import servers in Claude Desktop JSON format
• Cross-instance ops: Compare servers across instances, clone server configs between instances
• Health checks: Verify connectivity to all instances
• Tool management: Inspect tools per server, toggle tools/servers within namespaces

Available Tools (22)

Tool	Description
list_instances	List all configured MetaMCP instances
health_check	Check connectivity to all instances
compare_instances	Compare servers/namespaces/endpoints across instances
list_servers	List all MCP servers on an instance
get_server	Get server details by UUID
create_server	Create a new MCP server
update_server	Update an existing server
delete_server	Delete a server
bulk_import_servers	Import servers from Claude Desktop JSON format
clone_server	Copy a server config from one instance to another
list_namespaces	List all namespaces
get_namespace	Get namespace details with servers
create_namespace	Create a new namespace
update_namespace	Update a namespace
delete_namespace	Delete a namespace
get_namespace_tools	List tools in a namespace
toggle_server_in_namespace	Enable/disable a server in a namespace
toggle_tool_in_namespace	Enable/disable a specific tool in a namespace
list_endpoints	List all endpoints
get_endpoint	Get endpoint details
create_endpoint	Create a new endpoint
delete_endpoint	Delete an endpoint
list_api_keys	List all API keys
create_api_key	Create a new API key
delete_api_key	Delete an API key
get_server_tools	List tools for a specific server

Installation

npm install -g metamcp-admin-mcp

Or clone and build:

git clone https://github.com/danielrosehill/metamcp-admin-mcp.git
cd metamcp-admin-mcp
npm install
npm run build

Configuration

Single instance

export METAMCP_BASE_URL="http://localhost:12008"
export METAMCP_INSTANCE_NAME="desktop"          # optional
export METAMCP_SESSION_COOKIE="better-auth.session_token=..."  # from browser

Multiple instances

export METAMCP_INSTANCES='[
  {
    "name": "desktop",
    "baseUrl": "http://localhost:12008",
    "sessionCookie": "better-auth.session_token=..."
  },
  {
    "name": "vm",
    "baseUrl": "https://mcp.example.com",
    "sessionCookie": "better-auth.session_token=..."
  }
]'

Getting the session cookie

MetaMCP uses Better Auth for session management. To get your session cookie:

1. Open MetaMCP in your browser
2. Open DevTools (F12) → Application → Cookies
3. Copy the better-auth.session_token value
4. Use it as sessionCookie in config (prefix with better-auth.session_token=)

Claude Desktop / Claude Code config

{
  "mcpServers": {
    "metamcp-admin": {
      "command": "node",
      "args": ["/path/to/metamcp-admin-mcp/dist/index.js"],
      "env": {
        "METAMCP_INSTANCES": "[{\"name\":\"desktop\",\"baseUrl\":\"http://localhost:12008\",\"sessionCookie\":\"better-auth.session_token=...\"}]"
      }
    }
  }
}

How it works

MetaMCP exposes a tRPC API for its admin frontend. This MCP server acts as a tRPC client, calling those same endpoints with session cookie authentication. This means you get the same capabilities as the MetaMCP web UI, but accessible from any MCP client.

API Coverage

Built against the MetaMCP tRPC API:

• frontend.mcpServers.* — Full CRUD + bulk import
• frontend.namespaces.* — Full CRUD + tool/server status management
• frontend.endpoints.* — Full CRUD
• frontend.apiKeys.* — Create, list, delete
• frontend.tools.* — Query by server

License

MIT