Fathym
Menu
fAIOpenXThe LoopHolonicAboutDocsBlogLog in to OpenX
Docs menu

MCP: Perplexity

Perplexity can add a custom remote MCP connector. Its form offers three authentication choices: none, API key, and OAuth 2.0. For OpenX, choose OAuth 2.0 so you sign in through the browser.

Steps and button names below are from Perplexity'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 Perplexity's article.

What you need

  • A Perplexity account that can add custom connectors. The article does not list plan tiers; it describes the feature as one managed in Enterprise settings for organizations and says individual users can add remote connectors to their own account.
  • In an organization, members can add connectors only if an admin has turned on Allow members to add custom connectors, which is off by default. Admins can add and share connectors with the whole organization.
  • HTTPS is required for the server address. The OpenX address is HTTPS.

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, which is one of the two transports Perplexity's form offers (the other is SSE).

Connect

  1. Open Account settings > Connectors. (An admin adding it for an organization opens Enterprise settings > Permissions > Connectors permissions.)
  2. Click + Custom connector in the top-right corner.
  3. In the window that opens, select Remote.
  4. Enter a Name, such as OpenX, and the MCP Server URL above.
  5. Set Transport to Streamable HTTP, and Authentication to OAuth 2.0.
  6. Tick the box that confirms you understand the risks of custom connectors.
  7. Click Add. The connector appears on the Connectors screen.
  8. Click the connector card to start the sign-in and enable it. Sign in with OpenX, pick the workspace, and tick the rights to share with the connection.

For an organization-wide connector, the person who created it must also share it from the permissions screen before other members can use it.

If Perplexity asks for a Client ID and Client Secret, that is what its article says happens when a server does not support dynamic client registration. Its redirect URL for registering a client is https://www.perplexity.ai/rest/connections/oauth_callback.

Use it

Ask in a Perplexity thread: "What were the average signups per hour today?" Perplexity 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

Perplexity's Authentication choices include API Key, a static key supplied during setup. 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 this as its value:

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

Use the ellipsis on the connector card to change or remove it.

On this page