MCP expands what Claude Code can reach beyond the repository. Treat every server as a new trust boundary and review credentials, scopes and data paths before enabling it.
1. Start from a workflow need
Choose one concrete need such as reading issue metadata, querying internal docs or using a browser tool. Do not connect tools “just in case.”
2. Use the provider’s official setup
Install or configure the MCP server from its trusted documentation. Keep secrets in supported environment or credential stores instead of pasting them into prompts.
3. Inspect the exposed tools
Before asking Claude Code to act, list or review what the server makes available. Look for write, delete, send, admin or broad search capabilities.
4. Test read-only first
Ask for one narrow retrieval and compare the returned data with the source system. Confirm account, workspace and object boundaries are correct.
5. Add writes only with review
If the workflow needs external changes, add the smallest permission needed and keep an approval step before consequential actions.
Use this MCP connection in read-only mode first. List the tools you can access, then retrieve only [specific object]. Do not create, edit, send or delete anything. Show me the exact write-capable tools separately.
Connecting an unreviewed server; pasting tokens into chat; assuming “MCP” means safe by default; enabling broad writes before testing the account and object scope.
Finish check
You can name the server, account, tools, credential path and exact write capabilities, and a read-only test returned the expected source data.