Connectors catalog
Wicket supports 16 connectors. Each one proxies a hosted MCP server, carries a tool catalog grouped into read / write / destructive tiers, and authenticates members via OAuth.
The catalog
| Connector | Namespace | Tools (read / write / destructive) | OAuth setup | Extras |
|---|---|---|---|---|
| GitHub | GitHubMCP | 43 (26 / 13 / 4) | Your OAuth app or GitHub App | Entity harvesting, webhooks, GitHub App mode, resource conditions |
| Linear | LinearMCP | 35 (24 / 9 / 2) | Your OAuth app | Entity harvesting, webhooks, resource conditions |
| Cloudflare | CloudflareMCP | 25 (14 / 6 / 5) | Managed by Wicket | Entity harvesting |
| Sentry | SentryMCP | 22 (17 / 5 / 0) | Managed by Wicket | Entity harvesting, webhooks |
| Atlassian | AtlassianMCP | 19 (13 / 6 / 0) | Your OAuth app | Entity harvesting, webhooks, Jira + Confluence scopes |
| Stripe | StripeMCP | 18 (11 / 5 / 2) | Your OAuth app | Entity harvesting, webhooks |
| Supabase | SupabaseMCP | 16 (9 / 4 / 3) | Your OAuth app | Entity harvesting |
| PlanetScale | PlanetScaleMCP | 16 (15 / 0 / 1) | Your OAuth app | Entity harvesting |
| Slack | SlackMCP | 15 (8 / 6 / 1) | Your OAuth app | Entity harvesting, webhooks, channel restrictions |
| Airtable | AirtableMCP | 15 (5 / 8 / 2) | Your OAuth app | Entity harvesting, webhooks |
| Notion | NotionMCP | 14 (5 / 8 / 1) | Your OAuth app | Entity harvesting, webhooks |
GoogleMCP | 14 (8 / 6 / 0) | Managed by Wicket | Entity harvesting | |
| HubSpot | HubSpotMCP | 11 (11 / 0 / 0) | Your OAuth app | Entity harvesting, webhooks, read-only catalog |
| Vercel | VercelMCP | 9 (9 / 0 / 0) | Your OAuth app | Entity harvesting, webhooks, resource conditions |
| Hugging Face | HuggingFaceMCP | 5 (5 / 0 / 0) | Your OAuth app | Entity harvesting, webhooks |
| Prowler | ProwlerMCP | 4 (3 / 1 / 0) | Your OAuth app |
281 tools across the catalog. Exact tool names and tiers are listed in the dashboard’s policy builder (grouped by tier) and via GET /api/tools/catalog.
OAuth setup column, explained
- Managed by Wicket — works out of the box. Members click Connect and complete the provider’s OAuth flow; no configuration needed.
- Your OAuth app — the agent owner registers an OAuth app with the provider once and enters its client ID and secret in the agent’s connector settings. Members then connect with one click. See Connect a connector for the walkthrough and the redirect URL to use.
Tool tiers
Every tool carries a tier used for bulk policy authoring:
| Tier | Meaning | Examples |
|---|---|---|
| read | No side effects | get_file_contents, list_issues, search_code |
| write | Creates or modifies content | create_pull_request, slack_send_message, save_issue |
| destructive | Deletes or irreversibly changes state | delete_file, merge_pull_request, slack_delete_message |
The policy builder lets you select an entire tier with one click — “forbid all destructive GitHub tools” is a single checkbox.
Calling tools
All connectors are served from the single MCP endpoint with service-prefixed tool names:
github__get_file_contentslinear__save_issueslack__slack_send_messagetools/list on /mcp returns only the tools of connectors that are enabled on the agent and connected by you.
Example — one entry from a tools/list response. Each tool carries metadata identifying its service:
{ "name": "github__get_file_contents", "description": "Get the contents of a file or directory from a GitHub repository", "inputSchema": { "type": "object", "properties": { "owner": {}, "repo": {}, "path": {} } }, "_meta": { "zstrike_service": "github", "zstrike_service_label": "GitHub" }}When calling the tool, keep the prefixed name; Wicket strips the prefix before forwarding upstream.
Related
- Connect a connector — enable, configure OAuth, connect members
- Entity harvesting and freshness — how pickers and resource conditions get their data
- GitHub App mode — installation-based GitHub access