How connectors work
Connect a provider once — with OAuth or an API key — and BusinessMCP exposes it as a set of namespaced agent tools. github_read_file, gsc_query, slack_post_message, shopify_recent_orders, zendesk_recent_tickets — each is discoverable and callable by the Assistant, by any external agent on your MCP endpoint, and by the CLI. You write no integration code; we handle auth, schemas and dispatch.
The catalog
Open Connections to browse the catalog by category. Highlights:
- Code & ops — GitHub (read + PR writes), GitLab, Vercel, Sentry, Linear, Notion, Airtable.
- Revenue — Stripe (via its hosted MCP server), PayPal.
- E-commerce & support — Shopify, Zendesk, Intercom.
- CRM & sales — HubSpot, Pipedrive, Calendly.
- Marketing & analytics — Search Console, Mailchimp, Klaviyo, PostHog, Plausible, DataForSEO.
- Messaging — Slack (read + post), Resend (email).
- Social & ads — X, LinkedIn, TikTok, YouTube, Instagram, Facebook, Meta Ads, Google Ads (one-click white-label OAuth).
- Enrichment — built-in IP→company identification (in-house graph, no vendor needed) + People Data Labs firmographics.
New providers are added continuously; a few (Salesforce, Xero, QuickBooks, GA4, Google Calendar) are OAuth-only and marked "connect coming soon."
Support conversations: Intercom and Crisp
The Intercom and Crisp cards work the other way round from the rest of the catalog: they receive webhooks, they call no API and expose no agent tools. Every conversation lands on the customer's contact timeline and in the CRM Inbox — the customer's messages as inbound bubbles, your team's replies as outbound ones, a note when the conversation is closed — so the whole history of a person sits in one place. Replies stay in Intercom or Crisp: we never draft an answer for a support message and never move a contact's pipeline stage because they asked a question.
Setup is the same for both:
1. Open Connections → Support, expand the card and paste the signing secret — Intercom's app Client secret (Developer Hub → your app → Basic information), or the secret Crisp shows when you add a Web Hook (Settings → Websites → your site → Web Hooks). Connect.
2. Copy the webhook URL that now appears on the card (https://businessmcp.com/api/webhooks/intercom/… or …/crisp/…). It is unique to your workspace.
3. Register that URL in the tool. Intercom: subscribe to conversation.user.created, conversation.user.replied, conversation.admin.replied and conversation.admin.closed. Crisp: enable message:send, message:received and session:set_email.
Every delivery is verified against the secret (unsigned or wrongly signed requests are rejected) and replays are ignored. A conversation attaches to a contact only when the tool tells us the person's email — Intercom sends it with the opening message, Crisp sends it as a separate session:set_email event once the visitor types it in. Anonymous chats are counted on the card ("without an email") and not stored; a workspace teammate chatting with your own widget is skipped too. Optionally, Settings → Support widget → "Learn from support conversations" also files the transcripts into the company brain as untrusted, contact-PII knowledge so the analyst and Inbox drafts know what customers actually ask. It is off by default.
Required, recommended, supplementary
The catalog is tiered. Required is just the tracking script. Recommended are high-value first-party integrations (Stripe, GitHub, Search Console, the social/ads set, enrichment). Supplementary is the long tail — connect what you actually use. Onboarding recommends connectors based on your goals.
Where tokens live
Credentials are stored server-side in a per-workspace vault with deny-all row-level security. The agent calls the tool; the token is injected at execution and never returned to the model. Output is additionally scrubbed by the caller's access policy, so a scoped key can be blocked from revenue or PII even on a connector that returns it.
Custom & external MCP servers
Already run an MCP server, or want to connect one of the thousands that exist? BusinessMCP acts as a gateway: attach any external MCP server by URL and it becomes reachable through your one endpoint. See Connect a custom MCP server.
Frequently asked questions
Where are my API keys and OAuth tokens stored?
Server-side, encrypted in a per-workspace vault with deny-all row-level security. Agents call the tool; they never see the credential. You can revoke any connection at any time.
Do connectors change my dashboard analytics?
No. Connectors are tool-layer only — they give the Assistant, your MCP endpoint and the CLI new tools to call. They do not alter your first-party analytics, reports or KPIs, which come from the tracking script.
Keep going
Turn your company into one AI-ready data platform on a single hosted MCP endpoint.