Connect Gemini CLI to Pear MCP

1. Create your Pear API key

Sign in to Pear, connect your provider account, and copy a Pear API key. Gemini CLI supports OAuth discovery for compatible remote MCP servers, but the simplest static setup is a bearer token in your local user settings.

2. Add Pear to Gemini CLI settings

Gemini CLI documents MCP servers through amcpServersobject in settings. For Pear, use a Streamable HTTP entry with a bearer token.

{
  "mcpServers": {
    "pear": {
      "httpUrl": "https://pearmcp.com/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_PEAR_API_KEY"
      }
    }
  }
}

Keep this in your user-level Gemini CLI settings. Do not commit a settings file that contains a real Pear API key.

3. Check the MCP registry

• Use Gemini CLI's MCP inspection command to confirm Pear is connected.
• Check that calendar, task/reminder, contact, mail, and scheduling tools appear.
• Try a read-only prompt before asking Gemini CLI to create or update data.
• Keep API keys outside project files and shell history where possible.