Grok client guide1. Create your Pear account
Sign up at pearmcp.com, then connect Apple iCloud or Microsoft 365. Choose the Grok setup below that matches where you work.
Sign Up FreeApple Reminders compatibility
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.
Read the Apple Reminders compatibility note2. Connect Grok Web with OAuth
Pear’s Grok Web client is active.
Use pear_oauth_grok_web as the Client ID. Leave Client Secret blank, keep Token Auth Method set to None / PKCE only, and use PKCE S256 if Grok presents a PKCE choice.
Open Grok's connector settings, create a Custom connector, and enterhttps://pearmcp.com/api/mcp. Keep the authorization endpoint, token endpoint, and mcp: scopes that Grok discovers. In the OAuth Credentials Required dialog, enter the Client ID above and use the public-client settings shown here. No Pear API key is needed for this flow.
Select Save & Connect, sign in to Pear, approve the connection, and return to Grok.
Grok Business and Enterprise workspaces require a team admin to provision Pear from the cloud console before members can connect it. Adding or removing connectors requires Team Read-Write permission.
Leave Client Secret empty. Pear does not issue a Grok client secret because this is a public OAuth client protected by PKCE. Never paste apear_sk_... value into Grok's Client ID or Client Secret fields; Pear API keys are Bearer credentials for the separate Grok Build and xAI API paths below.
3. Use Pear from Grok Build
Store your Pear API key in the PEAR_API_KEY environment variable without committing it. Then add Pear through Grok Build's documented static header path:
grok mcp add --transport http pear https://pearmcp.com/api/mcp \
--header 'Authorization: Bearer ${PEAR_API_KEY}'
grok mcp doctor pear
grok inspect
grokInside the Grok TUI, open /mcps to check Pear status. xAI also documents compatible Claude, Cursor, and project MCP configuration files.
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. The example reads the key from the server environment rather than embedding it in source.
const pearApiKey = process.env.PEAR_API_KEY;
if (!pearApiKey) throw new Error('Missing PEAR_API_KEY');
const pearMcpTool = {
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 ${pearApiKey}`,
};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 Microsoft To Do tasks for these action items, or first confirm Apple exposes a usable legacy CalDAV list.
- Search recent mail from this client and draft a reply I can review.
What the Grok paths can expose
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 when the chosen Grok surface exposes and invokes the corresponding Pear tools.
- Keep Google Calendar migration paths ready as Pear expands provider support beyond compatible IMAP/SMTP mailbox beta.
- Start Pear OAuth from Grok Web with the active production Client ID, or use the documented coding and API paths without running a local bridge.
Grok workflows to try
- Once connected, ask Grok to read mail context, create a follow-up task, and schedule the next meeting.
- Use Grok Build to create Microsoft To Do follow-ups or usable legacy Apple CalDAV 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.
