Skeet MCP Streamable HTTP Support
Skeet now supports streamable stateless HTTP transport for MCP services, in addition to Server-Sent Events (SSE) and stdio. This enables modern, stateless, and scalable communication for MCP clients that support the Streamable HTTP transport.
Streamable HTTP Endpoint
- Endpoint:
https://mcp.stride.systems/mcp/<apikey> - Transport: Streamable HTTP (stateless, no session management)
- Method: All requests must use
POST - Client Compatibility: Only works with MCP clients that support stateless streamable HTTP transport (see MCP SSE Support for comparison).
This transport is recommended for new integrations and is designed for high scalability and compatibility with modern HTTP infrastructure.
Comparison: SSE vs. Streamable HTTP
| Feature | SSE (Stdio) | Streamable HTTP |
|---|---|---|
| Connection | Long-lived, stateful | Stateless, per-request |
| Method | GET (event-stream) | POST |
| Browser Support | Native | Requires compatible client |
| Scalability | Good, but stateful | Excellent, stateless |
| Endpoint Example | /ot/<apikey> | /mcp/<apikey> |
- SSE is ideal for real-time browser updates and works with stdio via supergateway.
- Streamable HTTP is ideal for stateless, scalable, and modern MCP client-server communication.
Configuration Example
Here's a basic example of configuring an MCP service with Streamable HTTP:
mcp.json
{
"mcpServers": {
"stride.systems": {
"url": "https://mcp.stride.systems/mcp/YOUR_SKEET_MCP_KEY"
}
}
}For more details about SSE transport, see the MCP SSE Support page.
Related Pages
- MCP SSE Support - Learn about Server-Sent Events transport
- MCP Stdio Support - Standard Input/Output transport configuration