AI and agents · By Rivtor · Updated
Host a Python MCP server over Streamable HTTP
A hosted Python MCP server needs an HTTP transport, a reachable ASGI listener, the correct hostname trust configuration and deliberate authentication. A local stdio server is not a remote HTTP service; test the deployed endpoint using a client compatible with the pinned SDK.
See the Rivtor deployment workflow →
Separate local tools from a hosted endpoint
A stdio client starts a local subprocess and exchanges protocol messages through its input and output. Hosting that Python file on a server does not expose it over HTTPS. Choose the HTTP transport supported by your pinned MCP SDK and a compatible client, then configure a production ASGI serving process.
Record the SDK and protocol versions in the example project. MCP APIs and transport details have evolved; do not combine constructor arguments from different major releases. Use the official Python SDK deployment guide for the version you actually install.
Prepare the deployment contract
| Boundary | Required decision |
|---|---|
| Entrypoint | Importable ASGI app or supported SDK server command |
| Listener | Assigned port and reachable interface |
| Endpoint | The actual HTTP MCP route, not an assumed /sse path |
| Host validation | Explicit allowed production hostnames |
| Authentication | Appropriate protection for every exposed tool |
Add a separate lightweight health route. A load balancer’s GET health request is not an MCP tool call, and a healthy process does not prove a client can authenticate and invoke a tool.
Validate trust without disabling it
The Python SDK’s hostname protections can reject a newly deployed public hostname. Configure the allowed host and applicable origin rules for the installed version. Do not solve this by accepting arbitrary hosts or removing authentication. Reverse-proxy TLS termination can also affect the URL a client discovers.
On Rivtor, treat the server as a supported Python service or use a reviewed Dockerfile where needed. Inspect service overrides and confirm source dependencies are included. No special Rivtor MCP feature is required merely to host your own HTTP application.
Exercise a harmless tool first
Connect a compatible client and call a read-only synthetic tool. Record whether failures occur at routing, authentication, protocol negotiation or tool execution. Keep logs free of tokens and private tool arguments. Before exposing a mutating tool, verify its authorization boundary; a reachable MCP endpoint can otherwise become a public interface to privileged actions.