Skip to main content

Documentation Index

Fetch the complete documentation index at: https://usenaive.ai/docs/llms.txt

Use this file to discover all available pages before exploring further.

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

1

Get an API key

Register at POST /v1/auth/register or use an existing key.
2

Connect SSE

Open a connection to:
GET https://api.usenaive.ai/mcp/sse
Authorization: Bearer nv_sk_live_...
The server responds with a session event containing a sessionId.
3

Send messages

POST https://api.usenaive.ai/mcp/messages?sessionId=<session-id>
Content-Type: application/json

Client Configuration Examples

Add to claude_desktop_config.json:
{
  "mcpServers": {
    "naive": {
      "url": "https://api.usenaive.ai/mcp/sse",
      "headers": {
        "Authorization": "Bearer nv_sk_live_..."
      }
    }
  }
}

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

FeatureOriginal (@usenaive/sdk)v2 (Hosted)
Transportstdio (local process)SSE (remote)
Requires local installYes (npm i -g @usenaive/sdk)No
AuthNAIVE_API_KEY env varBearer header on SSE
Proxies throughapi.usenaive.ai → PaperclipDirect (same instance)
LatencyTwo hopsSingle hop