Twelve providers, and this is all of them. If a service you need is not listed here, the only way to reach it is as a custom MCP server — there is no other extension point, and nothing on this page is a subset of a longer list somewhere else. The same data is available live, and it is the authoritative version:
Each entry carries provider, name, description, category, auth_type, enabled, capabilities and setup_fields. setup_fields is the exact list of what a provider needs — read it rather than guessing. enabled is false when a provider’s OAuth application is not configured in the region you are talking to. A disabled provider cannot be connected; every other field still reads normally.

​
Reading the columns

Connects with is auth_type — oauth means a browser redirect started from the dashboard, manual means a value you paste, through the dashboard or the API. Default namespace is the prefix this integration’s tools are presented to the model under, as <namespace>_<tool>. It is the provider key everywhere except a custom server, which gets no prefix. You can change it; see namespacing. Tools come from says whether we connect to a server the vendor hosts, run the tools ourselves against the vendor’s API, or neither — a channel provider lends an agent no tools at all. Exa’s server answers web-search calls; Tavily’s answers web search and page extraction.
Exa publishes a keyless tier, and we require a key anyway. That tier is a shared anonymous pool, so its rate limit is exhausted by strangers: an agent built on it works in testing and then fails in the middle of a real call with Exa’s free-tier rate-limit error. Create a key at dashboard.exa.ai/api-keys. Tavily’s MCP server has no keyless mode at all — it answers an unauthenticated request with a 401.

​
Scheduling

Google Calendar is the one native provider: nine tools we implement against the Calendar REST API rather than proxying a server Google hosts. From your side it is identical to any other integration — same approval, same namespacing, same listing endpoint. See Google Calendar.

​
Project management

​
CRM

A HubSpot connection is identified by its portal, so one workspace can hold one integration per portal.

​
Enrichment

Finds a person’s work email, phone number and profile from a name, a company or a domain.
Searching is free; every lookup or export spends credits from your RocketReach plan, and nothing on our side caps that. An agent task run once per row of a five-thousand-row list spends five thousand credits. Cap it in RocketReach, or size the batch to the plan.

​
Email

One Resend integration serves two unrelated purposes: an agent can call Resend’s MCP tools, and email batches send through the same key. Neither knows about the other. The key is what scopes the tools to your account, so there is no keyless mode.

​
Messaging

Telegram lends an agent no tools and cannot be attached under mcps. It routes private Telegram bot messages to a published text agent through a trigger. The end-to-end walkthrough is Telegram.

​
Developer tools

Every tool the server exposes is available to attached agents. A custom server gets no namespace by default — there is no provider name to derive one from — so its tool names reach the model exactly as the server writes them. See custom MCP servers.

​
Setup fields

What each provider asks for on create. OAuth providers have no setup fields: the redirect supplies everything. A field of type secret takes either a plaintext value — which the platform stores as a workspace secret and replaces with a reference — or an existing {{secrets.NAME}} reference. headers is the exception: header values are stored exactly as you send them and are never turned into secrets for you. Reads never return a secret value. credentials_ref and any secret-bearing webhook_config field come back as {{secrets.NAME}}.