Connect your tools (MCP)

MCP (Model Context Protocol) is a universal connector. Add one for a tool you already use, and Claude gains the ability to work with it directly — pull a Notion doc, query a database, check a Sentry error — instead of you copy-pasting back and forth. One command to add a server; new abilities appear.

MCP — the Model Context Protocol — is best understood as a standard plug. Before it, connecting Claude to each new tool meant a bespoke integration. With it, any tool that speaks the protocol snaps in the same way, and Claude gains the ability to read and act in it directly: pull a Notion doc, query your database, check a Sentry error, open a pull request — no more copy-pasting back and forth as the courier.

Servers come in two shapes. A remote one is a URL you point at (a hosted service like Notion’s); a local one runs on your machine over stdio (like the Playwright browser server). Either way it’s one claude mcp add command to connect, and /mcp shows you everything currently wired up. New abilities just appear in the session.

Two things to hold onto. First, trust matters: a connector can read and act inside the tool you point it at, so only add servers you’d trust with that access. Second, the signal that you need one — if Claude keeps asking you to go fetch the same data by hand, that tool has earned an MCP server. Start with the one you touch daily; the payoff is immediate.

claude mcp add --transport http notion https://mcp.notion.com/mcp

claude mcp add --transport stdio playwright -- npx -y @playwright/mcp@latest

/mcp