SSE Transport
The Naive MCP server uses Server-Sent Events (SSE) transport. This is a standard HTTP connection that stays open for bidirectional communication.Connecting
Client Configuration Examples
- Claude Desktop
- Cursor
- Custom Client
Add to
claude_desktop_config.json:Session Lifecycle
- Sessions are tied to the SSE connection
- When connection drops, the session ends
- Each new connection creates a new session
- Auth is validated once at connection time
Differences from Original Naive MCP
| Feature | Original (@usenaive-sdk/node) | v2 (Hosted) |
|---|---|---|
| Transport | stdio (local process) | SSE (remote) |
| Requires local install | Yes (npm i -g @usenaive-sdk/node) | No |
| Auth | NAIVE_API_KEY env var | Bearer header on SSE |
| Proxies through | api.usenaive.ai → Paperclip | Direct (same instance) |
| Latency | Two hops | Single hop |