LEARN // MCP
What is an MCP transport
An MCP transport is the channel that carries messages between your MCP client and a server. With stdio, your client starts the server as a local process and they exchange JSON messages over standard input and output. With Streamable HTTP, the server lives at a URL and your client sends each message as an HTTP request.
A draft compile is from $0.05, and new accounts start with $5 of usage.
- Messages: JSON-RPC 2.0 on every transport
- stdio: a local process, no port
- Streamable HTTP: a URL, local or remote, OAuth sign-in
- Spatial Compiler: hosted over HTTP, local over stdio
01 // HOW IT WORKS
stdio and Streamable HTTP
Every transport carries the same JSON-RPC 2.0 messages, so a tool behaves the same over either one. With stdio, which needs the least setup, the client launches a command, writes requests to its input and reads replies from its output. Nothing listens on a port, and the server runs only while the client keeps it open.
Streamable HTTP puts the server behind one URL. The client posts each request, and the server answers with a single response or streams several messages back as server-sent events. It works across the network, supports OAuth sign-in, and replaced the older HTTP plus SSE transport in the 2025 versions of the spec.
02 // IN YOUR PROJECT
Where ports come in
Engine MCP servers often add a hop the protocol leaves open: the server talks to a plugin inside your editor over a local WebSocket or TCP port. When a connection fails, check that hop first. The editor must be open, the plugin running, and the port in the plugin must match the one the server expects. A firewall or a second editor on the same port can block it.
03 // SPATIAL COMPILER
Spatial Compiler's two transports
The hosted server at https://spatialcompiler.dev/mcp uses HTTP, with a browser sign-in. The local server, npx -y @applied-manifold/spatial-compiler, uses stdio: your client starts it with SPATIAL_API_KEY set, and it forwards every call to the hosted API. Neither opens a port on your machine or needs an editor plugin. See Install via MCP.
What is the difference between stdio and Streamable HTTP MCP transports?
Use stdio for a server running on your machine and Streamable HTTP for a remote server at a URL.
Which port does an engine MCP server use?
Each editor plugin chooses its own port in settings. Over stdio the MCP link uses no port, only the plugin connection does.
How do I troubleshoot a broken MCP connection?
Restart the client and check its MCP log. Test local commands manually, redo browser sign in for HTTP and confirm the editor plugin is running.
Is an MCP transport the same as a REST API?
No. A REST API exposes endpoints for direct code calls, while an MCP transport carries protocol messages for agents to discover and call tools.
Compile your first effect
You pay per compile and see the price before it runs. New accounts start with $5 of usage.