Connectors

A connector wires a third-party service into Wicket’s proxy and policy engine. Each connector provides:

• An MCP tool namespace (e.g. GitHubMCP, SlackMCP)
• A set of tools grouped into read / write / destructive tiers
• An OAuth flow for per-member credential storage

Supported connectors

16 connectors: GitHub, Slack, Linear, Notion, Stripe, Supabase, Vercel, HubSpot, Airtable, Atlassian, Cloudflare, Google, Hugging Face, PlanetScale, Prowler, and Sentry.

The Connectors catalog has the full matrix — tool counts by tier, namespaces, OAuth setup mode, and which connectors support entity harvesting and webhooks.

Enabling connectors

Connectors are enabled per agent:

1. The owner toggles the connector on in the agent’s settings.
2. For most connectors, the owner enters their OAuth app’s client ID and secret once (Sentry, Cloudflare, and Google are managed by Wicket and skip this step).
3. Each member completes the OAuth flow for the connector before generating their member key.

See Connect a connector for the full walkthrough.