Skip to main content
The Parabola MCP is available to customers on our Advanced and Enterprise plans. If your organization is on one of these plans and you’d like access, reach out to your account manager or help@parabola.io.

​
What you can do with the Parabola MCP

🔒 Scoped to your permissions. The MCP only sees flows you have editor or viewer access to in Parabola — if you can’t see it in the app, the MCP can’t either. Org admins and content admins have the same full access through the MCP that they already have in Parabola.
Here are example questions the MCP handles well, organized by the use case they support.

​
1. Adoption, cost, and ROI visibility

Answers the questions leadership keeps asking — about who’s actually using Parabola and what the team has built.
  • Are we on track on credit usage this billing period?
  • How many of our users are actually building?
  • Our three-way match flow saves 1 hour per run at $25/hour — calculate the total dollar savings since it started running, and break it down by month if you can.

​
2. Operational health monitoring

Surfaces failing, paused, or at-risk flows across your workspace without clicking through each one.
  • Give me a health check on our Parabola workspace — anything I should be worried about?
  • Which flows have failed at least once in the last 30 days, and what’s the failure rate on each?
  • What’s our overall flow creation rate month-over-month? Are we building more or less than we did six months ago?

​
3. Coverage planning and single-point-of-failure detection

Identifies what’s at risk when someone is out, and where manual processes create fragility.
  • Sarah is out next week. Pull up the flows she owns and flag any that don’t have an automated trigger, but has run in the last 14 days.
  • Which flows in our team do not have an automated schedule?
  • Joanna is leaving the company at the end of the month. Show me her flows that have an active trigger and have run in the last 30 days — these are her production automations we need to find a new owner for before she leaves.

​
4. Discoverability and reuse before building something new

Finds existing flows and patterns before duplicating work.
  • We’re building a new reconciliation flow for a new entity — do we already have reconciliation logic I should look at?
  • Show me all flows owned by the finance/billing people (Paul, Andrew, Emory, me) with “billing” or “invoice” in the name.
  • Show me Ana’s most recently created flows — they’re probably working on something adjacent to what I’m building.

​
Server details

Server URLhttps://parabola.io/api/mcp
AuthenticationOAuth 2.0. Actions run on behalf of the authenticated user and are scoped to that user’s Parabola permissions.
TransportStreamable HTTP
Rate limitsApplied per tool, per user

​
Before you connect

These prerequisites apply regardless of which AI tool you’re connecting from:
  1. A Parabola account with access to the flows and data you want the AI to work with.
  2. Permission (or admin approval) in your AI tool to add custom MCP connectors. Most enterprise plans gate this to admins.
  3. Network reachability from the AI provider’s servers to https://parabola.io/api/mcp. Claude, ChatGPT, and Glean all broker the connection from their own cloud — not from your machine — so review your networking and firewall settings if you have strict egress policies.

​
Connect from Claude

Applies to: Claude.ai (web), Claude Desktop, Claude mobile, Cowork

​
One-time initial setup

(Likely needs to be done by an owner of the Claude account.)
  1. Click Customize → Connectors and click +
  2. Scroll down to Custom connectors and click + to add a new custom connector
  3. Name this custom connector “Parabola”
  4. Enter https://parabola.io/api/mcp and save
  5. After this, individual members can enable Parabola from their own settings.

​
Enabling the Parabola MCP

  1. Click Customize → Connectors
  2. Search “Parabola”
  3. Click to connect and complete the Parabola OAuth sign-in.
That’s it! Now you can use the Parabola MCP in Claude. 📄 Official Claude docs

​
Connect from Claude Code

Applies to: Claude Code (CLI) Unlike Claude.ai and Claude Desktop, Claude Code connects from your own machine rather than brokering through Anthropic’s cloud. There’s no one-time admin setup — each person adds the server and authenticates individually from their terminal. OAuth is always per-user; one teammate connecting does not connect it for anyone else.
Network note: Because Claude Code reaches https://parabola.io/api/mcp directly from your machine, the cloud-egress consideration in Before you connect doesn’t apply — but your local network does need to reach that URL.

​
Adding and authenticating

  1. Add the Parabola server to Claude Code: 
    claude mcp add --transport http parabola https://parabola.io/api/mcp
    By default this registers the server for the current project directory only. Add --scope user to make it available across all your projects: 
    claude mcp add --transport http --scope user parabola https://parabola.io/api/mcp
  2. Start a Claude Code session: 
    claude
  3. Authenticate by running /mcp, selecting parabola, and completing the Parabola OAuth sign-in in the browser window that opens. Then return to the terminal.
  4. Confirm the connection with claude mcp list (in the terminal) or /mcp (in a session). You should see parabola listed. That’s it! 🎉

​
For teammates

Each person needs to run both steps above — adding the server and authenticating — on their own machine, since server definitions and OAuth tokens are stored locally per user.
If you want teammates to skip the add step, run the command with --scope project instead. This writes the server definition to a .mcp.json file in the project directory that you can commit to your repo. Teammates who pull the repo inherit the server automatically and only need to run /mcp to authenticate with their own account.

​
A note on connectors vs. CLI

If you’ve already connected Parabola as a custom connector in Claude.ai, it may appear in your /mcp list inside Claude Code with a claude.ai prefix. That connector is managed in the Claude app’s settings, not the CLI — claude mcp remove won’t affect it. The steps above add a separate, CLI-managed connection.

​
Connect from ChatGPT

Applies to: ChatGPT web (and mobile, once connected on web) Plans: Business, Enterprise, Edu. Custom MCP connectors with full tool support aren’t available on Free or Plus.

​
One-time initial setup

(Likely needs to be done by an owner of the ChatGPT account.)
  1. Go to Workspace Settings
  2. Go to Apps and hit Create
  3. Enable developer mode
  4. Click New app form and hit Create
    • Name: Parabola
    • Description: Run and inspect Parabola flows from ChatGPT
    • MCP Server URL: https://parabola.io/api/mcp
    • Authentication: OAuth
  5. The app should now appear in your “Drafts”
  6. Publish this draft step so the others can use it.

​
Enabling the Parabola MCP for your ChatGPT account

  1. In ChatGPT, go to Settings → Apps
  2. Search “Parabola”
  3. Click Connect and complete the Parabola OAuth sign-in.

​
Using the Parabola MCP in chats

Start a new conversation, click +, then More, then enable the Parabola connector for this conversation. You’ll need to re-enable it in each new chat. 📄 Official OpenAI docs

​
Connect from Glean

Please contact help@parabola.io if you’d like to connect the Parabola MCP to Glean.

​
Connect from other MCP-compatible tools

Parabola’s MCP server follows the open MCP spec, so it works with any compliant client. You need three things:
  1. The server URL: https://parabola.io/api/mcp
  2. OAuth 2.0
  3. Support for Streamable HTTP

​
We want to hear from you

The Parabola MCP keeps getting better thanks to feedback from people using it. Share thoughts, questions, and ideas at help@parabola.io.
Last modified on June 16, 2026