What is MCP?
Model Context Protocol (MCP) is Anthropic’s standard for connecting AI assistants to external tools and data sources. It enables agents to:- Query databases directly
- Interact with APIs
- Access file systems
- Control browsers
- Connect to any custom service
Configuration
Location
MCP servers are configured in.claude/settings.json:
Global vs Project
Common MCP Servers
Supabase
list_projects,get_projectexecute_sql,apply_migrationlist_tables,list_extensionsdeploy_edge_function
Chrome DevTools
take_screenshot,take_snapshotclick,fill,navigate_pageevaluate_scriptlist_console_messages
Firecrawl (Web Scraping)
firecrawl_scrape- Extract page contentfirecrawl_search- Search the webfirecrawl_map- Discover URLs on a sitefirecrawl_crawl- Crawl multiple pages
Grafana
search_dashboards,get_dashboard_by_uidquery_prometheus,query_loki_logslist_alert_rules,list_incidents
Context7 (Documentation)
resolve-library-id- Find library documentationquery-docs- Search library docs
Environment Variables
Reference Variables
Use${VAR_NAME} syntax to reference environment variables:
Security Best Practices
- Store secrets in
.env(git-ignored) - Use
${VAR}references, not hardcoded values - Rotate API keys regularly
- Use minimal required permissions
Custom MCP Servers
Building Your Own
Create a custom MCP server for your tools:Registering Custom Servers
Permissions
Tool Approval
Configure which MCP tools auto-approve in settings:Permission Patterns
Debugging
Check Server Status
Common Issues
Verbose Logging
Squad Integration
Per-Squad MCP Servers
squads-cli resolves each squad’s MCP config through a three-tier lookup,
falling back to the next tier if the current one is missing:
- User override —
~/.claude/mcp-configs/{squad}.json - Generated from context —
~/.claude/contexts/{squad}.mcp.json(built from a squad’scontext.mcplist) - Fallback — your global
~/.claude.json
gh, gcloud, psql, …) over MCP wherever a good CLI alternative exists,
and only reaches for MCP servers you explicitly configure.
Agent-Specific Tools
Best Practices
- Start with official MCP servers before building custom
- Use project-level config for project-specific tools
- Document required environment variables
- Test MCP servers independently before integration
- Limit tool permissions to minimum required
Related
Secrets Management
Secure API keys for MCP servers
Hooks
Automate actions around tool calls