Claude MCP Servers: How to Connect and Which to Try First

Claude MCP servers are MCP servers you connect to Claude so it can call real tools: list pull requests, query a database, read Search Console data. You connect a local server through a config entry or a hosted server through a connector, then confirm it by asking Claude to use one of its tools.

Two ways to connect

There are two routes, and the right one depends on where the server runs.

Route	How it connects	Good for	Watch out for
Local server	Config entry that starts a process on your machine	Files, local databases, personal tooling	Credentials sit on your computer
Remote server	HTTPS endpoint, usually with OAuth sign-in	Shared team tools, SaaS products	You trust the host with the connection

For local servers in Claude Desktop, the usual mechanism is a JSON config file with an mcpServers object, where each entry gives a command and arguments. For remote ones, you add a connector or URL in settings. Anthropic changes these screens, so use its documentation as the source for exact menu names.

BusinessMCP’s walkthrough on connecting Claude Desktop and its page for Claude Desktop servers show the hosted route end to end. If you prefer to see the wider field first, the BusinessMCP MCP server directory lists what you can connect.

A sensible starter set

Resist the urge to install ten servers on day one. Three is plenty to learn how it feels.

1. One read-only data source. A database or analytics server where you can only select, never write.
2. One content or code source. GitHub, or a file server restricted to one folder.
3. One web reader. A fetch-style server that converts a page to markdown.

Why those? They are useful immediately and low-risk. Directory pages mark some as Verified, for example the Fetch server and the Prisma and Supabase servers appear with that label in BusinessMCP’s category lists. Verified there means a link check on the repository or docs, not an audit, so you still decide what to trust. For finding more, see our MCP servers list.

Key takeaway: the first server you connect should be the one whose worst mistake you can undo. Read-only first, write access later.

Step by step: connect and test

1. Decide local or remote. If you are unsure, remote with OAuth is usually simpler to set up and easier to revoke.
2. Get credentials in the narrowest form available. For payments, BusinessMCP’s Stripe listing recommends a restricted key with read access only to the resources you need, and notes that test-mode keys are supported.
3. Add the server using Anthropic’s current instructions.
4. Restart the app if the method requires it.
5. Ask Claude “what tools do you have from this server?” It should list names that match the listing.
6. Run one harmless prompt, such as “list the five most recent charges” or “show the schema of the orders table.”
7. Check the result against the source system with your own eyes the first few times.

What goes wrong most often

• The server does not appear. Usually a typo in JSON, a missing runtime such as Node, or a forgotten restart.
• Auth fails. Expired token, or a key scoped to the wrong resource.
• Claude picks the wrong tool. Too many overlapping servers. Remove duplicates, for instance two web fetchers.
• Slow replies. Each connected server adds tool descriptions to the model’s context. Disable what you are not using.

Choosing by task

If you work mostly in a terminal, the setup differs, so read Claude Code MCP servers. If your tools live in a vendor’s cloud and the whole team needs them, remote MCP servers are the better pattern. If you are choosing for a particular field, see developer servers or SEO servers.

A note on trust

Whatever you connect, Claude will act through it with the permissions you gave. Read are MCP servers safe before connecting anything that holds customer data or can send messages. Features and menu names change often, so confirm on Anthropic’s pages and the server publisher’s own documentation.

Example workflows once connected

Concrete prompts make the setup worth it. These are patterns drawn from listings we read, adapted to be generic.

Revenue check. With a read-only payments server, ask for recent failed charges and which customers to follow up with. BusinessMCP’s Stripe listing suggests prompts of this kind and also describes drafting an invoice for review before anything is sent. Keep that draft-first habit for anything that touches customers.

Code review prep. With a GitHub server, ask Claude to list open pull requests that touch a given folder and summarise the diffs. You read the summary, then open the pull request yourself.

SEO triage. With a Search Console server, ask which queries have impressions but few clicks and what content gaps that suggests. The SEO category lists Google’s own Search Console server and describes it as exposing query data, index coverage and sitemap tools.

Research. With a fetch server, ask Claude to read three documentation pages and compare their claims. The Fetch server in BusinessMCP’s lists is described as honouring robots.txt and converting pages to markdown.

Comparing the main ways to run servers with Claude

Factor	Local config	Hosted connector
Setup time	Minutes, needs runtime installed	Minutes, needs sign-in
Where secrets live	Your machine	The provider’s vault, by their account
Team sharing	Each person repeats setup	One endpoint, scoped keys
Revocation	Delete the config and rotate the key	Revoke the key in the provider’s settings
Offline use	Possible for local-only servers	Needs internet

BusinessMCP, for instance, states that keys on its hosted endpoint are scoped per connection and can be revoked, and that provider credentials are stored server-side rather than exposed to the model. That is the vendor’s own claim, so read its security page before relying on it.

Keeping the setup tidy

Name servers clearly so you can tell them apart in tool lists. Remove any server you have not used for a month. Keep a note of which credentials each one holds, and rotate them if a laptop is lost. When Claude behaves oddly, disable servers one by one to find the source before blaming the model.