#####   ######  #####    ###    #   #  ###  #   #  ######
##  ##  ##      ##  ##  ## ##   #   #   #   #   #  ##
#####   ####    #####   #   #   #   #   #   #   #  ####
##  #   ##      ##      ## ##    # #    #    # #   ##
##   #  ######  ##       ###      #    ###    #    ######

$ curl repovive.com/roadmaps/claude-code/claude-md-skills-hooks-mcp/adding-an-mcp-server

░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░████████████████████████████████████████████████████████████████████████████████████████

#####   ######  #####    ###    #   #  ###  #   #  ######
##  ##  ##      ##  ##  ## ##   #   #   #   #   #  ##
#####   ####    #####   #   #   #   #   #   #   #  ####
##  #   ##      ##      ## ##    # #    #    # #   ##
##   #  ######  ##       ###      #    ###    #    ######

$ curl repovive.com/roadmaps/claude-code/claude-md-skills-hooks-mcp/adding-an-mcp-server

Repovive

Adding an MCP Server - CLAUDE.md, Skills, Hooks & MCP | Claude Code | Repovive

Repovive.

Claude Code7 sections · 136 units8h total

Open in Course

Adding an MCP Server

claude mcp add and settings config

The fastest way to add an MCP server is the CLI:

claude mcp add --transport stdio github -- npx @modelcontextprotocol/server-github

Or configure it directly in .claude/settings.json under mcpServers:

{
  "mcpServers": {
    "github": {
      "command": "npx",
      "args": ["@modelcontextprotocol/server-github"]
    }
  }
}

There are $3$ scopes: local (just you, not in git), project (committed to .mcp.json at the project root, shared with team), and user (in ~/.claude/settings.json, across all your projects). I'd start with local scope while testing, then promote to project once you're happy with it.

Once connected, reference MCP resources with @github:repos/owner/repo/issues. Use /mcp to manage servers interactively.