Claude Code MCP: Setup Guide for Useful MCP Servers

Setup Strategy

Start with one or two servers that map to repeated work. Filesystem and GitHub usually provide the best early return.

Example Config

Keep secrets outside committed config and document expected environment variables in CLAUDE.md.

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

Pair With CLAUDE.md

Use CLAUDE.md to tell Claude when to use MCP, which commands are safe, and what to verify before handoff.

Claude Code MCP Workflow

Claude Code works best when MCP is paired with explicit instructions that tell the agent when to use each tool and what to verify after tool use.

• Use CLAUDE.md for durable project guidance.
• Use mcp.json for external capabilities.
• Use tests and build commands as final validation gates.
• Keep destructive or write-heavy tools behind clear review expectations.

Permission Boundaries

Before adding a server, decide whether Claude Code needs read access, write access, or only a narrow project scope. This keeps powerful agent workflows easier to trust.

MCP Setup Order

Claude Code MCP works best when setup follows a predictable order: document the repo, add the smallest useful server, verify the command, then expand permissions only when the workflow proves useful.

• Write the expected commands and project constraints in CLAUDE.md first.
• Start with filesystem or GitHub before databases and write-capable tools.
• Use read-only database users for inspection and debugging workflows.
• Record token owners, rotation steps, and fallback instructions for the team.

What To Put In CLAUDE.md

MCP config tells Claude Code what tools exist, but CLAUDE.md explains when to use them. Keep that guidance practical so the agent does not reach for external tools when local files and tests are enough.

Use GitHub MCP when a task references an issue or PR.
Use filesystem MCP only within this repository.
Use browser checks for UI changes before handoff.
Do not query production databases without explicit approval.

Team Review Checklist

Before sharing a Claude Code MCP setup, review it like developer infrastructure. The important question is not whether the server works once; it is whether the team understands the access it grants and how to recover when it fails.

• Every server has an owner and a reason to exist.
• Secrets stay in environment variables or a managed secret store.
• Dangerous write actions are documented or disabled.
• The same setup can be recreated on a new machine.

FAQ