Claude Code Field Guide
22 / 35

MCP Servers

Model Context Protocol connects Claude Code to the tools your business actually lives in — Notion, Airtable, Slack, databases, and more.

Still accurate
Currency check: Core concept and mechanics unchanged; the ecosystem of available servers has simply grown considerably.

By default Claude Code only sees your local files — but your actual work lives across Notion, Airtable, Asana, Slack, GitHub, databases, and dozens of other tools. MCP (Model Context Protocol) is the open standard that connects Claude Code to those external systems: once a server is connected, Claude can read from and write to that tool directly, inside the same conversation, instead of you copy-pasting data in and out by hand.

Servers are added with claude mcp add (local to your project, shared with your team via a checked-in .mcp.json, or available across every project of yours), and managed with /mcp. Tool definitions from connected servers are deferred by default — only names and descriptions load into context until a specific tool is actually used — which keeps a long list of connected servers from bloating every conversation.

Closing the loop between a bug report and a PR

With a project-tracker MCP server and a GitHub MCP server both connected, “implement the feature described in ticket ENG-4521 and open a PR” becomes a single instruction: Claude reads the ticket, writes the code, and opens the PR, without anyone manually relaying information between the two tools.

Answering a data question directly

A PM connects a read-only database MCP server and asks “what's our signup total this month?” directly in a Claude Code session — getting a live, queried answer rather than pinging an analyst or opening a separate BI tool.