What MCP is and how to inspect or add one connection safely

Understand MCP in plain English

MCP gives Claude Code access to tools outside your project folder. That might mean documentation, GitHub, databases, or other services. Every MCP connection expands what Claude can read or do, so pause and ask yourself what access you are actually giving it before you connect anything.

Inspect your current MCP setup

Use the real inspection screens instead of asking Claude to guess. In Claude Code, type `/mcp`. In a regular terminal, run this command:

Practice with one safe, read-only MCP server

If you want to practice the mechanics safely, add a read-only documentation server instead of a write-capable work server. That gives you practice without giving Claude power over your project. Run this in a normal terminal:

Verify the connection in both places

After adding the server, check it in the CLI and in Claude Code. Run `claude mcp list` again and reopen `/mcp` inside Claude Code. Then ask Claude one simple docs question so you can confirm the server is actually usable.

Apply the trust rule before any future server

Only connect official servers from sources you trust, and only when you need that access right now. Official docs, official provider docs, and a clear understanding of what data the server can read or actions it can take are the minimum bar. If you cannot explain what a server can access, you are not ready to connect it.