First MCP to install: pick the platform you work with most. For marketers that's usually Google Ads, Meta Ads, Klaviyo, or GA4. This lesson walks through installing one - same pattern applies to the rest.

Step 1: Decide which MCP you need

Ask yourself: which platform am I pulling data from most often right now?

• Building weekly reports for ecommerce clients? Start with Google Ads + Meta + Klaviyo.
• Doing SEO? Start with Google Search Console + DataForSEO.
• Running email? Start with Klaviyo or Mailchimp.
• Analytics-heavy? Start with GA4.

Pick one. Install it. Use it for a week. Then add the next.

Step 2: Tell Claude what you want

Installing an MCP is just telling Claude in plain English. Example:

Install the Klaviyo MCP for me. Walk me through the authentication steps. Add the configuration to my project's .mcp.json file.

Claude

1. Tells you what the Klaviyo MCP can do
2. Walks you through auth (usually opening a browser, signing in, approving)
3. Writes the connection config to .mcp.json
4. Tests the connection with a simple query Pattern applies to almost any MCP. Replace "Klaviyo" with the platform name.

Step 3: What .mcp.json looks like

.mcp.json is a file in your project folder that tells Claude which MCPs to activate for this project. You don't edit it manually. Claude does.

Example (simplified)

{ "mcpServers": { "klaviyo": { "url": "https://mcp.klaviyo.com", "auth": "oauth" }, "google-ads": { "url": "https://api.pipeboard.co/mcp/google-ads", "auth": "api-key" } } }

When Claude starts in this project, it connects to Klaviyo + Google Ads. Other projects without this file don't connect to anything - keeps token overhead scoped.

Step 4: Test it works

Ask Claude something that requires the MCP you just installed:

Pull a list of the Klaviyo campaigns from the last 30 days. Show me campaign name, send date, opens, clicks, revenue.

Claude uses the Klaviyo MCP to fetch the data and shows you the table. If it works, install successful. If it errors, Claude explains what went wrong.

Common errors

Authentication expired

OAuth tokens expire. Claude asks you to re-authenticate - same flow as the initial install.

Account access

For multi-account platforms (Google Ads with multiple customer IDs, Meta Ads with multiple ad accounts), you might need to specify which account you want:

Claude, use the [account-id] Google Ads account for this query.

Or set it in project CLAUDE.md so it's automatic for this project:

Account config

Google Ads customer ID: 123-456-7890

Rate limits

Some MCPs have per-minute or per-hour rate limits. Claude will pause and retry automatically. If you hit limits often, Claude can batch requests or spread them over time.

Installing a 2nd MCP (simpler)

Same pattern

Install the Meta Ads MCP in this project. Walk me through auth. Add to .mcp.json.

Claude adds the new MCP to the same .mcp.json file. Both now activate on session start.

Power-user tips

• Install MCPs per project, not globally - keeps token overhead low and isolates client data
• Share .mcp.json via git - when a teammate pulls the repo, they get the same MCP setup
• Ask Claude what's available - "what MCPs are connected in this project?" or "what can I do with the Klaviyo MCP?"
• Disable MCPs you're not using this session - tell Claude "disconnect the [MCP] for this session"
• Check claude.ai/settings/connectors - browse the full list of officially supported platforms

Action items

☐ Pick the platform you work with most often

☐ Tell Claude to install the MCP for that platform in a project

☐ Complete the authentication flow

☐ Test with a simple query - confirm data comes back

☐ Check that .mcp.json was written in the project folder

Next lesson: MCP vs CLI - when to use each.

Exercises

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