Agent MCP Server

MCP server registry and marketplace - discover, install, activate tools on demand. The agent mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 12 defined tools rather than through you.

What it actually does

Search spans the official MCP registry, npm, and PyPI in one query, so popular servers that aren't in the official index (Microsoft @playwright/mcp, @modelcontextprotocol/server-*, mcp-server-fetch, mcp-server-git, …) all show up.

Its toolset

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

• Action — Purpose
• find_tool — Single-call discovery. Hybrid BM25 + semantic search → top match + confidence label + compact required_args + 4 alternatives. Auto-activates the
• find_tools — Batch discovery. Pass intents: [...] to discover N tools in one round-trip. Use for multi-step tasks
• get_schema — Full input_schema for a discovered tool. Only needed when the compact required_args summary isn't enough (conditional / polymorphic args)
• proxy_call — Invoke a discovered tool through agent-discover without exposing it to the host catalog. Pair with find_tool({auto_activate: false}) for huge
• list — Search the local registry by server (FTS5)
• uninstall — Remove a server
• activate — Start a server, discover its tools, expose them to the host as serverName__toolName
• deactivate — Stop a server, hide its tools
• browse — Federated search across the official MCP registry, npm, and PyPI
• status — Active servers summary (names, tool counts, tool lists)
• Core — The Core tool exposed by this server

Adding it to your client

servers on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Configuration

You will need 2 environment variables: AGENT_DISCOVER_OPENAI_API_KEY, OPENAI_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

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 — Action, find_tool, find_tools and 9 more — is a fair guide to whether it matches your workflow. It is maintained by keshrath; 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.

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.
• With 12 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Agent.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• 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.