Log inSubmit server
Metatool App logo

Metatool App

by metatool-ai

Aggregates MCP servers into configurable namespaces and exposes them through unified authenticated endpoints.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Metatool App

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "metatool-ai-metatool-app": {
      "command": "uvx",
      "args": [
        "mcp-hn"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

uvx mcp-hn

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 25d ago.

Overview

metatool-ai/metatool-app MCP server aggregates configured MCP servers into a unified MCP endpoint with namespaces, transport options, and access controls. It can start STDIO-based servers, expose aggregated endpoints over SSE or Streamable HTTP, and provide OpenAPI endpoints for compatible clients. Use it when you need to compose several MCP servers, select or rename tools, inspect configurations, or centralize authentication. Docker Compose is the recommended deployment path, with local development and VS Code/Cursor Dev Container options also documented.

Use cases

  • Aggregate several MCP servers behind one endpoint
  • Group tools into namespaces for different agent workflows
  • Inspect and debug saved MCP server configurations
  • Expose composed MCP services over SSE or Streamable HTTP
  • Centralize authentication for hosted MCP endpoints

Key features

  • Namespace-based MCP server aggregation
  • STDIO server configuration and secret references
  • SSE and Streamable HTTP endpoints
  • Tool filtering, overrides, and annotations
  • Built-in MCP endpoint inspector
  • API-key and OAuth authentication

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

30/34 checks healthy over the last 78d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9d ago via OSV.dev · mcp-hn (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars2.7kStargazers on the source repository.
Last commit4mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How Metatool App works

What metatool-ai/metatool-app MCP server does

metatool-ai/metatool-app MCP server acts as a proxy and aggregation layer for MCP infrastructure. It stores configurations for connected MCP servers, groups them into namespaces, and emits each namespace through one or more endpoints. A namespace can contain multiple servers, and individual servers or tools can be enabled or disabled.

The system is intended for teams or developers that want to host dynamically composed MCP servers rather than configure every upstream server separately in each agent client. It also provides a graphical interface for managing connections and saved server configurations.

How it works

A server configuration tells MetaMCP how to launch an upstream MCP server. STDIO examples use a command and argument list, such as starting a server with uvx. Connected servers are grouped into namespaces. Namespace settings can control which tools are available, apply request or response middleware, and change tool names, titles, descriptions, or MCP annotations.

Endpoints are assigned to namespaces. The tools from all enabled servers in the selected namespace are then presented through the endpoint as one MetaMCP server. Supported MCP transports include SSE and Streamable HTTP. The project also documents OpenAPI endpoints for clients such as Open WebUI.

Middleware operates at namespace scope and can intercept or transform MCP requests and responses. The documented built-in example filters inactive tools to reduce the tool context exposed to language models. The Inspector provides saved server configurations and can be used to examine MetaMCP endpoints.

Setup and configuration

Docker Compose is the recommended way to run metatool-ai/metatool-app MCP server. The repository also documents development with Dev Containers in VS Code or Cursor, plus local development. Deployment details, configuration examples, and connection instructions are provided in the project documentation at docs.metamcp.com.

STDIO server environment values can be supplied directly, referenced with ${ENV_VAR_NAME}, or passed through automatically when the expected variable name matches a variable in the MetaMCP container. Referencing container variables keeps secret values out of the server configuration and repository. For local Docker development with pnpm run dev:docker, variables may also need to be listed in turbo.json under globalEnv.

Endpoints support API-key authentication through a header or query parameter, as well as standard OAuth from MCP specification version 2025-06-18.

Tools and capabilities

  • Aggregate multiple MCP servers behind one endpoint.
  • Organize servers into namespaces and switch the namespace assigned to an endpoint.
  • Enable or disable servers and individual tools.
  • Edit tool names, titles, descriptions, and namespace-specific annotations.
  • Apply namespace-level middleware to MCP requests and responses.
  • Inspect endpoints using saved server configurations.
  • Expose endpoints through SSE, Streamable HTTP, or documented OpenAPI routes.
  • Configure API-key or OAuth authentication.

Limitations and notes

Some capabilities described by the project are future work rather than current functionality. Tool logging, error tracing, validation, scanning, and Elasticsearch-style tool selection are listed as future ideas or coming-soon use cases.

The server is infrastructure for composing and exposing MCP services; the usefulness of a namespace depends on the upstream MCP server configurations supplied to it. Clients that only support STDIO require the documented connection approach, while HTTP-capable clients can connect to the corresponding endpoint transport.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Metatool App

metatool-ai/metatool-app is an MCP server that connects configured upstream MCP servers into namespaces and unified endpoints. Its main tools and capabilities include aggregating MCP tools, filtering or overriding them, applying middleware, inspecting saved configurations, and exposing services through SSE or Streamable HTTP with authentication.

Use Docker Compose, which the project recommends for running the server. The repository also documents Dev Containers for VS Code or Cursor and a local development setup. Refer to the project documentation and repository instructions for the deployment files and development commands.

Yes, Cursor is explicitly documented as a client and as an environment for Dev Container development. Cursor can connect to a MetaMCP endpoint using the connection configuration described in the repository.

Use the repository's STDIO connection approach for Claude Desktop. The README specifically documents connecting Claude Desktop and other STDIO-only clients, including API-key authentication troubleshooting where applicable.

Yes, it can expose aggregated namespaces through SSE or Streamable HTTP endpoints. The project also documents OpenAPI endpoints for clients such as Open WebUI, alongside API-key and OAuth authentication options.

Related MCP servers

All in Aggregators All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMetatool App AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/metatool-ai-metatool-app?style=directory)](https://allmcps.com/mcp/metatool-ai-metatool-app)
HTML Embed
<a href="https://allmcps.com/mcp/metatool-ai-metatool-app"><img src="https://allmcps.com/api/badge/metatool-ai-metatool-app?style=directory" alt="Metatool App on AllMCPs" /></a>