Connect Remote Clients
Point Claude and custom clients at your URL.
Connect Remote Clients is a free MCP Academy lesson on CoddyKit — lesson 4 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the MCP Academy learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.
Time to Go Live
Your server is built, proxied, and healthy. Now real clients connect to it over the internet using its public URL. 🌍
Clients Need a URL
Remote clients no longer launch a local process. Instead you hand them the server's public URL, usually ending in your /mcp endpoint.
https://mcp.example.com/mcpPoint Claude at the URL
In a host like Claude, you register a remote server by giving its URL instead of a command, so the host connects over HTTP.
{ "url": "https://mcp.example.com/mcp" }Send the Auth Token
A protected server expects an access token. Clients attach it in an Authorization header on every request they send.
Authorization: Bearer YOUR_TOKENCustom Clients Use the URL Too
Your own Python client connects the same way: open a streamable HTTP session against the remote URL rather than spawning stdio.
streamablehttp_client("https://mcp.example.com/mcp")The Handshake Still Happens
Remote or local, the connection begins with the same initialize handshake where client and server agree on version and features.
Discovery Works Remotely
After connecting, the client lists tools, resources, and prompts over the network exactly as it would for a local server.
Mind the Latency
Network hops add delay that local stdio never had. Expect a little latency and design tools so a slow call does not stall the user.
Handle Dropped Links
The internet is flaky, so connections drop. A good client will reconnect and resume rather than failing the whole session.
Verify End to End
Confirm the full path works: client to proxy to server and back. A successful tool result proves the deployment is truly live. ✅
One Server, Many Clients
The big payoff of going remote is sharing: one hosted server can serve teammates, agents, and apps all at once.
Quick Check
How does a remote client connect to your deployed MCP server?
Recap: Remote Clients
Remote clients connect to your public URL with an auth token, run the same handshake and discovery, and let one server serve many. 🎉
Frequently asked questions
Is the “Connect Remote Clients” lesson free?
Yes — the full text of “Connect Remote Clients” is free to read here on the web, and the MCP Academy course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the MCP Academy course, upgrade to CoddyKit PRO.
What will I learn in “Connect Remote Clients”?
Point Claude and custom clients at your URL. You practise MCP Academy with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start MCP Academy?
No prior experience is required. MCP Academy on CoddyKit is structured for beginners through advanced learners; this is — lesson 4 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “Connect Remote Clients” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this MCP Academy lesson?
Yes. Every MCP Academy lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.
All lessons in this course
- Package the Server in Docker
- Run Behind a Reverse Proxy
- Health Checks & Restarts
- Connect Remote Clients