What a robot could do with your mailbox
Imagine asking your robot, "Did the hotel send my booking?" or "What time is my next meeting?" A custom conversation app can request that information through Pear, then turn the result into a spoken answer. Pear supplies permitted email and calendar tools. The robot application supplies speech, the AI model and the connection between them.
This is a developer guide. Pear has not tested these workflows on a physical humanoid robot, and does not ship a robot app or a hardware adapter. A built-in voice assistant does not by itself mean a robot can connect to Pear.
Which humanoids have a development path?
Unitree G1 EDU: Unitree lists secondary development for the EDU model. A developer can investigate its SDK and audio interface, then build an application that connects to Pear. Do not assume the standard G1 has the same access.
Unitree G1 EDU email and calendar integration guide
Booster K1 and T1: Booster documents a Python Agent framework, an SDK and speech capabilities. These are useful building blocks for a custom mailbox app. Pear is not an installed Booster Agent.
Booster K1 and T1 integration guide
1X NEO: 1X describes a voice companion and has announced a developer platform. In the public material checked for this guide, we did not find a complete owner-facing procedure for connecting a private Pear MCP endpoint. Treat a Pear connection as unresolved.
Figure and Tesla Optimus: the public product pages checked for this guide did not provide an owner-facing Pear setup procedure. We cannot turn demonstrations of conversation or household tasks into email-integration instructions.
Reachy Mini is a desktop companion rather than a full humanoid. Its conversation app accepts MCP tools through Hugging Face Spaces, not arbitrary MCP URLs. A direct Pear URL is not a drop-in configuration for that installer.
Build the conversation before connecting the hardware
First make a private app on your development computer. Use typed requests and sample email summaries to check the experience. Add Pear through an authenticated MCP client and check pear_provider_status. Then try a known message in a specific connected mailbox. Only after that should you connect the robot microphone and speaker through its supported SDK.
LiveKit is useful if you are writing the Python voice agent. ElevenLabs is useful if you want to configure a hosted conversational agent. Neither product automatically installs a Pear integration on a robot. Both require a separate account and can have their own usage charges.
Start with a private, read-only morning briefing
Let the owner ask for a calendar summary or selected email subjects. Bind each session to the correct owner and connected account. A shared speaker or a familiar voice is not proof of identity. Keep the assistant private; anyone who can invoke a shared agent could otherwise reach the mailbox behind its key.
Enable only provider status and the read tools the workflow needs. Do not expose sending, deletion or robot motion tools to this first assistant. Treat text inside emails as data, not instructions. Ask before speaking message bodies where other people could hear them.
Pear does not provide identity recognition, robot control, speech synthesis or a guarantee that the AI will choose the right tool. Your application must handle access, timeouts, interrupted speech and errors. Never describe an unavailable mailbox as having no unread messages.
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
Research checked on 10 September 2026. This is a custom development path, not a tested Pear robot integration.
Booster developer documentation
NEO product and voice interface
