MCP integrations,
built on a gateway that already ships.
MCP integrations will let your BEAR OS AI employees use the tools your business already runs on — CRMs, stores, trackers, docs — through the open Model Context Protocol. The marketplace is in active development, but the security layer it rides on is live in production today: an encrypted secrets vault, OAuth connect and refresh, per-connection scopes, and an action log recording every call — the same gateway that already publishes your content through your connected Buffer account.
The gateway is not a promise — it is in production
Encrypted secrets vault
Connection credentials are AES-GCM encrypted at rest with a master key held in the environment — plaintext tokens are never written to the database. This is the store every MCP credential will live in.
OAuth connect & refresh
State-verified authorize and callback flows with proactive token refresh near expiry and automatic refresh-and-retry on auth failures — the exact handshake MCP servers use.
Permission scopes enforced
Every connection is scope-limited at the gateway, so a caller can only perform the actions you granted. Disallowed calls are blocked and logged, not attempted.
Full action log
Every outbound call through the gateway records provider, action, status, attempts and duration — an audit trail you can already read for the live Buffer connection.
Connection health & verify
Connections track status, expiry and last error, and a verify endpoint runs a real authed call through the gateway — the "Test connection" button MCP cards will inherit.
Real traffic today
Publishing already runs through this gateway through your connected Buffer account, with webhook ingestion deduped and shared-secret-verified. MCP is an extension, not a rewrite.
Live today, and what the marketplace adds
Secure API gatewayLIVE
Encrypted vault, OAuth flows, scope enforcement, action log, connection health — shipped and carrying production publishing traffic today.
Approval-gated actionsLIVE
Content drafts already flow through an approval queue before anything publishes; that same human gate is the standing rule for future MCP write actions.
Curated MCP marketplaceCOMING
An MCP client in the worker plus a curated registry of official remote servers — pick, see permissions explained, OAuth, verify, and assign to employees. In active development.
Per-employee tool assignmentCOMING
Choose which AI employees may use each connected server, with every tool call logged and outbound writes approval-gated — the design is already enforced for today's connections.
MCP integrations FAQ
What are MCP integrations?
MCP (Model Context Protocol) is an open standard that lets AI systems connect to external tools and services — CRMs, databases, project trackers, storage — through one common protocol instead of a custom integration per tool. For BEAR OS it means your AI employees will be able to use the tools your business already runs on: a curated marketplace of official remote MCP servers you connect with OAuth, assign to specific AI employees, and monitor through a full action log.
Can I connect MCP servers to BEAR OS today?
Not yet — the MCP marketplace is in active development and labeled as coming on this page. What is live today is the layer it rides on: the secure API gateway with an AES-GCM encrypted secrets vault, OAuth connect and refresh flows, per-connection permission scopes, and an action log that records every outbound call. That gateway already carries real traffic — publishing runs through your connected Buffer account with every call logged.
How will MCP connections stay safe?
Three rules are already enforced in the shipped gateway and carry over directly. Credentials are AES-GCM encrypted at rest — plaintext tokens are never stored. Every connection is scope-limited, so an AI employee can only call what you granted, and a disallowed action is blocked and logged rather than attempted. And every tool call lands in the action log with provider, action, status and timing — while anything that writes to the outside world goes through the approval framework first.
Which MCP servers will be in the marketplace?
The curated first wave targets official remote servers from the platforms small businesses already run on — think Cloudflare, GitHub, Stripe, Shopify, HubSpot, Supabase, Notion and Linear — rather than an open free-for-all. Curation matters because these connections act on your behalf: each server ships with its permissions explained in plain language before you connect, and you choose which AI employees may use it.
What can I use instead while the marketplace is in development?
The live gateway already covers today's core integrations: Buffer for publishing across your channels, Google sign-in, and Stripe-ready billing infrastructure. Connections are managed per workspace with health status and logged calls — see API integrations for the full picture. If your stack depends on a specific MCP server, request early access and tell us which one — the first-wave list is being prioritized by real demand.
Connect your stack to your AI team.
Early access is open in waves. Tell us which MCP servers your business needs — demand sets the first-wave order.