What is Instinct?
Instinct describes a personal assistant that works across your apps and devices. You reach it by text or phone, and it can use a phone and computer to carry out tasks.
This guide covers the personal assistant at instinct.com. Its ability to use connected apps does not establish that it can connect to Pear through MCP.
Can Instinct connect to Pear?
As of 30 September 2026, we have not found official public instructions for adding a custom MCP server to Instinct. Pear has not verified an authenticated Instinct connection, tool discovery, or provider read.
This is a connection requirements guide. We cannot yet give you a confirmed Instinct settings path or authentication procedure. If your Instinct account offers a custom connector, contact Pear support with the official instructions and field names, without credentials.
What a Pear connection would need
Pear provides a hosted MCP endpoint for connected Apple iCloud and Microsoft 365 accounts. A client must support Streamable HTTP and an authentication method Pear accepts.
https://pearmcp.com/api/mcpFor an API-key connection, the client must send your personal Pear API key in the Authorization: Bearer header. This describes Pear's requirements, not a confirmed Instinct feature. Only enter a key in a documented private credential field. Do not paste it into a conversation or share an Apple app-specific password with the assistant.
This guide does not provide an Instinct OAuth Client ID. Do not reuse another client's ID or assume that an OAuth prompt establishes compatibility. See the custom MCP requirements for the full checklist.
How to confirm a connection
Once an official configuration path is available, a successful check needs to authenticate, list Pear's available tools, and complete a read such as pear_provider_status. Follow with a read of a known calendar event from the intended account.
Saving a URL is not proof of access. Reconnection, permissions and revocation also need checking. Sending mail or changing events requires separate verification and approval of the exact action.
Use a documented setup path today
For a messaging assistant with published custom MCP instructions, read the Poke guide or Folk guide. You can also browse all Pear client guides. Each guide states its own authentication method and limits.
Pear supports Apple iCloud and Microsoft 365. Those provider connections do not by themselves connect Instinct.
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.
Review Pear's data handling and the assistant's own policies before connecting an account.
Sources and compatibility status
Public sources checked on 30 September 2026. Instinct's homepage, linked sign-in page and public sitemap did not provide custom MCP setup instructions. This does not rule out features available inside individual accounts.
