Every tool speaks a different language
A contact in Salesforce isn't a contact in HubSpot. Your agent has to learn ten shapes just to answer one question.
The Company Brain for teams that run on AI agents.
Your agents are only as good as what they can reach. Company Brain gives every agent live, governed access to the tools your company already runs on, powered by the RouteMCP integration engine.
SourcesCompany Brain
RouteMCP
normalize
route
govern
the state of play
$9.1B
the spend is arriving whether the plumbing is ready or not
40%
every one of them needs to reach real systems
73%
not the model. the connection to everything else
0
Pass-through by default. Sync to your own database when you need it.
Four layers between your agents and everything they need to know.
Your agents sit at the top. Your platforms sit at the bottom. Everything in between is handled, so nothing in between is yours to build.
RouteMCP runs ityou build it
L4
Your agentsBrain layer
Whatever you build on top: support copilots, revenue agents, internal tools. They think. Company Brain gives them something to think about.
L3
Company BrainMemory layer
A live, shared view of what your company knows right now. Not a vector copy from last week, the actual current state, assembled on request.
L2
RouteMCPPipe layer
Governed actions flow back out. Create the refund, update the CRM, post the message, all scoped, logged, and reversible.
L1
RouteMCPData layer
One normalized schema over every connected tool. Your agents read a customer, an invoice, a ticket the same way, no matter which system it lives in.
SalesforceStripeKekaQuickBooksGmail+17 more
One server. Three steps. Every tool your agents touch.
/ setup≈ 10 minutes
- 1
Point RouteMCP at your tools
Connect the systems your company already runs on. OAuth, done in minutes. Live access from day one, sync later if you want it.
- 2
Drop one server into your agent
Add a single MCP server to your agent config. That is the whole install. Every connected tool shows up as callable context.
- 3
Your agents get a memory
They read live state and take governed actions across everything, through one normalized interface. No glue code per tool.
~/.config/agent/mcp.json
$ cat ~/.config/agent/mcp.json
{
"mcpServers": {
"routemcp": {
"command": "npx",
"args": ["@routemcp/mcp-server"],
"env": {
"ROUTEMCP_KEY": "cb_live_••••••••"
}
}
}
}connected · 47 tools available
The model was never the hard part. The connection was.
Teams do not fail to ship agents because the reasoning is weak. They fail at the seam between the agent and everything the company already runs on.
Reading is only half the job
Most layers let agents look but not touch. Real work means acting, and that's a second brittle pipeline to own.
Auth quietly becomes your problem
Tokens, scopes, refresh flows, rate limits. None of it is the product you set out to build. All of it lands on your team.
Speaks every platform your agents touch.
22 deeply-normalized connectors, full read and write. One field name across every provider: contact.email works on Salesforce, HubSpot & Zoho identically.
SalesforceHubSpot
Zoho CRM
Pipedrive
LeadConnector
Monday CRM
FreshBooksQuickBooks OnlineXeroZoho Books
Google CalendarSalesforceHubSpotZoho CRMPipedriveLeadConnectorMonday CRMFreshBooksQuickBooks OnlineXeroZoho BooksGoogle Calendar
Cal.com
CalendlyGmailSlack
Google Drive
Google Docs
PostgreSQL
SupabaseGitHubNotionJiraCal.comCalendlyGmailSlackGoogle DriveGoogle DocsPostgreSQLSupabaseGitHubNotionJirathe wedge nobody else has
First-class LeadConnector, Cal.com & Supabase.
The tools most integration layers quietly skip. We treat them as deeply as Salesforce, same unified schema, same full read and write, no second-class endpoints.
LeadConnectorCal.comSupabase6
CRM
Salesforce · HubSpot · Zoho CRM · Pipedrive · LeadConnector · Monday CRM
4
Accounting
FreshBooks · QuickBooks Online · Xero · Zoho Books
3
Calendar
Google Calendar · Cal.com · Calendly
2
Communication
Gmail · Slack
2
Docs & storage
Google Drive · Google Docs
2
Database
PostgreSQL · Supabase
New connectors ship every week. Need one that is not here yet?
Request a connectorLive by default. Stored only when you choose it.
Company Brain is pass-through by default for agent reads. Access is live, scoped, and logged. Choose to sync a system into your own database, and it stays inside the same governance boundary.
01
Pass-through by default
Agent reads happen live. Company Brain fetches from the source system and hands the answer straight to your agent, with nothing copied on that path. Sync a system into your own database whenever you want a persistent copy instead.
02
Scoped access
Every connection is least-privilege by default. Grant an agent exactly the objects and actions it needs, revoke in one click, and nothing leaks past the boundary you set.
03
Past legal in days
Pass-through by default keeps the review narrow, and synced data stays inside the same scopes and audit trail. Teams clear procurement and legal in days, not the quarter it usually takes to approve a new data vendor.
live proof
audit-trail · governed actionslive
READsalesforce · contactslive
WRITEhubspot · dealsscoped
READsupabase · orderslive
READgmail · admin.settingsout of scope
WRITEgithub · issuesscoped
Give agents reach without giving up control.
Autonomy and oversight are not a trade-off. Every agent operates inside boundaries you draw, and everything it does is visible and reversible.
Full audit trail
Every read and every action an agent takes is logged with who, what, and when. Replay any decision, hand your auditor a clean record, prove exactly what happened.
audit log1,248 events
agent-07readSalesforce · contacts
maya@acmeexportinvoices-q3.csv
agent-07writeHubSpot · deal #4821
agent-03readpayroll · salaries
File-level boundaries
Set access at the object, not the account. An agent can see open invoices without seeing salaries, touch one workspace and never another.
agent-07 requests access
Open invoicesallowed
Payroll · salariesblocked
Workspace · Salesallowed
Workspace · Legalblocked
Monitor and correct
Watch agent behaviour in real time and step in when you need to. Pause a connection, tighten a scope, or roll back an action without redeploying anything.
agent-07 · bulk update · 240 dealsrunning
PauseRoll back
Built for teams shipping agents into real work.
support & revops
Teams automating the busywork
Support and revenue ops building agents that resolve tickets, update the CRM, and reconcile payments across a stack that never quite talked to itself.
fintech & regulated
Teams that answer to auditors
Fintech and regulated companies that need agent reach without a new data-copying vendor in every security review. Pass-through by default keeps that review narrow, and sync stays inside the same governance boundary when you use it.
overlooked platforms
Builders on overlooked rails
Teams running on LeadConnector, Cal.com, and Supabase, the platforms global integration layers overlook. Company Brain treats them as first-class, not an afterthought.
Live by default. Synced only where you choose.
the usual stack
Company Brain
01Data model
the usual stackRaw per-tool APIs, ten schemas to learn
Company BrainOne normalized schema across every tool
02Actions
the usual stackReads only, or a second system for writes
Company BrainGoverned read and write in one interface
03Your data
the usual stackCopies everything into their warehouse, no live option
Company BrainLive by default, sync only the systems you choose
04Auth & tokens
the usual stackYour team owns every OAuth flow
Company BrainHandled, scoped, and rotated for you
05Overlooked platforms
the usual stackLeadConnector, Cal.com, Supabase rarely supported
Company BrainFirst-class connectors, not an afterthought
06Security review
the usual stackA quarter to approve a data vendor
Company BrainDays, live by default and governed if you sync
Builders who tried it do not go back.
from our private beta, onboarding the first 100 teams
01fintech · india
“We were about to stitch Merge and Composio together ourselves. RouteMCP saved us three weeks and two subscriptions. One config line and our agent had Salesforce and Razorpay as tools.”
Arjun M.
CTO, Fintech startup
02saas · singapore
“The unified schema is the real unlock. We write agent logic once, and it works whether our customer runs HubSpot or Zoho. Field names just match. I didn't believe it until I tested it.”
Priya S.
Founding Engineer, AI-native SaaS
03series a · sf
“Zero data storage isn't just a feature, it's what got us past legal. We can put RouteMCP in front of enterprise customers without a six-month security review. That's the actual value.”
David L.
Engineering Lead, Series A startup
Common questions.
A structured, versioned map of how your company operates, built from the data already living in your CRM, HRMS, payment, and communication tools. It is not a chatbot over your documents and not a search box. It is the layer that lets agents retrieve what your company knows and act on it through governed skill files.
Those tools remember and retrieve. Company Brain adds the two things they don't: the ability to take real, full-CRUD actions across 40+ platforms, and governable skill files that let an agent run a company playbook within hard limits. Recall is the starting point, not the product.
A versioned YAML document that encodes one company process, the permissions it needs, the guardrails it must respect, and the steps it runs. Agents call skill files directly. You can read, review, version, and roll them back like any other code.
Yes. The @routemcp/mcp-server package is MIT-licensed and publicly available on GitHub. You can inspect every tool definition, self-host it, or contribute connectors. The SDK and cloud dashboard are commercial, but the MCP server you run in your agent environment is fully open.
Never. Every read is passthrough. RouteMCP fetches from the source platform and returns the result directly to your agent. We log tool-call metadata for observability, but we never buffer, cache, or persist a single row of your customers' data.
Merge handles normalized reads but locks writes behind enterprise, costs $650+/mo, and has no MCP tooling. Composio handles agent tool-calling but has no normalized schema. RouteMCP is both in one stack: unified schema reads, full CRUD writes, and a native MCP server, from $49/mo. You stop paying for two platforms and stop writing glue code between them.
CRM: Salesforce, HubSpot, Pipedrive, Zoho CRM, Monday CRM, LeadConnector. Payments: Stripe, Razorpay, Paddle. HRMS: Workday, Keka, GreytHR, BambooHR. Accounting: QuickBooks, Xero, FreshBooks, Zoho Books. PMS: AppFolio, Buildium. Developer tools: GitHub, Notion, Jira. Email: Gmail. We ship new connectors regularly. See the full list at docs.routemcp.io/integrations.
Yes. The SDK is a standard REST-backed TypeScript client. Many teams use it for traditional product integrations, syncing CRM data, triggering payments, pulling payroll, with no AI layer. If and when you add an agent, the MCP server is already there.
Everything else is in the docs.docs.routemcp.io
Build the next generation of AI apps.
We are onboarding the first 100 teams. Three fields, one click.
50% off for life · first 100 teamsno credit cardsandbox in 24hopen-source MCP server
Questions first? Email nishant@codiste.com