MCP Server — 5 minute setup

Use your 50 agents from Claude, Cursor, and ChatGPT

Orbitable speaks Model Context Protocol. Wire it once, and every specialist agent shows up as a tool inside your favourite AI client.

Get an API key Jump to setup

Every agent becomes an MCP tool

Each tool is named agent_<id> and accepts a task, optional context, and an optional customer_slug that loads that customer's full universe: ICP, brand voice, products, competitors.

agent_social-listener

Reddit / Twitter monitoring, trends, competitor watch

agent_competitive-intel

Battle cards, market maps, win/loss decks

agent_cro-auditor

Website CRO audits with prioritised fixes

agent_content-writer

SEO / AEO / GEO articles

agent_customer-strategist

ICP and persona research, jobs-to-be-done

agent_gtm-motion-planner

GTM motion planning, channel mix, sequencing

+ 44 more specialists across Research, Content, Growth, Sales, Strategy, Build, Intel, Customer, Ops, and Auditors

Your connected accounts become tools as well

Connect HubSpot, Attio or Slack in Orbitable and they appear alongside the agents in the same client. Ask for the deals that have gone quiet, have an agent write the follow-up, then log it on the record without leaving the conversation. Agencies connect one account per client and every call names which one it used.

integration_connections

List connected accounts and their ids

hubspot_search

Contacts, companies, deals, tickets

hubspot_log_note

Put the brief on the record

attio_upsert_record

Create or update, matched on an attribute

slack_post_message

Deliver work where it gets reviewed

hubspot_update_record

Move a deal stage, set a property

Read-only by default if you want it that way, and these calls cost no credits.

3-step setup

Step 1

Create an API key

In Orbitable, head to Settings → API Keys, click New API key, name it (e.g. Claude Desktop laptop), and copy the value. Format: mfl_live_<64-hex>. The plaintext key is shown once — store it somewhere safe.

Step 2

Wire your client

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json on macOS or %APPDATA%\Claude\claude_desktop_config.json on Windows:

json{
  "mcpServers": {
    "orbitable": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-fetch", "https://orbitable.ai/api/mcp"],
      "env": { "MCP_AUTH_HEADER": "Bearer mfl_live_YOUR_KEY" }
    }
  }
}

Restart Claude Desktop. orbitable appears in the tools menu with all 50 agents.

Cursor

Settings → MCP → Add server. Transport HTTP, URL https://orbitable.ai/api/mcp, header Authorization: Bearer mfl_live_…

ChatGPT (custom GPT actions)

Add an action with base URL https://orbitable.ai/api/mcp and authentication type API Key → Bearer. The manifest at /api/mcp/manifest describes every tool.

Step 3

Verify with curl

bash# Public manifest (no auth)
curl https://orbitable.ai/api/mcp/manifest

# List tools (auth required)
curl -X POST https://orbitable.ai/api/mcp \
  -H 'Authorization: Bearer mfl_live_YOUR_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

# Call an agent
curl -X POST https://orbitable.ai/api/mcp \
  -H 'Authorization: Bearer mfl_live_YOUR_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
    "jsonrpc":"2.0","id":2,"method":"tools/call",
    "params":{
      "name":"agent_competitive_intel",
      "arguments":{
        "task":"Build a battle card for HubSpot vs Salesforce in mid-market.",
        "customer_slug":"my-saas-co"
      }
    }
  }'

Per-tier limits

Hit a limit? You'll get JSON-RPC error -32004 with a clear message. Upgrade or wait for next month.

Free first world

Not included

MCP calls / month

Free

Founder

Included

MCP calls / month

$89/mo

Team

Included

MCP calls / month

$349/mo

Agency

Included

MCP calls / month

$1,999/mo

Enterprise

Included

MCP calls / month

Custom

Your prompts stay private

Every MCP invocation logs tenant_id, tool_name, and outcome (success / error) for usage metering and debugging. We do not log the contents of task or arguments. Output length and duration are recorded so you can see your monthly usage. Best practice: one key per surface (laptop / desktop / shared CI runner) and rotate quarterly.

Ready to wire it up?

Get started