quickstart changedagents-and-tools/mcp-tunnels/quickstart
Nearest release: v2.1.312, published under an hour before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+3added
Lines−3removed
From line
10
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits9to this page, all time
## What you’ll build ## What you'll build
The whole hunk
from line 10, old and new numbered
/
from line 10
1010
1111This quickstart takes you from creating a tunnel to Claude calling a private MCP server through it. It uses Docker Compose with [manual](https://platform.claude.com/docs/en/agents-and-tools/mcp-tunnels/concepts#credential-provisioning) credential provisioning, which is the shortest path for local testing. For production deployments, see [Deploy with Helm](https://platform.claude.com/docs/en/agents-and-tools/mcp-tunnels/deploy-helm) or [Deploy with Docker Compose](https://platform.claude.com/docs/en/agents-and-tools/mcp-tunnels/deploy-compose).
1212
13## What you'll build
13## What you’ll build
1414
1515A two-container [tunnel stack](https://platform.claude.com/docs/en/agents-and-tools/mcp-tunnels/concepts#components) (the [proxy](https://platform.claude.com/docs/en/agents-and-tools/mcp-tunnels/concepts#components) and [cloudflared](https://platform.claude.com/docs/en/agents-and-tools/mcp-tunnels/concepts#components)) plus a sample MCP server running alongside it. When everything is running, the sample server is reachable from Claude at `https://echo.<your-tunnel-domain>/mcp` even though nothing is listening on a public port.
1616
from line 24
2424 <Step title="Create a tunnel">
2525 In the Claude Console, go to the [MCP tunnels](https://platform.claude.com/settings/workspaces/default/mcp-tunnels) page (`platform.claude.com/settings/workspaces/default/mcp-tunnels`). Each tunnel belongs to one workspace. Select the workspace you want in the workspace picker in the sidebar. Click **New tunnel** and give it a name. Leave **Set up programmatic access** off; this quickstart uses manual credential provisioning.
2626
27 After it's created, open the tunnel. Copy two values from the **Connection** section:
27 After it’s created, open the tunnel. Copy two values from the **Connection** section:
2828
2929 * **Domain** (looks like `abcd1234.tunnel.anthropic.com`)
3030 * **Token** (click the eye icon, then copy)
from line 107
107107 </Tab>
108108 </Tabs>
109109
110 Back in the Console, on the tunnel detail page, click **Add certificate** and upload `data/ca.crt` (or paste its contents). The **Needs certificate** badge next to the tunnel's name goes away.
110 Back in the Console, on the tunnel detail page, click **Add certificate** and upload `data/ca.crt` (or paste its contents). The **Needs certificate** badge next to the tunnel’s name goes away.
111111 </Step>
112112
113113 <Step title="Write the sample MCP server">
No line in this hunk matches that.