Fathym
Menu
fAIOpenXThe LoopHolonicAboutDocsBlogLog in to OpenX
Docs menu

MCP: Claude.ai

Claude.ai connects to a remote MCP server as a custom connector. It signs in with OAuth, so you sign in with OpenX in the browser and there is no key to generate, store, or rotate.

Steps and button names below are from Anthropic's own help article, checked 2026-10-13. Menu labels are as of that date and may change; if one differs on your screen, follow Anthropic's article.

What you need

  • A Claude plan that allows custom connectors: as of 2026-10-13 Anthropic lists Free (limited to one custom connector), Pro, Max, Team and Enterprise.
  • Claude connects from Anthropic's cloud, not from your device. The OpenX address is public, so nothing needs allowing on your side.
  • On Team and Enterprise, an organization owner adds the connector first (see below).

The address

https://openx.fathym.com/ox-api/mcp

To pin the connection to one workspace, use the workspace form instead: <origin>/ox-api/mcp/w/<workspace id>. The transport is Streamable HTTP.

Connect (Pro and Max)

  1. Go to Customize > Connectors.
  2. Click + Add, then Add custom connector.
  3. Enter a name, such as OpenX.
  4. Enter the server address above and click Continue.
  5. Review the detected authentication settings and click Continue. Leave Authentication on a sign-in choice; you do not need a key.
  6. Click Add.
  7. Find OpenX in the connector list and click Connect. Your browser opens the OpenX sign-in. Sign in, pick the workspace, and tick the rights to share with the connection.

Connect (Team and Enterprise)

  1. An owner goes to Organization settings > Connectors, clicks Add, hovers over Custom, and selects Web.
  2. The owner enters the name and server address, then adds the connector, as in steps 3 to 6 above.
  3. Each member goes to Customize > Connectors, finds OpenX, and clicks Connect to sign in with their own OpenX account.

Use it in a chat

Click the + at the lower left of the chat, choose Connectors, and switch OpenX on. Then ask: "What were the average signups per hour today?" Claude calls call_api against your saved source of truth. To build, it proposes with manage_proposals, and you accept in the portal. Every tool is listed in OpenX MCP Server tools.

If you would rather paste a key

Anthropic's form has a Request headers section for servers that do not use OAuth. For OpenX, prefer the browser sign-in: a connector configured with an Authorization header returns 401 once the key is revoked or reaches the end of its lifetime, instead of falling back to the browser sign-in. If you do use a key, open APIs -> OpenX MCP Server, mint an MCP key for this workspace, and paste it as the value of an Authorization header:

Authorization: Bearer <YOUR_JWT_TOKEN>

A key works only on its workspace's own address, so set the connector's URL to https://openx.fathym.com/ox-api/mcp/w/<workspace id>; on the all-workspaces address it is refused. Your workspace id is the ID shown in Workspace -> Settings.

A key from APIs -> API Keys is a team key for the REST API, and the MCP server does not take one. Never put the key in the server address. How each way works is on Connecting to the OpenX MCP Server.

Remove or change it

To change a connector, remove it (the three dots next to it, or Remove) and add it again.

On this page