Skeet MCP SSE Support

Skeet provides native support for Server-Sent Events (SSE) as its primary mechanism for remote-hosted MCP services. This real-time communication protocol enables efficient, one-way communication from your MCP services to clients, making it ideal for streaming updates and continuous data flow.

Overview

Server-Sent Events offer several advantages for MCP implementations:

• Real-time Updates: Receive instant updates from your MCP services
• Efficient Resource Usage: Maintains a single connection for multiple events
• Native Browser Support: Works out of the box with modern web browsers
• Automatic Reconnection: Built-in retry mechanism for connection failures

SSE Endpoint

• Endpoint: https://mcp.stride.systems/ot/<apikey>
• Transport: Server-Sent Events (stateful, long-lived connection)
• Method: GET (event-stream)
• Browser Support: Native support in modern browsers
• Use Case: Ideal for real-time browser updates and continuous data streaming

Configuration Example

Here's a basic example of configuring an MCP service with SSE:

{
  "mcpServers": {
    "skeetbuild": {
      "url": "https://skeet.sh/ot/YOUR_SKEET_MCP_KEY"
    }
  }
}

For more details about stdio support, see the MCP Stdio Support page.

Related Pages

• MCP Streamable HTTP Support - Learn about stateless HTTP transport
• MCP Stdio Support - Standard Input/Output transport configuration

Additional Resources

• SSE Specification
• Skeet MCP Documentation
• Model Context Protocol
• MCP Stdio Support