AI Engineering

Best MCP Servers for Business: 16 Official Servers and How to Choose

Rows of colourful patch cables plugged into a labelled network panel Plug AI into what you use.

The safest MCP servers for a business are the official ones, run by vendors whose tools you already use, connected over OAuth with the smallest permissions that work. Reference servers are for learning. When your own system has no server, you build one.

This guide covers official servers from vendors most businesses already pay for. For each one it gives the same facts, taken from the vendor’s own documentation: whether it runs remotely or locally, and how it signs in. It then sets out how to judge any server before you connect it. If the term is new, start with what an MCP server is.

One disclosure first. CodeLeap builds custom MCP servers, and we have no affiliation with any vendor listed here. Nothing below is a ranking. We have not tested these servers against each other, and the order within each table is not a verdict.

Where to find MCP servers

Three places cover most needs. Each one lists servers, and none of them vouches for every server on it.

The first is the vendor’s own documentation. If you pay for a product, its docs will say whether an official MCP server exists and how to connect it. Every server in this guide links to that page.

The second is the official MCP Registry. It launched in preview on 8 September 2025, with general availability to follow, and it provides MCP clients with a list of MCP servers. Because it is still a preview, treat entries as a lead and check the publisher yourself.

The third is the directory inside your assistant. Claude, for example, has a Connectors Directory, described in Anthropic’s guide to using connectors. That same page says to only connect to servers from trusted organisations, which is a good rule to keep for everything that follows.

Official MCP servers by job

The tables below list servers from vendors that document their own MCP server. Details were taken from each vendor’s documentation in November 2026 and can change, so open the linked page before you set anything up. Where a vendor offers a choice of sign-in methods, we list both.

Developer and operations tools

ServerRemote or localHow it signs in
GitHubRemote, or local with DockerOAuth or personal access token
SentryRemote, or local through npmOAuth or user auth token
SupabaseRemote, or local through the CLIOAuth or personal access token
CloudflareRemoteOAuth or API token
Microsoft Azure MCP ServerLocalEntra ID and role-based access control
Google Cloud (BigQuery, Maps, Cloud Storage and more)RemoteSee each product’s setup guide

GitHub’s server lets an assistant work with repositories, issues and pull requests. The hosted version is at https://api.githubcopilot.com/mcp/, and there is a local Docker option for teams that prefer it.

Sentry’s server is remote and uses OAuth, which suits teams that want an assistant to read error reports without handling a key. A local version that takes a user auth token also exists.

Supabase offers both a remote server and a local one through its CLI. It supports read-only mode and project scoping, which matter a lot for a database.

Cloudflare publishes a set of remote servers for its platform, with OAuth or an API token.

Microsoft’s Azure MCP Server runs locally and uses Entra ID with role-based access control, so the assistant gets the access your identity already has.

Google Cloud lists remote MCP servers for BigQuery, Maps, Cloud Storage and other products. Setup is documented per product, so check the entry for the one you want.

Work management and collaboration

ServerRemote or localHow it signs in
Atlassian (Jira and Confluence)RemoteOAuth 2.1, with an optional API token
LinearRemoteOAuth 2.1 or API key
AsanaRemoteOAuth
NotionRemote, hosted by NotionOAuth, or an MCP token for Business and Enterprise owners
SlackRemoteOAuth

These servers let an assistant read and update the places where your team tracks work. The Atlassian remote server covers Jira and Confluence, and Atlassian says actions respect existing permissions.

Linear runs a remote server with a separate read-only endpoint. Asana’s V2 server is remote and uses OAuth.

Notion hosts its own remote server. Its docs say the older local package is no longer actively maintained, so use the hosted one.

Slack’s server lives at https://mcp.slack.com/mcp and uses OAuth.

Sales and support

ServerRemote or localHow it signs in
HubSpotRemoteOAuth 2.0 through a user-level app
IntercomRemote, with US and EU endpointsOAuth or bearer token

HubSpot’s server is at mcp.hubspot.com. HubSpot’s docs say it excludes Sensitive Data Properties, which is a useful default for a CRM.

Intercom’s server has separate US and EU endpoints, so pick the one that matches where your workspace is hosted.

Payments

ServerRemote or localHow it signs in
StripeRemoteOAuth or agent API key
PayPalLocal and remoteAccess token for the local server

Stripe’s remote server is at https://mcp.stripe.com. PayPal offers a local server that takes an access token, and a remote one. Payment servers are where the vendor warnings in the section below matter most.

Automation

ServerRemote or localHow it signs in
Zapier MCPHosted by ZapierSee Zapier’s documentation

Zapier MCP is a hosted server that connects an assistant to many of the apps Zapier supports. It is a useful route when a tool has no official server of its own. It also puts one more party between the assistant and your data, so judge it with the checklist below like any other.

The reference servers are for learning

The MCP project publishes a repository of reference servers: Everything, Fetch, Filesystem, Git, Memory, Sequential Thinking and Time. They are useful for learning how a server is put together and for testing a client.

The repository itself describes them as reference implementations and educational examples, and says they are not production-ready. Treat them as you would sample code. Read them, learn from them, and do not give one of them access to company files or systems on the strength of its name.

This is one of the main differences between a server example and a server you can rely on. An example shows a pattern. A vendor’s official server comes with an owner, documentation and a way to report problems.

How to judge an MCP server before you connect it

Run any server, official or not, through the same checks. They take a few minutes and catch most of the avoidable risk.

  1. Who runs it? A server published by the vendor of the product is a different proposition from one a community member wrote. Prefer the vendor. If you must use a community server, read its code or have someone who can.
  2. Remote with OAuth, or local with a pasted token? OAuth lets you sign in as yourself and revoke access later. A pasted token is a credential that sits in a config file on someone’s laptop.
  3. What scopes does it ask for? The MCP project’s security best practices say to minimise scopes and avoid wildcard scopes. Be wary of any server that asks for full access when the task needs a read.
  4. Is there a read-only mode? Several vendors offer one. Linear has a /mcp/readonly endpoint, and Supabase has a read_only setting. Start there, and add write access only when you have a reason.
  5. Do actions respect your existing permissions? Atlassian says its server’s actions respect the permissions a user already has. That is the behaviour you want, because the assistant cannot do more than the person could.
  6. Is tool approval on? Keep a human able to approve actions, especially anything that changes data or moves money.
  7. What can administrators control? Slack allows only Marketplace-published or internal apps, and its admins approve clients. Asana lets Enterprise+ admins allow or block clients. Ask the same question of any vendor, and write down the answer.
  8. Is it local? The security guidance warns that local servers may have direct access to the user’s system. If you run one, sandbox it and give it the minimum privileges.

If a server fails two or three of these, find another route to the same data. That might be a different server, a narrower custom one, or a plain API call.

Vendor warnings to read first

Several vendors say plainly where their servers need care. These warnings are specific, so read them before you connect anything.

Stripe. Its MCP documentation tells users to turn on tool approval, and warns about prompt injection from other servers. That means a second server connected to the same assistant could try to steer it into using Stripe in ways you did not intend. Per its docs, full-access and restricted keys without the Agent tag stop working in December 2026, so migrate to an agent API key by 30 November 2026. If you use Stripe’s server with an API key, check that date.

Supabase. Its guide says the server is a developer tool. Do not give it to customers, and keep manual approval switched on.

Azure MCP Server. Microsoft’s overview says the local server is strictly for developer use within your organisation.

Anthropic. Its connectors guide says to only connect to servers from trusted organisations.

The pattern across all four is the same. Official does not mean unlimited. The vendors tell you who the server is for, and a safe setup follows that.

When to build your own MCP server

Build your own when none of the official servers reaches the system you care about. Four situations come up most often.

  • Your own platform. If you run a product with customers, an MCP server gives their assistants a defined way in.
  • An internal database or tool. No vendor will publish a server for your internal systems.
  • A system with no official server. Plenty of industry software has an API and no MCP server.
  • A narrower, safer action set. Even when an official server exists, it exposes the vendor’s idea of useful actions. A custom server can offer five well-described tools and leave out delete and bulk update.

The last one is easy to overlook. A vendor’s server has to serve every customer, so it is broad by design. Yours can be shaped around one team’s task.

Most custom servers sit on top of an API you already have. Our guide to MCP vs API explains how the two fit together, and how to build an MCP server walks through the build.

CodeLeap’s MCP server development starts from £5,000 (about $6,500), at a fixed price agreed before we start. What moves the price is the number of tools, how many systems sit behind them, and how involved the authentication is. If you want an assistant to take multi-step actions across several of these systems, that is closer to our AI agents and automation work.

A sensible next step

List the five or six tools your team uses most. Check each vendor’s documentation for an official MCP server. Connect one, over OAuth, in read-only mode if it has one, and let a few people use it for a week before you add a second.

If a system you depend on has no official server, or you want a narrower set of actions than a vendor offers, our MCP server development service starts from £5,000 (about $6,500). Book a call and we will tell you straight whether an existing server will do.

Frequently asked questions

What is the best MCP server?

There is no single best one, because the right server depends on the tools your team already uses. A sensible rule is to start with official servers from vendors you already pay for, such as your code host, project tracker or CRM, connect them over OAuth, and give them the smallest permissions that do the job. Add others only when a specific task needs them.

Are MCP servers safe?

It depends on who runs the server and how you connect it. The MCP project's security guidance covers local server risks, scope minimisation and avoiding wildcard scopes. Anthropic advises connecting only to servers from trusted organisations. Official remote servers with OAuth, read-only modes and tool approval switched on are the safer end of the range.

Where can I find MCP servers?

Start with the vendor's own documentation, since official servers are published there. The official MCP Registry, which launched in preview on 8 September 2025, lists servers for MCP clients. Claude has a Connectors Directory too. Treat any listing as a starting point and still check who publishes the server and what access it asks for.

What is the difference between a remote and a local MCP server?

A remote server runs on the vendor's infrastructure and you connect to it over the internet, usually signing in with OAuth. A local server runs on your own machine, often started with a package or Docker, and usually needs a token or credentials you supply. The MCP security guidance warns that local servers may have direct access to the user's system.

Do I need to build my own MCP server?

Only if the system you want an assistant to reach has no official server, or you need a narrower and safer set of actions than a vendor offers. If your tools are mainstream SaaS products, an official server may already cover them. Custom servers make sense for your own platform, an internal database or a workflow with specific rules.

Want to build something like this?

Book a free 30-minute consultation and we'll help you find where automation pays off.

Book a consultation Get a free quote

Keep exploring

Back to all insights

Book a free call with Vivian

COO and co-founder · London

Request a callback

Leave your name and number and we'll call you back.