claudhopper

MCP servers

The Model Context Protocol is how Claude Code reaches things outside your repo: your tickets, your docs, a browser, a database. You add a server with one command and Claude gets new tools.

Every server you add is a door. Know who you are letting in.

Facts checkedNov 11at the source

Add your first server

  1. Pick one you trust. The maker's own server is the safe default.
  2. Add it. Remote servers use HTTP. Local ones run a command on your machine.
  3. Sign in if it asks. Run /mcp inside Claude Code to see status and to authenticate with servers that use OAuth.
  4. Use it. Just ask. Claude sees the new tools.
A remote (HTTP) server
claude mcp add --transport http notion https://mcp.notion.com/mcp
A local (stdio) server
claude mcp add --env AIRTABLE_API_KEY=YOUR_KEY --transport stdio airtable \
  -- npx -y airtable-mcp-server

The -- separates Claude's own options from the command that runs the server.

Who can see the server

ScopeWho gets itStored in
Local (the default)You, in this project~/.claude.json, under the project's path
Project (--scope project)Everyone on the repo, through git.mcp.json in the project root
User (--scope user)You, in every project~/.claude.json
Housekeeping
claude mcp list
claude mcp get notion
claude mcp remove notion

Before you connect anything

  • Check that you trust the server. It gets whatever access you give it.
  • Servers that fetch outside content can carry prompt injection back in with it.
  • Claude Code asks for your approval before using project-scoped servers from .mcp.json.

Three add-ons people keep installed are on the third-party page: Playwright MCP, Context7 and the GitHub MCP Server.

Claudhopper move: Add servers at project scope when the whole team needs them and user scope when only you do. The default, local, is the one nobody meant to pick.

Source: the Claude Code documentation at code.claude.com/docs, read on November 11, 2026.

Advertisement