The Research MCP server is a hosted MCP endpoint that lets MCP-aware clients call Caesar’s API-key authenticated research endpoints as tools. It is distinct from the Docs MCP server, which only answers documentation questions.
Looking for documentation search? See the MCP Docs Server.
Pass your Caesar API key as a Bearer token in the Authorization header.
Add the research MCP server to your OpenCode config under mcp (see the OpenCode MCP docs):
Set your API key in the environment:
Add a remote MCP server in mcp.json (see Cursor MCP docs):
Set your API key in the environment:
Use the CLI to add the remote HTTP server with your API key (see Claude Code MCP docs):
Set your API key in the environment before running the command:
Add the server in ~/.codex/config.toml (see Codex MCP docs):
Set your API key in the environment:
Add the HTTP server with the CLI (see Droid MCP docs):
Set your API key in the environment before running the command:
The MCP server mirrors the existing research endpoints and exposes them as tools.
Use research_file_upload with base64-encoded content:
Every tool accepts an optional api_version argument to set the API-Version header when calling the underlying endpoint.