Agent MCP Server

One MCP server to aggregate them all - A unified Model Context Protocol server implementation. Exposed over MCP by the agent mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

1MCP is the unified MCP runtime. 1mcp serve aggregates your MCP servers, and CLI mode adds a thinner agent-facing workflow for Codex, Claude, Cursor, and similar tool-using agents.

• Configuration sprawl: every client needs its own MCP wiring, auth choices, and filtering rules
• Agent sprawl: autonomous sessions carry too many tools and schemas into context up front
• 1mcp serve gives you one aggregated runtime in front of many MCP servers
• CLI mode lets agents discover tools progressively with instructions, inspect, and run
• Static servers can load at startup, while template servers are created from per-client or per-session context
• Presets, filters, and instruction aggregation keep the same runtime adaptable across clients and projects

Adding it to your client

The server ships on npm as @upstash/context7-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Its toolset

Everything the assistant can do here goes through one of these:

• Opt — in async loading for early HTTP listener availability when clients can reconcile capability changes
• Approach — Best for
• Contributors — The Contributors tool exposed by this server

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the agent mcp server does with a few real requests.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Agent's toolset — Opt, Approach, Contributors — is a fair guide to whether it matches your workflow. It is maintained by 1mcp-app; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.