Settings reference

Connect other tools with MCP servers

Publish Jira, HubSpot, GitHub, Mixpanel or any other MCP server once, and every app can use it as the colleague who opens it.

Other tools are MCP servers

In the portal: Admin, MCP servers

Most tools your colleagues work in now offer an MCP server: Jira and Confluence, HubSpot, GitHub, Mixpanel, Notion and many more. An administrator publishes such a server once, and from then on any app can use it. Apps never register an OAuth app, never build a connect screen and never see a password or token: cyantula holds the credential and makes the call on the app's behalf.

Publish a server

  1. Open Admin, MCP servers. The catalog lists servers you can publish in one click. Search it for the tool you need.
  2. Click Publish to organisation. A tool that is not in the catalog can still be added with Add by URL: paste the address its publisher documents.
  3. Pick the Account modes: personal accounts (each colleague connects their own), one company account for every app, or both, so the app owner chooses per app.
  4. Optionally limit which groups may use the server.

Where the catalog reads its entries is set under Admin, Settings, MCP servers. You do not need a source to publish a server by its address.

Tools that need their own OAuth client

Most servers let cyantula register itself when a colleague first connects. A few do not, GitHub among them. For those, cyantula says so when you publish, and you register a client with the publisher first:

  1. Publish the server. Its page in cyantula then shows the redirect URI to register.
  2. For GitHub: open github.com/settings/developers (or your organisation's settings), click New OAuth App, and paste that redirect URI as the Authorization callback URL.
  3. Copy the Client ID and a new Client secret into the server's OAuth client fields in cyantula.

Colleagues connect once

With personal accounts, every colleague authorises their own account once, under Profile, Other tools. That one connection serves every app they open, and each of them only sees what their own account may see. Somebody who has not connected yet is asked to before an app that needs the tool opens. With a company account, an administrator connects it once on the server's page instead.

Apps use it

An app owner adds the server on the app's All integrations tab, or while publishing, and deploys once. The Integrations page in the portal holds the instructions to hand a coding agent, and an agent connected to cyantula can read them itself.

A tool without an MCP server

An app can still talk to it directly. Then each colleague enters their own API key in the app, never one shared key and never the app creator's, so everybody keeps acting as themselves.