Userorbit MCP server

Connect Userorbit to Claude, Codex, ChatGPT, Cursor, and other MCP-compatible clients. Once connected, an AI assistant can work with feedback, announcements, roadmaps, help-center articles, contacts, tours, demos, surveys, checklists, workflows, and support conversations using your existing Userorbit permissions.
Remote MCP server URL
https://api.userorbit.com/mcptext

Use the hosted server unless your client specifically requires a local stdio integration.

Before you start

You need:
  • A Userorbit account with access to the workspace you want to connect.
  • An MCP-compatible client.
  • Permission to add custom connectors in that client. Team and enterprise clients may require an owner or administrator.

Only connect Userorbit to AI clients you trust. The client can access the workspace and scopes you approve.

Choose an access level

The authorization screen shows the scopes requested by your client:
  • Read — View and search workspace data. This is the best choice for analysis, reporting, summaries, and Q&A.
  • Write — Create, update, publish, archive, and delete workspace content. This is optional.

Start with read access. Leave write access disabled unless you intend to make changes from the AI client. You can revoke a connection at any time from Settings → Connected Apps in Userorbit.

Connect Claude

  1. Open Claude and go to Settings → Connectors.
  2. Select Add connector → Add custom connector.
  3. Enter Userorbit as the name.
  4. Enter https://api.userorbit.com/mcp as the remote MCP server URL.
  5. Select Add, then Connect.
  6. In the browser authorization window, choose a Userorbit workspace and the scopes you want to grant.
  7. Select Authorize.

After the browser reports that the connection succeeded, return to Claude. If the connector screen still shows the previous state, close and reopen Connectors; Claude refreshes the status when the view is reopened.

Connect Codex

In the Codex desktop app:
  1. Open Settings → MCP servers.
  2. Select Add server.
  3. Choose Streamable HTTP.
  4. Enter Userorbit as the name and https://api.userorbit.com/mcp as the URL.
  5. Save, authenticate, and complete the Userorbit authorization flow.
  6. Restart Codex or begin a new task so the new tools are loaded.

You can also configure the shared Codex connection from a terminal:
codex mcp add userorbit --url https://api.userorbit.com/mcp
codex mcp login userorbitBash

Connect ChatGPT

If custom connectors are enabled for your ChatGPT account or workspace:
  1. Open Settings → Connectors or Apps.
  2. Add a custom MCP connector.
  3. Enter Userorbit as the name and https://api.userorbit.com/mcp as the server URL.
  4. Choose OAuth authentication.
  5. Connect and approve the Userorbit workspace and scopes.

The exact menu labels depend on your ChatGPT plan and workspace settings. An administrator may need to enable custom connectors first.

Connect Cursor, Claude Code, or another MCP client

Clients that support remote OAuth can connect directly to:
https://api.userorbit.com/mcptext

Claude Code can add the hosted server with:
claude mcp add --transport http userorbit https://api.userorbit.com/mcpBash

For clients and CI environments that support bearer authentication, you can use a Userorbit API key:
Authorization: Bearer YOUR_USERORBIT_API_KEYhttp

If the API key belongs to more than one workspace, also send x-team-id with the target workspace ID.

What you can ask Userorbit to do

Read-only examples:
  • “Summarize the most common feedback themes from this month.”
  • “List the announcements published this quarter.”
  • “Find help-center articles about onboarding.”
  • “Show unresolved support discussions and group them by topic.”
  • “Analyze tour performance and identify the largest drop-off.”

Examples that require write access:
  • “Create a feedback item from these interview notes.”
  • “Draft a help-center article, but do not publish it.”
  • “Move this feedback item to planned.”
  • “Publish the approved announcement.”

For important or destructive changes, review the proposed action before approving it in your AI client.

Tool permissions and approval prompts

Userorbit labels read-only tools separately from tools that can change data. This lets MCP clients allow safe list, search, and detail requests without treating them as destructive operations.
Compatibility tools that combine multiple actions remain available for existing integrations. Because those tools can also update or delete content, an MCP client may request approval even when the selected action is read-only. New prompts should prefer the read-only tool shown by the client.
When your client shows Current workspace summary, prefer it for routine orientation. The detailed workspace tool remains available for diagnostics.

Disconnect or revoke access

To revoke the Userorbit authorization:
  1. In Userorbit, open Settings → Connected Apps.
  2. Find the AI client connection.
  3. Select Revoke.

You can also remove or disconnect Userorbit from the connector settings in the AI client. Revoking in Userorbit invalidates its access and refresh tokens.

Troubleshooting

The browser says connected, but the connector screen has not updated

Close the connector detail screen and reopen it. If Userorbit appears in a new chat and can return the current workspace, the connection succeeded and the old screen was only stale. If it still appears disconnected, update or relaunch the desktop client and reconnect.

The authorization request expired

Authorization requests expire after a short period. Return to the AI client and start the connection again.

A write action is unavailable

The connection probably has read-only access. Reconnect Userorbit and explicitly enable the Write scope, or authorize a separate connection for write operations.

A read action asks for approval

Ask the assistant to use the read-only Userorbit tool for that resource. Existing compatibility tools can contain both read and write actions, so clients may treat the whole compatibility tool as sensitive.

Codex does not show the new tools

Start a new Codex task or restart the app after adding or authenticating the server. Existing tasks do not always reload MCP tools dynamically.

The MCP URL returns “Method not allowed” in a browser

This is expected. The MCP endpoint accepts protocol requests over HTTP POST; opening it directly in a browser sends a GET request.

Was this helpful?