Fathym
Menu
fAIOpenXThe LoopHolonicAboutDocsBlogLog in to OpenX
Docs menu

OpenX MCP Server

This page answers what the OpenX MCP server is, where to point a client, and what a connected AI can and cannot do. The pages under it are the reference: connecting, the tools, the resources, the prompts, errors and limits, and recipes.

What it is

OpenX runs one official MCP server for your workshop. MCP (the Model Context Protocol) is the open standard AI clients use to call tools and read resources. Any MCP client can connect: Claude, ChatGPT, Cursor, a coding agent, or a model you run yourself. Azi uses the same kind of connection.

Where it lives

Give your client this address, also shown in APIs -> OpenX MCP Server in the workspace:

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

That address reaches all your workspaces, and you pick one each time you sign in. Each workspace also has its own address, https://openx.fathym.com/ox-api/mcp/w/<workspace id>, whose connection can only ever reach that workspace. An MCP key works only on that workspace address. Your workspace id is the ID shown in Workspace -> Settings. See Connecting.

Reading and building

A connected AI reads your workshop as you: the stored workspace, what exists in your cloud, how each part is doing, and the read-only routes of the OpenX api your access allows. It can also build, by proposal: it proposes a data connection, a surface or a warm query, and a person accepts it in the workspace portal. There is no accept tool over MCP, by design, so an AI connected from outside never accepts its own proposals. Any workspace member can accept a proposal; some changes (access, licences, connected-app requests) need a management right. Accepting is not deploying, and builds nothing in the cloud.

What a kind needs before it can be proposed (a cloud connection, then a private landing zone) is in get_workspace, under Capabilities.InactiveKinds; see Environment for the order.

Outside the workspace identity mode

The server uses your OpenX team sign-in. It is not affected by the API identity mode set for a workspace, so changing that mode does not change what an MCP connection can do.

Where to go next

  • Connecting: sign in through the browser, or use an MCP key.
  • Tools: the full list of tools, with inputs and examples.
  • Errors and limits: what a 401 means and how long a connection lasts.
  • Connect a client: step-by-step setup for each client.
On this page