Streamable HTTP
Streamable HTTP is the MCP transport for remote servers: the client sends each message as an HTTP POST to one endpoint, and the server can answer with a single response or a stream of events.
Updated
On this page
What it is
MCP defines how messages travel between a client and a server, called the transport. A local server can talk over standard input and output, but a server on the internet needs HTTP. Streamable HTTP uses one URL for everything: requests go up as POST bodies, and the server answers with JSON or streams several messages back when a call takes a while.
Because it is plain HTTPS, it works through normal networks and proxies, and the server can sit behind sign-in like any web API.
In Xodia
Xodia's MCP server is a remote server reached over Streamable HTTP at one address on the app's domain. In an app that asks for the transport type, choose Streamable HTTP and set sign-in to OAuth.
You never run anything on your computer to use it: the server is part of the Xodia app, and your AI app connects to it over the internet.
Read more
Related terms
- MCP (Model Context Protocol)MCP, the Model Context Protocol, is an open standard that lets an AI app connect to outside tools and data through one common interface.
- MCP OAuthMCP OAuth is how a remote MCP server signs in the person using an AI app: the app opens the server's sign-in page, you approve access, and the app gets a token it sends with every call.
- Preview deploymentA preview deployment is a temporary, private copy of a website built from a branch or pull request, so changes can be checked at a real address before they go live.