Skip to main content
Alchemist exposes a full Model Context Protocol (MCP) server. Any MCP-compatible agent can call Alchemist’s search and document tools without writing any integration code — you just point the agent at the endpoint.

MCP endpoint

Transport: Streamable HTTP (MCP 2025 spec) Authentication — two options, both on the Authorization: Bearer header: OAuth signs you in as an existing Alchemist user, so sign in once at app.askalchemist.com before connecting. API keys come from Settings → API keys.

Available tools

Shared configs — configure once

Several agent surfaces share configuration, so you may not need to set things up more than once:
claude_desktop_config.json is not on this list. It holds local stdio servers only — a remote MCP server can’t be configured there, and claude mcp add-from-claude-desktop therefore won’t carry Alchemist into Claude Code. Add it with claude mcp add instead.

Choose your integration

Claude

Claude.ai web, Claude Desktop, and Claude Code — configure once, sync everywhere.

Cursor

Cursor IDE — one JSON block in .cursor/mcp.json.

Codex

OpenAI Codex — one command: codex mcp add --url … .

ChatGPT

ChatGPT Custom GPT Actions — REST-based, API key.

OpenAI Agents SDK

Python & JS — connect Alchemist as an MCP server in your agent.

OpenAI Responses API

Hosted mcp tool — OpenAI calls Alchemist server-side.

OpenClaw

OpenClaw personal AI assistant — OAuth via openclaw mcp add --auth oauth.

Hermes

Nous Research Hermes Agent — built-in MCP client, OAuth or API key.

Generic MCP

Any MCP-compatible client — copy-paste config and system prompt.

Manual integration (non-MCP)

If your agent doesn’t support MCP, integrate directly via the REST API: