Built-in connectors
Email by IMAP and SMTP, with Gmail and Outlook through their own sign-in (OAuth); calendars; Slack; HubSpot; Google Drive; OneDrive; Microsoft Teams.
During the beta, some of these connectors have not been tried on real customer accounts yet. Tell us if one doesn’t behave as expected.
MCP servers
MCP (Model Context Protocol) is an open standard that lets an AI assistant use tools provided by another service. On Pichu’s Connectors page, you can add a remote MCP server from the catalog (Zapier, GitHub, Stripe, Linear, Airtable, monday.com, Brevo) with its token, connect Notion or Jira and Confluence with a one-click authorization, or add any MCP server by its HTTPS address.
With one-click authorization, Pichu registers with the publisher using the MCP authorization flow (OAuth with PKCE). The tokens stay encrypted on the platform; the Bot’s computer goes through a relay that attaches an up-to-date token to each call.
Sites without a connector
When a service has no connector, your Bot uses its own browser on its computer. You sign in once, or let the Bot use a password from the vault, and the session stays open for next time.
Shared by your Bots
Connectors belong to your computer: all of your Bots can use them, within each Bot’s approval settings.