Quickstart: connect your MCP gateway

You can be calling real tools through a single MCP endpoint in three steps: connect a server, copy your gateway URL, and add it to your client. Everything is metered on tool calls - there is no charge for the MCP servers you connect.

1. Connect an MCP server

Open Tools in the left rail. Click Browse connectors to pick an app from the catalog, or Add MCP server to paste any MCP server's URL and leave Auth on Auto-detect. The gateway connects public servers directly and, for OAuth servers, discovers sign-in and opens a popup automatically.

2. Copy your gateway URL

Every workspace gets one endpoint that exposes the union of all your connected tools, namespaced per server. Home shows yours, with a copy button:

https://mcp.fastn.dev/your-company

The bare https://mcp.fastn.dev works too: it takes your org and workspace from your sign-in. To connect only your fastn workspace (its workflows and the fastn platform tools) with no tool picker, use https://mcp.fastn.dev/fastn-workspace. Gateway API, headers, and access keys lists every URL form.

3. Add it to your client

Add the URL to your MCP client as a remote server. On first connect the client opens a browser tab where you sign in to Fastn Connect once; there is no token to paste. In Claude Code, for example:

claude mcp add --transport http fastn https://mcp.fastn.dev/your-company

Each client adds a remote server differently. Connect a client on Home has step-by-step setup for every supported client, and the next page covers the same steps. Clients that cannot sign in with OAuth take an access key instead.

That is it - your agent now sees every enabled tool from every connected server through one gateway, with governance and audit applied on every call.