MCP connectors: connect Claude and ChatGPT to the tools your company runs on
Your team already asks AI to write the email, summarise the meeting and draft the proposal. The answers get far better the moment the AI can see the CRM, the inbox and the invoices. That is what an MCP connector does.
Deployed OS gives your company its own MCP gateway: one MCP with every connector in it. People sign in to the tools with their own logins, admins decide which groups get what, and every call is logged. It works the same in Claude, ChatGPT and Copilot.
Pick a tool to see what the AI can do in it, what to ask and who sees what.
Finance and accounting
- Fortnox MCPRead-only · Built for the Nordics
- Visma eEkonomi MCPRead-only · Built for the Nordics
- Xero MCPRead-only
- QuickBooks MCPBuilt on request
- Sage Intacct MCPBuilt on request
- Tripletex MCPBuilt on request · Built for the Nordics
- Pleo MCPBuilt on request · Built for the Nordics
- DATEV MCPBuilt on request
- e-conomic MCPBuilt on request · Built for the Nordics
- PowerOffice MCPBuilt on request · Built for the Nordics
- Pennylane MCPBuilt on request
- Qonto MCPBuilt on request
- Spendesk MCPBuilt on request
- Agicap MCPBuilt on request
- Mollie MCPBuilt on request
- Stripe MCPBuilt on request
ERP and business systems
- Monitor ERP MCPBuilt on request · Built for the Nordics
- Business Central MCPBuilt on request
- NetSuite MCPBuilt on request
- SAP S/4HANA MCPRead-only
- SAP Business One MCPRead-only
- SAP Ariba MCPRead-only
- Workday MCPBuilt on request
- Odoo MCPBuilt on request
- Exact Online MCPBuilt on request
- AFAS MCPBuilt on request
- Uniconta MCPBuilt on request · Built for the Nordics
- Xledger MCPBuilt on request · Built for the Nordics
Contracts and e-signing
CRM and sales
- HubSpot MCPReads and writes
- Salesforce MCPReads and writes
- Pipedrive MCPReads and writes
- SuperOffice MCPReads and writes · Built for the Nordics
- Attio MCPReads and writes
- Zoho CRM MCPReads and writes
- Dynamics 365 MCPReads and writes
- SAP Sales Cloud MCPRead-only
- Close CRM MCPReads and writes
- Salesloft MCPReads and writes
- Gong MCPBuilt on request
- Keap MCPReads and writes
- Oracle Sales MCPReads and writes
- Creatio MCPReads and writes
- Teamleader MCPBuilt on request
- Sellsy MCPBuilt on request
HR and recruiting
Chat and messaging
Email and calendar
Files and knowledge
Projects and tasks
Customer support
Marketing and analytics
- Google Analytics MCPRead-only
- Google Search Console MCPRead-only
- Google Ads MCPRead-only
- Meta Ads MCPBuilt on request
- Mailchimp MCPReads and writes
- Canva MCPBuilt on request
- Typeform MCPRead-only
- Google Forms MCPReads and writes
- LinkedIn MCPReads and writes
- Instagram MCPReads and writes
- X (Twitter) MCPReads and writes
Data and BI
Research and web search
What an MCP connector is
MCP, the Model Context Protocol, is the open standard Claude, ChatGPT and Copilot use to talk to other software. An MCP connector is one link between an AI assistant and one tool: an address, a login and a set of actions such as "search deals" or "list unpaid invoices".
Once it is connected, you stop pasting things into the chat. You ask, and the AI fetches what it needs from the tool, within the rights of the person asking.
New to this? Our guide explains what Claude connectors are and which one to set up first.
Why one connector per person stops working
With three enthusiasts it is fine for everyone to add their own connectors. At thirty people nobody can say which tools are connected, who reaches what or whether anyone uses them. Someone leaves and their connections stay live.
That is the problem a company MCP solves. We wrote a longer piece on it: what an MCP gateway is and when you need one.
How Deployed OS handles connectors
One connection per employee, every tool behind it, and the controls IT asks for in the first meeting.
- One MCP for every tool
- Each person connects their AI assistant to your company MCP once. Every connector you switch on is behind it, next to your company’s skills and guardrails.
- Each person’s own login
- For almost every tool, people sign in with their own account, so the AI sees exactly what they see. Where a tool only offers a company key, its page says so and how access is limited.
- Admins choose who gets what
- Finance gets Fortnox, sales gets HubSpot, everyone gets Slack. A connector is only visible to the groups you give it to.
- Every call logged
- Who asked, which connector, read or write, when. You also see AI use and cost per person and per team. Exportable for review, and access goes the day someone leaves.
- Claude, ChatGPT and Copilot
- The same connectors work in whichever assistant people prefer. You don’t have to pick one AI provider for the whole company.
Read first, write where it’s safe
Most of what people need from a tool is reading: what’s overdue, what was said, where the deal stands. So most actions read. Where the AI writes, it writes the safe things: a draft email that is never sent, an internal note, a task, a draft contract.
Writing is a separate permission. Admins give Edit access only to the groups that need it; everyone else can only read, whatever the connector can do. For the actions you choose, the AI shows the person what it is about to do and waits for a yes.
Every connector page lists exactly what that connector can do today. Need it to do more? We extend connectors for the companies that use them.
Nordic systems, not just American ones
Most MCP directories stop at Slack and Salesforce. Swedish companies run on Fortnox, Visma eEkonomi, Scrive and Oneflow, so those are connectors too, with the same login, groups and log as everything else.
Missing a tool?
Tell us what your company runs on. If a connector is missing we build it, and if one does too little for you we extend it. You can also connect your own MCP servers.
MCP connectors: common questions
A link between an AI assistant such as Claude or ChatGPT and one tool, built on the Model Context Protocol. It gives the AI a set of actions in that tool, such as searching deals or listing invoices, within the rights of the person using it.
The server is the software that exposes a tool’s actions over MCP. The connector is what you add in Claude or ChatGPT to reach it. With Deployed OS your company has one MCP server, and every tool you switch on is a connector behind it.
Yes. Deployed OS is your company’s own MCP, so the same connectors work in Claude, ChatGPT and Copilot. People keep the assistant they prefer.
Only where a connector has a write action, and only for the groups an admin gives Edit access. The write actions are deliberately narrow: drafts, notes, tasks and similar. Each connector page lists exactly what it reads and what it writes. No connector deletes anything.
Tell us. We build new connectors and extend existing ones for the companies that use them.
It depends on the size of your team. Get in touch and we will walk you through it.
- Claude Connectors: What They Can Access and How to Set Up
- MCP Gateway: What It Is and How to Choose One
- MCP Security: Risks and Best Practices for Companies
- MCP Governance: Access Control, Auth and Audit Logs
- Claude Team vs Enterprise: Pricing, Usage and Which You Need
- Is Claude Safe for Confidential Information? Plan by Plan
See it on your own tools.
Tell us which systems your company runs on. We’ll show you what your team can ask, and what IT gets to control.