Fathym
Menu
fAIOpenXThe LoopHolonicAboutDocsBlogLog in to OpenX
Docs menu

MCP: Lovable

Lovable can add a custom MCP server as a chat connector, with OAuth as its default authentication. You sign in with OpenX in the browser and there is no key to store.

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

What to know first

  • Lovable says custom MCP servers are available on all plans.
  • The connection is personal to you, and teammates add the server with their own sign-in.
  • It gives context in the project chat and in Chats. It does not run inside your published app. Lovable's page says a published app that must call a service at runtime needs a different route.
  • A workspace admin can turn custom MCP servers off. If MCP server is greyed out, that is why.

The address

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

To pin the connection to one workspace, use <origin>/ox-api/mcp/w/<workspace id>. The transport is Streamable HTTP. Lovable's page does not name the transports it supports; it asks only for the server URL of an MCP server it can reach.

Connect

  1. Open Connectors and select the + button at the top right of the catalog. Choose MCP server.
  2. Enter a Server name, such as OpenX.
  3. If a Connection dropdown appears, leave it on Direct connection. The OpenX address is public.
  4. Enter the Server URL above.
  5. Leave authentication on OAuth (default).
  6. Click Add & authorize. Sign in with OpenX, pick the workspace, and tick the rights to share with the connection.

Check it

Ask Lovable something OpenX can answer, such as "What were the average signups per hour today?" Lovable calls call_api against your saved source of truth. To build, it proposes with manage_proposals, and you accept in the portal.

If you would rather paste a key

Lovable's authentication choices include Bearer token or API key, for servers without OAuth. For OpenX, prefer the browser sign-in: a connector configured with a key 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 bearer token:

Bearer <YOUR_JWT_TOKEN>

A key works only on its workspace's own address, so set the server 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.

Change it

The connection type is fixed when you add the server. To switch, remove the server and add it again.

On this page