Skip to content
Developers
MCP

Connect Supervisible

View Markdown

Connect Claude, Codex, ChatGPT or Cursor and check your workspace before your first task.

Use Supervisible from your assistant to plan staffing, inspect capacity, manage projects and work with permitted financial data.

MCP server URL: https://app.supervisible.com/api/mcp

You need a Supervisible account with an active membership in the workspace you want to use. Your assistant uses your existing workspace permissions. Your AI provider may require a paid plan or admin approval for custom connections.

Choose your client

Run:

claude mcp add --transport http supervisible https://app.supervisible.com/api/mcp

Open Claude Code, run /mcp, select Supervisible and finish sign-in. Select the workspace on the consent screen. See Claude Code's MCP guide for client configuration options.

Run:

codex mcp add supervisible --url https://app.supervisible.com/api/mcp
codex mcp login supervisible

Finish sign-in and workspace selection in the browser. Run codex mcp list to check the saved connection. See Codex's MCP guide for shared CLI/IDE configuration and OAuth options.

Open Customize → Connectors, select + → Add custom connector, and enter the server URL above. Finish adding the connector, then connect and sign in to Supervisible. Enable it for the conversation where you want to use it. Organization-managed accounts may need an admin to add the connector first.

Use Claude's remote connector flow rather than pasting a Cursor configuration into a desktop config file. Follow the current Claude custom connector instructions if your settings differ.

For a custom connection, enable Developer mode under Settings → Security and login. Open Plugins, select the plus button, enter the server URL above and choose OAuth when asked for authentication. Finish sign-in and workspace consent, then enable the plugin for your task.

Availability and navigation depend on your account and workspace policy. Follow OpenAI's connection quickstart for the current steps. A custom connection does not mean Supervisible has been listed in the public directory.

Add this to your project's .cursor/mcp.json, or use Cursor's MCP settings:

{
  "mcpServers": {
    "supervisible": {
      "url": "https://app.supervisible.com/api/mcp"
    }
  }
}

Connect and complete OAuth when prompted. Do not add an API key to this configuration.

Check the connection

Ask:

Use Supervisible's whoami tool. Tell me which member and workspace this connection uses. Do not change anything.

Confirm the workspace before continuing. The connection stays bound to the membership selected during consent; switching workspaces in the Supervisible app does not switch this connection.

Then try:

Show my Supervisible responsibilities and the projects I can access. Do not change anything.

You should see the projects and responsibilities available to your member. If the connection fails or the workspace is unexpected, follow the troubleshooting guide.

Make your first change

Start with a workflow example. When a tool supports preview, review its proposed changes and warnings before applying them. Commands without a preview can apply immediately; confirm their exact effect before calling them.

Read permissions and data, troubleshooting, or the tool reference. For a development server, use the separate local testing guide.

On this page