MCPs are scoped per project via the .mcp.json file. A project for an ecommerce client connects to Google Ads + Meta + Klaviyo. A project for a lead-gen client connects to Google Ads + LinkedIn + HubSpot. Different projects, different connections, different data isolation.

Why scope per project

Reasons to keep MCPs project-scoped, not global

• Token efficiency - only load MCPs you're actually using
• Data isolation - one client's data doesn't leak into another's session
• Easier auth - each project's auth is independent
• Cleaner mental model - opening a project folder = opening that project's context

The .mcp.json pattern

Every project that uses MCPs has a .mcp.json file at the root:

my-project/ ├── CLAUDE.md ├── .env ├── .mcp.json ← MCP config for this project └── (other files)

Claude reads .mcp.json on session start and activates only the MCPs listed. No .mcp.json = no MCPs active (pure local work).

Multi-account MCPs

Some platforms have multiple accounts under one login. Google Ads MCC (manager accounts) have multiple customer IDs. Meta Business Manager has multiple ad accounts.

Tell the project's CLAUDE.md which specific account to use

Client context

Google Ads customer ID: 123-456-7890

Meta Ads account ID: act_1234567890

Klaviyo account: client-acme-prod

Claude references these when making calls - one less thing you have to specify every instruction.

Checking what's active

What MCPs are active in this session?

Or in Claude Code directly

terminal
/mcp

Shows the list with status (connected / error / stale). Useful when something isn't working.

Disabling an MCP mid-session

If you realise you don't need an MCP that's loaded

Disconnect the Meta Ads MCP for the rest of this session. I only need Google Ads today.

Reduces overhead for the remaining session. Reconnects next session automatically.

Temporary MCP install

Sometimes you need an MCP just once

Install the DataForSEO MCP for this session only. Don't add it to .mcp.json - just connect for now.

Claude connects temporarily. Next session, it's gone. Useful for one-off research that doesn't warrant a permanent connection.

Common project configur ations

Ecommerce client

MCPs

• Google Ads (Pipeboard)
• Meta Ads (Pipeboard)
• Klaviyo (Claude Connector)
• GA4 (Claude Connector)
• Shopify (local MCP or wp-skills connector)
• Supabase (for memory + any client-specific data)

Lead-gen client

MCPs

• Google Ads (Pipeboard)
• LinkedIn Ads (3rd-party)
• Google Search Console (Claude Connector)
• GA4 (Claude Connector)
• HubSpot (via Supermetrics or custom)
• Supabase

SEO-focused client

MCPs

• Google Search Console (Claude Connector)
• DataForSEO (Local MCP)
• GA4 (Claude Connector)
• Supabase

Research / one-off project

MCPs

• Supermetrics (cross-platform data)
• DataForSEO (for SERP + keyword data)
• Supabase (for memory)

Security posture

MCPs come with different permission levels

• Read-only (default, recommended) - Claude can pull data, not change anything
• Read + write (explicit opt-in) - Claude can mutate the platform (create campaigns, send emails, post)

Default every MCP to read-only. Only enable write access when you specifically need it and you're ready to approve mutations carefully (Module 03 permission rules apply).

Install the Google Ads MCP in read-only mode. I don't want Claude to be able to make mutations yet.

Power-user tips

• Commit .mcp.json to git - anyone else who pulls the project gets the same MCP config
• Keep .env out of git (always) - individual auth stays per-machine
• Review .mcp.json quarterly - remove MCPs you stopped using
• Use Supermetrics for long-tail platforms - one MCP covers 150+ sources; avoids installing 10 separate small MCPs
• Name your MCPs clearly in .mcp.json - "klaviyo-acme" not "klaviyo" if you have multiple clients

Action items

☐ Check each of your projects has a .mcp.json (or doesn't need one)

☐ Add platform-specific account IDs to your project CLAUDE.md

☐ Run /mcp in a session to see active connections ☐ Default every MCP to read-only unless you need writes

☐ Remove MCPs you aren't using this quarter

Next lesson: Security + read/write rules for MCPs.

Exercises

1. Review the concepts covered in this lesson: Manage MCPs per project.
2. Write down your key takeaway from this lesson.
3. Practice running any commands or prompts mentioned above inside your terminal.