# Which Customer Onboarding Platform Has an MCP Server for Claude or ChatGPT? By Mantas Aleksiejevas > Cor has an MCP server. Add Cor from Claude's connector directory and run Obi, the AI agent that works directly with every new customer, from Claude. URL: /blog/customer-onboarding-mcp-server Published: 2026-11-01 Target keyword: customer onboarding mcp server **Quick answer:** Cor has an MCP server. Cor builds Obi, an AI agent that works directly with every new customer of a B2B software company and takes them through setup. Add the Cor connector from Claude's connector directory, sign in, and your team can run onboarding from Claude: see who finished setup, see who got stuck and why, and improve what Obi works from. Nothing new to learn and no other app to open. Cor's MCP is also available in ChatGPT. ## What an MCP server means for customer onboarding MCP is an open standard. It lets an AI assistant, like Claude, use another tool on your behalf, with your permission. The tool adds a "connector". You ask Claude a question, and Claude asks the tool. For onboarding, that means you can type "Which new customers are stuck on setup this week, and why?" into Claude and get the answer from Cor. You don't log in to another dashboard. You don't export a report. There are two sides to it: - **Your customers work with Obi.** Obi works directly with every new customer. Customers do not need Claude. - **Your team works with Cor from Claude.** You ask how onboarding is going, and Claude asks Cor. ## What Obi does with every new customer The MCP server is how your team runs Cor. The onboarding itself is done by Obi: 1. **First contact.** A new customer is added to Cor, directly or through an integration. Obi contacts them by email as standard. Obi can also be started from inside your product. 2. **A plan for each customer.** Obi learns what the customer needs and builds a plan. An admin on your team confirms the plan before Obi acts. 3. **Live sessions.** Obi runs onboarding on a live call, a bit like a Zoom call. The customer shares their screen. Obi sees it, guides them through setup step by step, and can complete setup tasks for them. 4. **Follow-ups.** Between sessions, Obi follows up by itself. 5. **Handovers.** When something needs a person, Obi hands over to your team by email, Slack or the Cor admin. 6. **A report.** Your team gets a report of who finished setup, what they asked and where they got stuck. Obi learns from the help centre you already have. It speaks more than 60 languages, so your help docs don't need translating. Cor is set up in a day. ## What you can do with Cor from Claude Once Cor is connected, your team can ask Claude things like: - "Who finished setup this week, and who is stuck?" - "Where did new customers get stuck most often, and why?" - "Walk me through one customer's onboarding session." - "What did new customers ask about most this week?" - "Draft a fix for the step where customers keep stalling." Claude may already be connected to your other tools, such as Slack or your CRM. Add Cor and it joins them. One request can find the customers who got stuck in Cor and draft follow-ups with the tools Claude already has. Session data also syncs to your CRM on every plan. For a full tour of the Cor connector, see [Cor MCP](/product/mcp). ## What stays in your control - **An admin confirms each plan.** Obi does not start work with a customer until an admin on your team confirms the plan. - **Changes need approval.** When you ask Claude to improve something, Cor drafts the change. Your team reviews it in Cor. Nothing reaches your customers until your team approves it. - **Your permissions still apply.** Each person on your team works with their own Cor account permissions. - **No engineers needed to connect.** Add the connector, sign in with Google, and you are done. You need an existing Cor account. ## How to check if an onboarding vendor has an MCP server Many teams now check vendor by vendor: "does [vendor] have an MCP server?" Here is a fair way to check any onboarding tool, including Cor: 1. **Is there an MCP server or connector at all?** Look in the vendor's own docs and in Claude's connector directory. Don't rely on a sales deck. 2. **Does it work with the AI assistant your company approved?** If IT approved one assistant, that is the one that counts. 3. **Can the assistant only read, or can it help you act?** Reading reports is useful. Fixing the step where customers stall is more useful. 4. **Who approves changes?** Check that a person on your team signs off before customers see anything new. 5. **What does the tool do for your customers?** An MCP server is only as useful as the work behind it. Ask whether the tool runs onboarding with each customer, or only shows data about it. Other onboarding and customer success tools may have their own MCP servers. Check each one's docs for what is live today. For a wider list of tools, see [the best AI onboarding agents](/blog/best-ai-onboarding-agents). ## Is there a best MCP server for user onboarding software? There is no single best one. The best fit is the one that connects to the assistant your team already uses and does real onboarding work behind it. Cor is one example: the MCP server lets your team run Obi from Claude, and Obi does the onboarding with each new customer. ## Running onboarding from Claude If Claude is the main tool your team works in, read [which AI onboarding agent works with Claude](/blog/ai-onboarding-agent-for-claude). It shows how Cor works from Claude, step by step. Read more: [how Obi works with every new customer](/product/onboarding-agent), [build or buy an AI onboarding agent](/blog/build-or-buy-ai-onboarding-agent) and [trust and security](/trust-security). Questions: team@getcor.ai. ## About the author **Mantas Aleksiejevas** Co-founder of Cor. Works on Obi, the AI agent that runs customer onboarding. [LinkedIn](https://www.linkedin.com/in/mantasaleks) ## FAQ **Does Cor have an MCP server?** Yes. Cor has an MCP server, and Cor is listed in Claude's connector directory. Add the Cor connector, sign in, and your team can run onboarding from Claude. Obi, Cor's AI agent, works directly with every new customer. **Does it work with ChatGPT and Copilot as well as Claude?** Yes. Cor's MCP is available in Claude, ChatGPT and any other AI assistant that supports MCP. **Do we need engineers to connect it?** No. Add the Cor connector in Claude and sign in with Google. You need an existing Cor account. Getting Obi ready uses the help centre you already have, and Cor is set up in a day. **Can the assistant change things without our OK?** No. Cor drafts changes, and your team reviews and approves them in Cor before any customer sees them. An admin also confirms each customer's plan before Obi acts, and each person works within their own Cor permissions. **Do our customers need Claude?** No. Only your team uses Claude. Obi works directly with every new customer by email as standard, and can also be started from inside your product. **What can we ask Cor from Claude?** Who finished setup, who got stuck and where, what customers asked, and what happened in a single customer's session. You can also ask Cor to draft improvements to what Obi works from, for your team to approve.