OpenRAG MCP — Final Release Notice

This package (openrag-mcp) has been retired.

OpenRAG now ships a built-in Model Context Protocol server over streamable HTTP — no subprocess, no separate install, no API key in a subprocess env block. Connect your MCP client directly to your running OpenRAG instance.

The last published version of openrag-mcp on PyPI is the final release. No further updates will be made to this package.

Migrating to streamable HTTP

The OpenRAG backend exposes an MCP endpoint at /mcp using the streamable-HTTP transport. Any MCP client that supports "url"-based server configs (Cursor, Claude Desktop, and the MCP SDK) can connect to it directly.

Prerequisites

• A running OpenRAG instance (v0.3.0 or later)
• An OpenRAG API key — create one in Settings → API Keys

Cursor

Config file: ~/.cursor/mcp.json

Standard API key:

{
  "mcpServers": {
    "openrag": {
      "url": "https://your-openrag-instance.com/mcp",
      "headers": {
        "X-API-Key": "orag_your_api_key_here"
      }
    }
  }
}

IBM auth (when IBM_AUTH_ENABLED=true on the server):

{
  "mcpServers": {
    "openrag": {
      "url": "https://your-openrag-instance.com/mcp",
      "headers": {
        "X-Username": "your_ibm_username",
        "X-Api-Key": "your_ibm_api_key"
      }
    }
  }
}

Restart Cursor after saving the config.

Claude Desktop

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

Standard API key:

{
  "mcpServers": {
    "openrag": {
      "url": "https://your-openrag-instance.com/mcp",
      "headers": {
        "X-API-Key": "orag_your_api_key_here"
      }
    }
  }
}

IBM auth:

{
  "mcpServers": {
    "openrag": {
      "url": "https://your-openrag-instance.com/mcp",
      "headers": {
        "X-Username": "your_ibm_username",
        "X-Api-Key": "your_ibm_api_key"
      }
    }
  }
}

Restart Claude Desktop after editing the file.

Available tools

All tools are auto-exposed from the /v1/ API and are available immediately after connecting:

Why streamable HTTP?

• No subprocess — your MCP client connects over HTTP; nothing to install or spawn locally.
• Full tool surface — document ingestion, task tracking, and knowledge filters are available from day one (previously listed as "coming later" in the stdio package).
• One auth model — the same API key or IBM credentials you use for the REST API work for MCP.
• Self-hosted and secure — the /mcp endpoint is part of your OpenRAG deployment; nothing leaves your network.

License

Apache 2.0 — see LICENSE for details.