Getting started

This page will walk through the first setup: creating an account, registering a remote MCP server, reviewing its scan, choosing which tools to track, and publishing the MCP Tower URL to agents and catalogs.

Publish a different path

The public MCP URL you enter is the URL agents connect to, for example https://mcp.example.com/. Its path can differ from the path of your origin URL, for example https://api.example.com/v2. MCP Tower then maps one onto the other:

A request for the public path goes to the origin path, and a request below it goes below the origin path: / goes to /v2, and /receipts/abc goes to /v2/receipts/abc. The query string is kept.
The protected resource metadata of the public URL (/.well-known/oauth-protected-resource) is fetched from the metadata of the origin URL (/.well-known/oauth-protected-resource/v2). Its resource, and the resource_metadata URL in WWW-Authenticate, come back with the public URL. See Accept the public audience.
Other /.well-known/ paths, and paths under /_mcptower/, are not mapped.

Redirects (Location headers) pass back unchanged. If your server redirects to its own paths, use relative URLs or public URLs. Links in tool results are not mapped either: build public links from your own configuration, for example a PUBLIC_BASE_URL setting.

When the public path is the same as the origin path, nothing is mapped and every path passes through as it is.