Connect Codex, Cursor, or Claude Code

Use a user-level configuration wherever possible. The endpoint accepts a bearer PAT through the Authorization header and does not use cookies, query tokens, SSE, or browser CORS.

Codex

See the official Codex MCP guide for current client commands and configuration behavior.

Use Codex CLI 0.144.1 or newer for this setup. Version 0.143.0 can write a remote-MCP block that its own config loader rejects; upgrade before adding Elicitra rather than editing around the broken entry. Confirm with codex --version.

Set ELICITRA_MCP_TOKEN, then add this to ~/.codex/config.toml:

codex mcp add elicitra \
  --url https://elicitra.eigen.rest/api/mcp \
  --bearer-token-env-var ELICITRA_MCP_TOKEN

The equivalent ~/.codex/config.toml entry is:

[mcp_servers.elicitra]
url = "https://elicitra.eigen.rest/api/mcp"
bearer_token_env_var = "ELICITRA_MCP_TOKEN"

Restart Codex and run codex mcp list. Then open Codex, run /mcp, and make a real elicitra_get_started call before treating setup as complete. Codex reads server instructions during initialization; Elicitra keeps their first 512 characters self-contained.

Claude Code

See the official Claude Code MCP guide for current scope and transport options.

Claude Code expands environment variables in HTTP headers. Add a user-scoped entry without exposing the token to shell history:

claude mcp add-json --scope user elicitra '{"type":"http","url":"https://elicitra.eigen.rest/api/mcp","headers":{"Authorization":"Bearer ${ELICITRA_MCP_TOKEN}"}}'

Verify with claude mcp get elicitra, then open /mcp inside Claude Code.

Cursor

See the official Cursor MCP guide for current configuration locations and supported transports.

Create ~/.cursor/mcp.json with an environment-backed authorization header:

{
  "mcpServers": {
    "elicitra": {
      "type": "http",
      "url": "https://elicitra.eigen.rest/api/mcp",
      "headers": {
        "Authorization": "Bearer ${env:ELICITRA_MCP_TOKEN}"
      }
    }
  }
}

Restart Cursor from an environment that can read ELICITRA_MCP_TOKEN. Confirm the connection under Settings → Tools & MCP → Available Tools or with cursor-agent mcp list-tools elicitra. Do not place the expanded PAT in either global or project configuration.

Cursor’s header and environment-variable support has changed across releases. Elicitra only claims compatibility with client versions in the compatibility matrix after a real bearer-auth smoke test.

Verify the connection

All clients must discover exactly the tools allowed by the PAT scope: 10 tools for the read profile and 14 for full draft authoring. A read-only PAT includes elicitra_knowledge_search but must not list create/update tools, and directly calling a hidden write tool must still fail with TOOL_NOT_AVAILABLE.

Ask:

Call elicitra_knowledge_search in en-US to explain what an Elicitra scenario is. Then call elicitra_get_started and elicitra_account_info. Summarize what you can change, what you cannot change, and the safe scenario-to-campaign workflow.