Connecting MCP servers to Claude permits it to work with exterior instruments, information, databases, repositories, and different techniques as an alternative of working solely inside the chat window. The setup differs barely between Claude Desktop and Claude Code, however each will be configured in just some steps.<\/p>\n
On this article, you\u2019ll learn to join MCP servers with Claude Desktop and Claude Code, a sensible step-by-step information for getting every setup operating accurately.<\/p>\n
What Is MCP and Why Does It Matter?<\/h2>\n
MCP (Mannequin Context Protocol) is the common connector layer that lets any AI mannequin speak to any exterior instrument by means of a single standardised interface with out customized integration code for each mixture.<\/p>\n
Earlier than MCP, connecting Claude to GitHub required one customized integration. Connecting it to Slack required a distinct one. Connecting it to your database required a 3rd. Anthropic referred to as this the \u201cN\u00d7M downside\u201d: N AI fashions occasions M exterior instruments meant N\u00d7M bespoke connectors<\/span>. MCP solves it by turning that into N+M. Construct one MCP server for GitHub, and each MCP-compatible AI consumer Claude, Cursor, Windsurf, and dozens extra can use it instantly.<\/p>\n Understanding the 3-part structure takes 2 minutes and prevents 90% of setup confusion.<\/p>\n Part Host Shopper Server Once you ask Claude to \u201ctest my open GitHub PRs\u201d, here’s what occurs behind the scenes:<\/p>\n Claude identifies it wants an exterior instrument to fulfil the request.<\/p>\n The MCP consumer in Claude sends a JSON-RPC request to the GitHub MCP server.<\/p>\n The server queries GitHub\u2019s API and returns structured information.<\/p>\n Claude incorporates that information into its context and generates your reply.<\/p>\n The entire move takes below a second. You by no means see the plumbing.<\/p>\n As of April 2026, Streamable HTTP is Anthropic\u2019s official advisable transport, and the older SSE transport is being deprecated.<\/p>\n Claude Desktop reads its MCP configuration from a single JSON file. There are two methods to put in servers: the brand new one-click Desktop Extensions (.mcpb information, previously .dxt) and the standard JSON config technique. Use Extensions for supported servers; use JSON config for something customized.<\/p>\n As of early 2026, Claude Desktop helps Desktop Extensions, pre-packaged MCP servers distributed as .mcpb information (MCP Bundle; older guides might name these .dxt information, which nonetheless work however are the legacy title). These set up with a double-click. No JSON modifying, no Node.js PATH points.<\/p>\n Open Claude Desktop.<\/p>\n Click on the \u201c+\u201d button within the bottom-left of the chat enter.<\/p>\n Choose \u201cConnectors\u201d to open the connectors menu.<\/p>\n Discover your server (e.g., GitHub, Google Drive) and click on Set up (or Click on onn add connectors to search out one on the connectors listing).<\/p>\n Restart Claude Desktop. The server prompts robotically.<\/p>\n Desktop Extensions are the precise alternative for non-technical customers or servers you wish to \u201cset and overlook.\u201d The JSON config technique beneath is correct for customized servers, non-public servers, or full management over arguments and surroundings variables.<\/p>\n Claude Desktop reads its MCP configuration from claude_desktop_config.json. The file location is determined by your OS:<\/p>\n macOS: ~\/Library\/Utility Assist\/Claude\/claude_desktop_config.json<\/p>\n Home windows:\u00a0%APPDATApercentClaudeclaude_desktop_config.json<\/p>\n On Home windows, which folder really has this file is determined by the way you put in Claude Desktop, and this journeys up lots of people. There are two fully completely different areas:<\/p>\n Direct .exe installer (from claude.ai\/downloads): %APPDATApercentClaudeclaude_desktop_config.json<\/p>\n Microsoft Retailer, WinGet, or MSIX set up: %LOCALAPPDATApercentPackagesClaude_pzs8sxrjxfjjcLocalCacheRoamingClaudeclaude_desktop_config.json<\/p>\n If %APPDATApercentClaude doesn\u2019t exist in your machine, you virtually definitely have the Retailer\/MSIX set up, and your actual file is at that second, uglier path. Home windows\u2019 app-packaging mannequin silently redirects it there as an alternative of the usual location each piece of documentation assumes.<\/p>\n If neither path has the file but, open Claude Desktop itself, go to Settings \u2192 Developer \u2192 Edit Config. That creates the file at whichever path your particular set up really makes use of, so that you don\u2019t must guess.<\/p>\n One Home windows-specific lure: paths inside JSON want double backslashes. C:UsersyournameDocuments in a JSON string have to be written as C:CustomersyournamePaperwork, a single backslash breaks the JSON parser. Right here\u2019s what a whole, accurately escaped config seems like:<\/p>\n Open Claude Desktop \u2192 high menu bar \u2192 Settings \u2192 Developer \u2192 Edit Config. This opens the file in your default editor and creates it if it doesn’t exist.<\/p>\n The file has only one top-level key, mcpServers. Consider it as a listing of servers you need Claude to find out about. Every server will get its personal entry inside that listing, and also you choose no matter title you need for that entry (like \u201cfilesystem\u201d or \u201cgithub\u201d beneath).<\/p>\n Inside every server\u2019s entry, there are three issues you may set:<\/p>\n command:\u00a0the precise program Claude runs to start out that server (often npx, since most servers are distributed as npm packages)<\/p>\n args:\u00a0the listing of arguments handed to that command, precisely such as you\u2019d kind them in a terminal<\/p>\n env:\u00a0any surroundings variables the server wants, mostly API keys or entry tokens<\/p>\n Right here\u2019s a sensible starter config for a developer workflow: filesystem entry, GitHub integration, and net search:<\/p>\n { filesystem doesn\u2019t want any credentials, so it solely has command and args. The args listing tells npx which package deal to run (@modelcontextprotocol\/server-filesystem) and which folders in your pc it\u2019s allowed to the touch, on this case Paperwork and initiatives.<\/p>\n github must show who you’re to GitHub\u2019s API, so it has an additional env block. GITHUB_PERSONAL_ACCESS_TOKEN is the place you paste your personal GitHub token. The server reads it as an surroundings variable when it begins up, the identical means a program run out of your terminal would.<\/p>\n Go to github.com and sign up. Click on your profile picture within the top-right nook, then click on Settings.<\/p>\n Within the left sidebar, click on Developer settings (it\u2019s close to the underside).<\/p>\n Click on Private entry tokens, then High-quality-grained tokens, then Generate new token. GitHub now recommends fine-grained tokens over the older \u201cbasic\u201d ones, since you may restrict them to particular repos as an alternative of your complete account.<\/p>\n Give it a Token title (something memorable, like \u201cclaude-mcp\u201d), and set an Expiration. GitHub warns in opposition to \u201cno expiration\u201d for good motive, choose 90 days and put a renewal reminder in your calendar.<\/p>\n Beneath Useful resource proprietor, choose your private account (or the group whose repos you want). Beneath Repository entry, select Solely choose repositories and choose simply those Claude really wants, not all of them.<\/p>\n Beneath Permissions, grant solely what you\u2019ll use. For many workflows, Contents (learn and write) and Points (learn and write) cowl it. Add Pull requests (learn and write) if you’d like Claude opening or reviewing PRs.<\/p>\n Click on Generate token on the backside, then copy it instantly. GitHub exhibits a fine-grained token precisely as soon as, when you navigate away earlier than copying it, you\u2019ll must generate a brand new one.<\/p>\n That token (it begins with github_pat_) is what goes instead of \u201cghp_your_token_here\u201d within the JSON config above:<\/p>\n “GITHUB_PERSONAL_ACCESS_TOKEN”: “github_pat_your_actual_token”<\/p>\n brave-search follows the identical sample as github: one command, one args listing to run the precise package deal, and one env variable for its API key.<\/p>\n That\u2019s the entire sample. Each server you ever add to this file follows the identical form: a reputation you select, a command to run it, arguments to configure it, and (if it must authenticate) an env block for its secrets and techniques.<\/p>\n Claude Code has its personal MCP configuration floor separate from Claude Desktop, and it comes with a devoted CLI command that makes setup sooner than modifying JSON manually.<\/p>\n You possibly can set up Claude Code following this information: Claude Code Information<\/p>\n Have already got servers arrange in Claude Desktop? Run claude mcp add-from-claude-desktop (macOS or WSL) to repeat them straight into Claude Code as an alternative of re-adding each by hand.<\/p>\n The essential syntax is:<\/p>\n claude mcp add — [args…]<\/p>\n That\u2019s the sample for a neighborhood server, one Claude Code runs itself as a subprocess. Hosted servers reached over a URL use \u2013transport http as an alternative and skip the \u2014 command solely:<\/p>\n claude mcp add –transport http docs-server https:\/\/instance.com\/mcp<\/p>\n Hosted servers want no Node.js, no native course of, and nothing to put in. They\u2019re the simplest first server to strive. Native servers, just like the Postgres instance beneath, want a command Claude Code can really run in your machine.<\/p>\n For a Postgres database server:<\/p>\n claude mcp add –transport stdio project-db Claude Code helps three scopes for server configuration:<\/p>\n Scope Native (default) Mission Consumer To confirm setup, run:<\/p>\n claude mcp listing<\/p>\n The standing column tells you precisely what\u2019s taking place:<\/p>\n Standing \u2713 Linked ! Wants authentication ! Linked \u00b7 instruments fetch failed \u2717 Failed to attach \u2717 Connection error \u23f8 Pending approval If it exhibits something aside from \u201cLinked\u201d, run the precise set up command manually in your terminal. The error it prints is much extra helpful than something within the standing line.<\/p>\n The MCP ecosystem has over 2,300 public servers in Might 2026. Most are deserted demos. Those beneath are actively maintained, production-tested, and canopy 80% of actual workflows. My trustworthy take: set up 3\u20135 servers most to start out. Each server provides its instrument definitions to Claude\u2019s context window, and a bloated instrument listing visibly degrades Claude\u2019s tool-selection high quality.<\/p>\n Server GitHub (Official) Filesystem Courageous Search Postgres Notion Slack Context7 Playwright For builders, the sensible starter pack is GitHub + Filesystem + Context7. That mixture covers 80% of coding workflows with out burning context tokens on unused instruments. <\/p>\n 73% of first-time MCP customers hit not less than one connection error. Listed here are the 5 patterns that account for the overwhelming majority of failures, and the repair for every.<\/p>\n Each statuses imply the server didn\u2019t begin, or an HTTP server\u2019s URL didn\u2019t reply. Run the precise set up command manually in your terminal and browse the error output straight. The three most typical causes: npx not present in PATH (use absolute path), flawed npm package deal title, or lacking surroundings variable. Repair the underlying error earlier than touching the Claude config.<\/p>\n If it\u2019s a neighborhood server timing out on its first run (npx downloading the package deal for the primary time can take some time), elevate the startup timeout as an alternative of assuming it\u2019s damaged:<\/p>\n MCP_TIMEOUT=60000 claude<\/p>\n Use the \/mcp slash command inside a Claude Code session to power a reconnect. If instruments nonetheless don\u2019t seem, run claude mcp get an empty instrument listing means the server began however declared no instruments, often a server-side config error. Restart with the up to date server config.<\/p>\n A single lacking comma or mismatched bracket in claude_desktop_config.json silently disables each server. Run your JSON by means of\u00a0jsonlint.com\u00a0or use jq to validate earlier than restarting Claude. That is the one most typical first-install failure mode.<\/p>\n Claude Desktop begins MCP servers with an undefined working listing, so relative paths like .\/mydir by no means resolve. At all times use absolute paths: \/Customers\/yourname\/initiatives as an alternative of ~\/initiatives or .\/initiatives. <\/p>\n One developer measured 30\u201340% of their Claude context window going to MCP instrument schemas that had been by no means utilized in that session. If Claude appears unusually gradual or costly, the perpetrator is nearly at all times too many related servers. Prune to the three\u20135 servers you really use in your present workflow. You possibly can at all times add extra later.<\/p>\n Sizzling take: most individuals who assume they want a higher-tier Claude plan really simply want fewer MCP servers loaded. The context price is invisible however important. For a comparability of Claude plan options and what they really unlock<\/p>\n Constructing a customized MCP server is the quickest technique to give Claude entry to inside instruments, proprietary APIs, or information that no public server covers. The Python SDK makes this surprisingly accessible: you outline instruments with decorators as an alternative of writing JSON schemas by hand.<\/p>\n The minimal viable MCP server in Python:<\/p>\n !pip set up mcp<\/p>\n from mcp.server.fastmcp import FastMCP<\/p>\n mcp = FastMCP(“my-server”)<\/p>\n @mcp.instrument() if __name__ == “__main__”: Register it in your Claude Desktop config the identical means as every other server level command at your Python interpreter and args on the server file path.<\/p>\n One safety be aware that almost all tutorials skip: at all times use scoped permissions when connecting MCP servers. Grant read-only entry first, develop to put in writing entry solely when you could have confirmed the server behaves as anticipated. An MCP server with write entry to manufacturing techniques and a misinterpreted immediate can do actual injury.<\/p>\n Connecting MCP servers to Claude turns it right into a sensible assistant that may work with information, repositories, databases, APIs, and different exterior instruments. Claude Desktop affords easy setup by means of Extensions or JSON configuration, whereas Claude Code makes server set up and administration simple by means of the CLI.<\/p>\n One of the best method is to start out with just a few important servers, use absolute paths, safe your credentials, and grant solely the permissions required. As soon as configured accurately, MCP creates a dependable bridge between Claude and the instruments you already use. With that basis in place, Claude turns into much more succesful, helpful, and prepared for real-world workflows.<\/p>\n A. MCP stands for Mannequin Context Protocol. It’s an open customary created by Anthropic in November 2024 that lets Claude hook up with exterior instruments, databases, information, and APIs by means of a common interface. With MCP enabled, Claude strikes from answering questions based mostly on coaching information to taking actual actions in related techniques studying information, querying databases, pushing GitHub commits, or sending Slack messages.<\/p>\n<\/p><\/div>\nHow MCP Works in 3 Easy Elements<\/h2>\n
\n What It Is
\n Instance in Claude<\/p>\n
\n The AI app the person talks to, manages context, safety, and which servers can be found.
\n Claude Desktop, Claude Code, Cursor<\/p>\n
\n Lives contained in the host. Handles protocol-level communication with every MCP server.
\n Constructed into Claude Desktop \/ Claude Code<\/p>\n
\n An exterior course of that exposes instruments, sources, or prompts to the AI through MCP.
\n GitHub MCP server, Filesystem MCP server<\/p>\n<\/figure>\n<\/div>\nClaude Desktop: Step-by-Step MCP Setup<\/h2>\n
Technique 1: Desktop Extensions (One-Click on, No JSON)<\/h3>\n
![\"Claude](\"https:\/\/cdn.analyticsvidhya.com\/wp-content\/uploads\/2026\/07\/image-68.webp\")
<\/figure>\n<\/div>\nTechnique 2: JSON Config (Full Management)<\/h3>\n
![\"Claude](\"https:\/\/cdn.analyticsvidhya.com\/wp-content\/uploads\/2026\/07\/image-69.webp\")
<\/figure>\n<\/div>\nModifying the Config File<\/h3>\n
\n “mcpServers”: {
\n “filesystem”: {
\n “command”: “\/usr\/native\/bin\/npx”,
\n “args”: [“-y”, “@modelcontextprotocol\/server-filesystem”,
\n “\/Users\/yourname\/Documents”, “\/Users\/yourname\/projects”]
\n },
\n “github”: {
\n “command”: “\/usr\/native\/bin\/npx”,
\n “args”: [“-y”, “@modelcontextprotocol\/server-github”],
\n “env”: {
\n “GITHUB_PERSONAL_ACCESS_TOKEN”: “ghp_your_token_here”
\n }
\n },
\n “brave-search”: {
\n “command”: “\/usr\/native\/bin\/npx”,
\n “args”: [“-y”, “@modelcontextprotocol\/server-brave-search”],
\n “env”: { “BRAVE_API_KEY”: “your_brave_api_key” }
\n }
\n }
\n}<\/p>\nWhat\u2019s taking place in every of the three servers:<\/h3>\n
Getting a GitHub token, step-by-step:<\/h4>\n
Claude Code: Including MCP Servers through CLI<\/h2>\n
Including a Server with claude mcp add<\/h3>\n
\n — npx -y @modelcontextprotocol\/server-postgres
\n postgresql:\/\/localhost:5432\/mydb<\/p>\n
\n Config Location
\n Who Sees It
\n Finest For<\/p>\n
\n ~\/.claude.json (per-project)
\n You solely
\n Private instruments, like GitHub, Slack, your DB<\/p>\n
\n .mcp.json in mission root
\n Your complete staff (dedicated)
\n Shared servers like Linear, Sentry<\/p>\n
\n ~\/.claude.json (top-level mcpServers key)
\n Solely you, all initiatives
\n Private instruments you need all over the place, not project-specific<\/p>\n<\/figure>\n<\/div>\n
\n That means<\/p>\n
\n Prepared to make use of<\/p>\n
\n Reachable, however wants a browser sign-in or a token<\/p>\n
\n Linked, however couldn\u2019t listing its instruments. Run claude mcp get for element<\/p>\n
\n Server didn\u2019t reply. Run the uncooked command manually to see the actual error<\/p>\n
\n The connection try itself threw an error<\/p>\n
\n A project-scoped server you haven\u2019t accredited but<\/p>\n<\/figure>\n<\/div>\nThe Finest MCP Servers to Set up First<\/h2>\n
\n What It Allows
\n Set up Package deal \/ Technique
\n Finest For<\/p>\n
\n Create points, evaluation PRs, search code throughout repos
\n Docker: ghcr.io\/github\/github-mcp-server
\n All builders<\/p>\n
\n Learn, search, and organise information in your machine
\n @modelcontextprotocol\/server-filesystem
\n Everybody<\/p>\n
\n Reside net search with out rate-limit friction
\n @modelcontextprotocol\/server-brave-search
\n Analysis duties<\/p>\n
\n Question and handle your database in plain English
\n @modelcontextprotocol\/server-postgres
\n Information \/ backend groups<\/p>\n
\n Learn pages, question databases, replace docs from Claude
\n Official Notion MCP server (OAuth)
\n Information-heavy groups<\/p>\n
\n Learn channels, search historical past, ship messages
\n @modelcontextprotocol\/server-slack
\n Workforce comms + ops<\/p>\n
\n Up-to-date library docs, fixing the stale coaching information downside
\n By way of npx or Claude Code CLI
\n Builders constructing with APIs<\/p>\n
\n Browser automation and net testing straight in Claude Code
\n @playwright\/mcp
\n QA and frontend engineers<\/p>\n<\/figure>\n<\/div>\nFrequent Errors and Fixes<\/h2>\n
Error 1: Standing exhibits \u201cFailed to attach\u201d or \u201cConnection error\u201d<\/h4>\n
Error 2: Instruments don\u2019t seem after connecting<\/h4>\n
Error 3: JSON syntax error silently breaks all servers<\/h4>\n
Error 4: Relative paths fail<\/h4>\n
Error 5: Context window will get eaten by instrument definitions<\/h4>\n
Superior: Construct Your Personal MCP Server<\/h2>\n
\ndef get_data(question: str) -> str:
\n “””Fetch information from my inside API.”””
\n return my_api.fetch(question)<\/p>\n
\n mcp.run()<\/p>\nConclusion<\/h2>\n
Incessantly Requested Questions<\/h2>\n