MCP Server
Query your contexts from any Model Context Protocol client. The Nexus MCP server exposes two read-only tools — list_contexts and query_context — over Streamable HTTP.
Endpoint
Point your MCP client at this Streamable HTTP URL.
https://q2-demo.nexus.pinecone.io/mcp
Authentication
Auth is per-caller — send one of these headers with your MCP requests. Every caller queries their own project.
  • Authorization: Bearer <nexus-jwt> — a Nexus session token (like the one used below).
  • X-Pinecone-Api-Key: pcsk_… — your Pinecone API key; the server logs in and mints a token for you. Best for a config that doesn't expire.
Claude Desktop
Claude Desktop runs local stdio servers, so bridge to the remote endpoint with mcp-remote. Paste this into your claude_desktop_config.json and restart Claude.
{
  "mcpServers": {
    "nexus": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://q2-demo.nexus.pinecone.io/mcp",
        "--header", "Authorization:Bearer ",
        "--transport", "http-only"
      ]
    }
  }
}
The token above is this console session and will eventually expire. For a durable config, swap the Authorization header for X-Pinecone-Api-Key:pcsk_YOUR_KEY.
Tools
  • list_contexts — list the contexts available to your project (each has a slug; only curated contexts are queryable).
  • query_context — ask a natural-language question scoped to one context. Args: context (slug), question, optional timeout_seconds.
Egress blocked? Allowlist q2-demo.nexus.pinecone.io in your client's network settings, then retry.