---
name: pear-mcp
description: Configure and use Pear MCP, a hosted remote MCP endpoint for user-authorized productivity workflows. Use when connecting a supported AI client to Pear or choosing the correct authentication path.
---

# Pear MCP

Use this skill when a user wants to connect a supported AI client to Pear's hosted MCP server or needs the canonical endpoint and authentication choices.

## Endpoint

- Remote MCP URL: https://pearmcp.com/api/mcp
- Transport: Streamable HTTP
- Setup guides: https://pearmcp.com/docs
- OAuth discovery: https://pearmcp.com/.well-known/oauth-authorization-server
- Protected-resource metadata: https://pearmcp.com/.well-known/oauth-protected-resource

## Authenticate

Prefer the setup guide for the user's client. Pear supports OAuth Authorization Code with PKCE for compatible, registered public clients and Client ID Metadata Documents. Pear does not provide open Dynamic Client Registration.

For clients using an API key, the user must sign in to Pear and obtain the key from Settings. Send it only as an Authorization bearer token. Never print, log, or place a Pear API key in shared configuration.

## Operate safely

- Ask the user to connect the provider account they intend to use.
- Request only the scopes the workflow needs.
- Treat create, update, delete, send, and move operations as user-visible writes.
- Use Pear's read-only discovery and planning tools before performing writes.
- Do not claim a client integration is verified merely because it accepts an MCP URL.