Agent MCP Server

Fleet-wide shared rate limiter for A2A + multi-MCP deployments. Most MCP servers rate-limit inde... The agent mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 6 defined tools rather than through you.

What it actually does

Fleet-wide shared rate limiter for A2A + multi-MCP deployments. Most MCP servers rate-limit independently — a hostile agent hitting 10 MCPs gets 10x quota. This MCP is the shared counter: every MCP checks here before allowing a call. Sliding window + concurrency grants + signed enforcement attestations. By MEOK AI Labs.

Adding it to your client

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

Its toolset

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

• Well — documented API
• Production-ready — Active maintenance
• Pro — ** $99/mo — Full MCP suite + EU AI Act tracking
• Enterprise — ** $499/mo — Custom dev + SLA + Dedicated support
• Domain — Purpose
• Tier — Price

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 — Well, Production-ready, Pro and 3 more — is a fair guide to whether it matches your workflow. It is maintained by CSOAI-ORG; 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.