Connect Continue to Pear MCP

1. Prepare Pear

Create your Pear account, connect iCloud or Microsoft 365, then copy a Pear API key. Use an environment variable so the key does not live inside your Continue configuration.

2. Add a streamable HTTP server

Continue's MCP docs support standalone files in.continue/mcpServerswithstreamable-http, SSE, and stdio entries. Use the HTTP transport for Pear's hosted endpoint.

name: Pear MCP
version: 0.0.1
schema: v1
mcpServers:
  - name: Pear
    type: streamable-http
    url: https://pearmcp.com/api/mcp
    requestOptions:
      headers:
        Authorization: Bearer YOUR_PEAR_API_KEY

If you manage Continue through Hub configs, use Continue's hosted secrets flow rather than pasting a real Pear key into a shared YAML file.

3. Validate in Continue

• Reload Continue after changing config so the MCP server list refreshes.
• Confirm Pear tools appear before using provider write actions.
• Use a read prompt like checking tomorrow's schedule as the first test.
• Rotate the Pear API key if it is pasted into a shared config by mistake.