Connect through MCP

Give your Agent access to your synchronized Obelisk history with one read-only query tool.

Service URL

https://cloud.obelisk.antinomie.org/mcp

1. Add this URL as a remote Streamable HTTP MCP server in an OAuth-capable client.
2. Follow the client's browser authorization flow. Sign in with your invited GitHub account.
3. Approve history query access and return to the Agent.
4. Ask the Agent to use the query tool. Sync history from a beta client first.

Choose OAuth or an API key. With OAuth, the MCP client obtains and refreshes its own credentials. With an API key, configure your client to send Authorization: Bearer <key> and skip OAuth. Manage authorized clients at Connections.

API key setup

Create a key in Console. Set OBELISK_API_KEY in the environment of the Agent client, then configure the client to read that variable and send it as a Bearer token. Setting an environment variable alone does not configure the HTTP header; the configuration syntax depends on your client. Do not configure OAuth and an API key simultaneously.

export OBELISK_API_KEY='<your API key>'
curl 'https://cloud.obelisk.antinomie.org/mcp' \
  -H "Authorization: Bearer $OBELISK_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  --data '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"example","version":"1"}}}'

Tool input

{
  "name": "query",
  "arguments": {
    "script": "return sessions({limit: 10});",
    "context": {
      "cwd": "/work/example-project",
      "invokingSessionId": null
    }
  }
}

The tool's text content contains the exact Query API response text. Failed queries return a tool error. The service executes the original Obelisk query methods; it does not provide a hosted natural-language Agent.

Client integration

Use OAuth scope history:query and resource https://cloud.obelisk.antinomie.org/mcp. The service supports PKCE S256, client registration, refresh and revocation. Resource-specific credentials cannot be reused at /query.

The transport is stateless and uses POST with JSON responses. There is no persistent SSE stream. Browser cookies alone are not MCP credentials. Cross-origin browser clients are not supported in this beta. The SDK flow has been verified; individual desktop Agent authorization screens still need client-specific testing.

Beta limits

Sync your history before querying. Accounts without a published index receive HTTP 409. Session history and original records are supported; the separate memory stream is not synchronized. Empty memory results do not mean you have no local memories.

Requests are limited to 64 KiB and responses to 1 MiB, with a five-second execution timeout. Full query parity, Windows paths, cancellation and individual Agent client compatibility remain under verification.

Read the Query API reference for query context and response behavior.