MCP Tower documentation

MCP Tower shows how AI agents use your MCP servers. It is a hosted proxy that sits between AI agents (ChatGPT, Claude, Perplexity, Copilot and others) and your remote MCP server. You publish the MCP Tower URL instead of your server’s own. Every request passes through to your server, and MCP Tower records what happened, without an SDK and without a change to your server’s code.

Recording an event never blocks or breaks the request it records: if analytics has a problem, your traffic still reaches your server.

How the docs are organized

• Get started covers registering your first MCP server and publishing its MCP Tower URL.
• Setup covers protecting your origin server, so it only accepts requests that come through MCP Tower.
• OAuth checks explains each check MCP Tower runs when it scans a server that uses OAuth, and what to do when one fails.

What MCP Tower does

1. Tool-call analytics and live stream: which agents call which tools, how often, how fast and with what errors, and a live view of calls as they happen.
2. Widget interaction tracking: widgets that agents render report clicks and form submissions.
3. Link-click tracking: links in tool responses are tracked, so you learn which ones users open.
4. Health monitoring: checks that your server answers and each tool responds, even without traffic.
5. Marketplace submission kit: catalog answers you write once and reuse, plus the manifest file for OpenAI’s upload flow.

Questions the docs don’t answer yet? Contact us.