Step-by-Step Study Material

Step 1: Understanding the Foundation — What is MCP?

MCP = Model Context Protocol

Think of MCP as a bridge that connects an AI assistant (Claude) to external tools and services.

Claude (AI Assistant) ←——MCP Bridge——→ ElevenLabs (Voice/Agent Platform)

Without MCP: You switch between Claude and ElevenLabs separately With MCP: You manage everything from inside Claude

Key Insight: MCP allows Claude to take actions on your behalf, not just give advice

---

Step 2: Understanding ElevenLabs' Role

ElevenLabs is a platform that provides:

• Voice agents — AI-powered voice interactions
• Chat agents — conversational AI interfaces
• Agent configuration — settings, behaviors, and monitoring tools

Before this integration, managing these agents required logging into ElevenLabs directly.

---

Step 3: What the Hosted MCP Actually Does

The ElevenLabs MCP gives Claude a curated set of tools specifically designed for managing ElevenAgents.

Concrete Examples of What Claude Can Now Do:

Important Concept: The tool set is deliberately scoped — meaning ElevenLabs intentionally limited what Claude can do. This keeps actions predictable and safe.

---

Step 4: Understanding "Hosted" vs. "Local" MCP

This is a critical distinction:

Hosted MCP (New)

You → Claude → ElevenLabs Hosted Server
              (ElevenLabs manages this)

• ✅ Nothing to install or maintain
• ✅ No API keys needed
• ✅ Uses OAuth for secure sign-in
• ✅ Revoke access anytime
• ✅ Best for: General users and teams

Local MCP (Original, still available)

You → Claude → Your Local Machine → ElevenLabs
              (You manage this)

• ⚙️ Runs on your own machine
• ⚙️ Requires your own API key
• ⚙️ More control for technical users
• ✅ Best for: Developer workflows

---

Step 5: Understanding the Security Model

Security works through three layers:

Layer 1: OAuth Sign-In
└── Sign in once, no passwords stored in Claude

Layer 2: Revocation Control
└── Cancel access from Claude settings OR ElevenLabs account settings

Layer 3: Team Access Control
└── Admins control what team members' Claude sessions can access

OAuth Explained Simply:

Instead of giving Claude your password, OAuth gives Claude a temporary permission token — like a hotel key card that only opens specific doors

---

Step 6: How to Get Started (Practical Steps)

Step 1: Go to Claude's connectors directory
         ↓
Step 2: Find and click "ElevenLabs"
         ↓
Step 3: Sign in using OAuth (one-time setup)
         ↓
Step 4: Claude now has access to your ElevenLabs agents
         ↓
Step 5: Start managing agents in natural language

---

Step 7: The Bigger Concept — Why This Matters

This integration represents a workflow shift:

Old Workflow:

Think about change → Open ElevenLabs → Make change → Return to Claude → Continue work

New Workflow:

Think about change → Tell Claude → Claude makes change → Continue work

Core Philosophy: "More of the work of managing agents now happens inside AI assistants — your tools should meet you there."

This reflects a broader trend: AI assistants becoming operational hubs, not just advisors.

---

Knowledge Check ✅

Test yourself with these questions:

1. What does MCP stand for, and what is its function?
2. What is the difference between the Hosted MCP and the Local MCP?
3. Why does ElevenLabs deliberately limit the tools available to Claude?
4. How does OAuth improve security compared to API keys?
5. Name two tasks Claude can perform on your ElevenLabs agents

---

Summary Card