Skip to content
Grok client guide

Connect Grok and Grok Build to Pear MCP

Use Pear's documented Grok connector, Grok Build, or xAI API path for Apple iCloud and Microsoft 365. Current client permissions apply, and Grok Business or Enterprise teams need an administrator to provision custom connectors first.
Quick setupOAuth or API keyGrok connectorsGrok BuildOAuth / APIRemote MCPSetup guide available

Connection proof

The values Grok asks for first.

Pear hosted endpoint
https://pearmcp.com/api/mcp
Authentication
OAuth / API
Setup surface
Manual connector

xAI documents custom connectors and remote MCP tools; Business and Enterprise teams require admin provisioning and Team Read-Write permission.

Setup guide available. Host-specific verification remains tracked separately.

Official setup reference

1. Create your Pear account

Sign up at pearmcp.com, then connect Apple iCloud or Microsoft 365. Grok chat can use Pear OAuth. Grok Build and xAI API workflows can use a Pear API key from Settings.

Sign Up Free

2. Add Pear as a Grok connector

Grok supports built-in connectors and custom MCP connectors. Add Pear as a custom MCP connector when you want Pear's unified Apple iCloud and Microsoft 365 tool surface rather than separate first-party office connectors. Use the hosted server URL:

On Grok Business and Enterprise, a team admin must provision Pear from the cloud console before members can connect it. Adding or removing connectors requires Team Read-Write permission. If you do not have that permission, ask your team admin to add Pear first.

https://pearmcp.com/api/mcp
  1. For an individual account, open grok.com/connectors. Managed-workspace members use the Pear connector their admin provisioned.
  2. Click New Connector, then choose Custom.
  3. Paste the Pear server URL.
  4. Complete Pear sign-in, or provide your Pear API key if Grok asks for a token.

3. Use Pear from Grok Build

Grok Build can inspect MCP servers available to your coding environment. After Pear is configured, run:

grok inspect
grok

Inside the Grok TUI, open /mcps to check Pear status. Grok Build is compatible with Claude Code style MCP configuration, so teams already using Pear there can usually reuse the same server entry. If Grok Build does not show Pear, re-run the inspect command from the project directory that contains your MCP config.

For xAI API builders

If you call Grok through the xAI API, pass Pear as a remote MCP tool. Keep the Pear API key on your server and send it as the MCP authorization value.

{
  "type": "mcp",
  "server_url": "https://pearmcp.com/api/mcp",
  "server_label": "pear",
  "server_description": "Pear MCP connects Grok to Calendar, Tasks, Contacts, and Mail.",
  "authorization": "Bearer YOUR_PEAR_API_KEY"
}

Try these prompts

  • What is on my calendar today and what should I prepare for?
  • Find a free 45-minute slot next week and create the meeting.
  • Create reminders for these action items and add due dates.
  • Search recent mail from this client and draft a reply I can review.

What Pear unlocks inside Grok

The available tools, reads, writes, and approvals depend on the current Grok surface, workspace role, connector configuration, and permission policy.

  • Use one hosted MCP server for Apple iCloud and Microsoft 365 workflows.
  • Read and write calendar events, tasks, contacts, and mail from Grok conversations.
  • Keep Google Calendar migration paths ready as Pear expands provider support beyond compatible IMAP/SMTP mailbox beta.
  • Use Pear in chat, coding, and API workflows without running a local bridge.

Grok and Grok Build workflows worth testing

  • Ask Grok to read mail context, create a follow-up task, and schedule the next meeting.
  • Use Grok Build to create release reminders while inspecting project instructions and MCP config.
  • Use the xAI API remote MCP path when you want Pear tools in your own Grok-powered app.
Grok + Pear

Put Grok to work across your providers.

Free includes 50 counted provider actions/month; Pro removes the cap.