# ElevenLabs Agents MCP setup for Pear email tools Configure a private ElevenLabs agent with Pear MCP, a secret Authorization header and selected read tools. Includes access requirements and robot integration limits. ## Connection and authentication Use the authentication method shown for each client surface. | Client surface | Authentication | Setup guide | | --- | --- | --- | | ElevenLabs Agents | API key | Setup guide available | ## When ElevenLabs is useful ElevenLabs Agents can provide the hosted conversation layer for a private voice application. Adding Pear gives that agent a documented route to connected email and calendar tools. A robot still needs a supported application and audio connection to the agent. This is configuration guidance. Pear has not completed a live ElevenLabs authentication and mailbox test for this page. An ElevenLabs account and its usage charges are separate from your Pear plan. ## 1. Check workspace access ElevenLabs documents MCP as disabled by default for a workspace. A workspace member can enable it by accepting the terms when adding the first server; this is a workspace-wide setting. Workspaces using Zero Retention Mode or HIPAA compliance cannot use MCP under the documentation checked for this guide. Create a private agent for your own use and connect your mailbox in Pear. Access to the agent must be authenticated and limited to the mailbox owner. A public widget or publicly callable agent must not share your personal Pear connection with visitors. ## 2. Add Pear as a custom MCP server Open the MCP server integrations dashboard and choose Add Custom MCP Server. Name it Pear, choose HTTP streamable transport, and use https://pearmcp.com/api/mcp as the server URL. ElevenLabs documents Secret Token as the Authorization header value. Store the complete value in its secret field: the word Bearer, a space, and your Pear API key. Do not include quotes, place the key in the URL, or configure a second Authorization header. Keep the integration private to the intended workspace members. ```text Server URL: https://pearmcp.com/api/mcp Transport: HTTP streamable Secret Token: Bearer ``` Save the integration and use its connection test to list tools. Attach it to the private agent. If authentication fails, verify the complete Authorization value and that the key has not been revoked; do not replace the endpoint with an invented SSE URL. ## 3. Limit the first agent to mailbox reads Use fine-grained tool control to enable pear_provider_status, pear_list_emails and pear_read_email for the prototype. Leave other tools disabled and keep approval required while testing. Tool approval is not proof of the speaker's identity, so the private access requirement still applies. Ask for provider status, then a message you already know in the selected mailbox. Compare the result with the original. Test a disconnected provider and a revoked key. The agent should explain failure rather than claim there are no messages. Start with subjects and ask before reading message bodies aloud. ## 4. Decide whether you need robot hardware A private voice conversation can be useful on its own. For a humanoid, the robot developer must connect microphone input, audio output and session access through supported vendor interfaces. Adding an MCP server in ElevenLabs does not make NEO, Figure, Optimus, Unitree or Booster connect automatically. [Humanoid robot development paths](https://pearmcp.com/guides/humanoid-robots) Consider what the voice platform retains and who can access transcripts before using real mail. Pear data handling and the voice provider's policies both matter. Email contents are untrusted data and must not be treated as instructions to change the agent's behavior. ## Provider limits and plans Apple iCloud and Microsoft 365 are available. Google Workspace is coming soon. Pear cannot access Apple's upgraded Reminders store; its hosted CalDAV connection is limited to legacy reminder data. Microsoft To Do is unaffected. Available tools depend on your connected providers, scopes, plan and readiness. Free includes 50 counted provider actions per month. One AI request can use several provider actions. Voice, model and robot costs are separate. Review content and recipients before approving writes. [iCloud setup](https://pearmcp.com/icloud-mcp-server) | [iCloud Mail](https://pearmcp.com/ai-icloud-mail) | [Microsoft 365](https://pearmcp.com/microsoft-365-mcp-server) | [Data handling](https://pearmcp.com/data-handling) | [Plans](https://pearmcp.com/pricing) ## Sources and compatibility status Documentation checked on 10 September 2026. Setup is documented; a completed Pear client connection remains unverified. - [ElevenLabs MCP configuration, access and approvals](https://elevenlabs.io/docs/eleven-agents/customization/tools/mcp) - [ElevenLabs MCP integration security](https://elevenlabs.io/docs/eleven-agents/customization/tools/mcp/security)