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.
Server URL: https://pearmcp.com/api/mcp
Transport: HTTP streamable
Secret Token: Bearer <your Pear API key>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
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.
Choose a useful first workflow
Start with a read. Ask which calendars are connected, find an event in a specific date range, or search a mail folder for a message you already know. Specify the account and timezone when they matter.
For Apple accounts, see iCloud setup and services and iCloud Mail workflows. For Microsoft accounts, see Microsoft 365 setup, Outlook Mail, and Microsoft To Do.
Apple Reminders availability depends on the Apple account. For Apple, Pear can read and write only the legacy reminder lists Apple still exposes through CalDAV. If the account has been upgraded to Apple's newer Reminders store, Pear cannot access those native lists and does not copy them into a separate reminder store. Apple may instead return compatibility placeholders, such as repeated "Where are my reminders?" items; Pear did not create them. Pear's safe fallback hides known placeholders and blocks writes to affected lists. Reconnecting iCloud or replacing the App-Specific Password will not change this Apple limitation. Calendar, Contacts, and Mail are unaffected, and Microsoft To Do uses Microsoft Graph and is unaffected. Full modern Apple Reminders access would require an Apple-platform companion using EventKit with the user's permission; Pear does not currently provide one. Google Workspace remains coming soon.
Pear exposes tools allowed by your account and permissions. Your AI client decides when to call them. Review recipients, dates, and content before approving writes. Read how Pear handles your data and the current plans before expanding the workflow.
Sources and compatibility status
Documentation checked on 10 September 2026. Setup is documented; a completed Pear client connection remains unverified.
