# Humanoid robots, email and calendars: a developer guide

Can a humanoid robot check your iCloud email? Compare Unitree, Booster, NEO, Figure and Optimus development paths and what Pear can provide.

## 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](https://pearmcp.com/guides/unitree-g1)

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](https://pearmcp.com/guides/booster)

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.

[LiveKit Python MCP setup](https://pearmcp.com/guides/livekit)

[ElevenLabs agent MCP setup](https://pearmcp.com/guides/elevenlabs)

## 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.

## 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

Research checked on 10 September 2026. This is a custom development path, not a tested Pear robot integration.

- [Unitree G1 model comparison](https://www.unitree.com/g1/)
- [Booster developer documentation](https://docs.booster.tech/developer-guide/)
- [NEO product and voice interface](https://www.1x.tech/order)
- [1X developer-platform announcement reference](https://www.1x.tech/discover/tom-sanocki-vp-engineering)
- [Figure official site](https://www.figure.ai/)
- [Tesla AI and robotics](https://www.tesla.com/AI)
- [Reachy Mini conversation app](https://github.com/pollen-robotics/reachy_mini_conversation_app)