What is the difference between “not confirmed” and “not supported”?

Not supported means the vendor's own documentation states the capability is unavailable. Not confirmed means the documentation is silent: nobody has published that the capability exists for that specific connection. Connector Scout never converts silence into a negative claim, and never converts it into a positive one either.

Why separate sync from search?

Because they are different data decisions. Search fetches content at the moment you ask. Sync indexes your content ahead of time, which means an index of it exists inside the assistant's platform. Those need different approvals, so they are tracked as separate capabilities.

Are plan availability and regions capabilities?

No. They control who may enable a connection and where it works, not what the connection can do. They are tracked as availability facets and are left empty unless a vendor documents them per connection, so an empty field is never mistaken for a verified answer.

Do vendors call these connectors?

Not consistently. OpenAI documents connectors, apps and the Plugin Directory; Anthropic documents connectors, custom connectors and MCP servers; Google documents Connected Apps and Gemini for Workspace. Connector Scout keeps using “connectors” because that is what people search for, and maps each vendor's own terminology explicitly.

Capabilities

AI connector capabilities, by what is actually documented

Most connector lists tell you a connection exists. This page organises the same dataset by capability — what a connection can retrieve, change or render — and shows how much of each capability is genuinely documented by the vendor rather than assumed.

At a glance

Connector Scout tracks 9 capability axes across 24 documentation-verified connection records on 3 AI platforms. Capability status is read from each record's matrix, never inferred, and availability controls such as plan and region are kept separate so an empty field is never read as a verified answer.

Capability axes: 9
Verified records: 24
Platforms compared: ChatGPT, Claude, Gemini
Availability facets tracked separately: 7
Most recent verification: 2026-08-04

The capability taxonomy

Capabilities describe what a connection does. They are deliberately narrower than “integration”, because vendors document each of these separately and they do not move together.

Search, retrieval and indexing

Search / retrieval: The assistant can query the connected tool and find matching content on demand, at the moment a question is asked.; Records with documented Search / retrieval
Sync / indexing: Content is indexed ahead of time rather than fetched only on demand. This is a governance decision as much as a speed one: an index of your content exists.; Records with documented Sync / indexing
Deep research: The connected tool can be used inside a multi-step research run, not just a single chat turn. Vendors document this separately from ordinary chat access, and it often requires selecting the connector explicitly.; Records with documented Deep research

Read and write actions

Read: Content the user is already permitted to see can be brought into the conversation and reasoned over.; Records with documented Read
Create: New objects can be created in the connected tool — records, drafts, issues, events.; Records with documented Create
Update: Existing objects can be modified in the connected tool.; Records with documented Update
Delete: Objects can be removed. This is the axis vendors document least often, and an unconfirmed delete is not the same thing as a documented refusal to delete.; Records with documented Delete
Send / dispatch: Something leaves the system on the user's behalf, or a side-effecting operation is triggered — sending mail, posting a message, running an action.; Records with documented Send / dispatch

Surfaces inside the assistant

Interactive UI: The connected tool renders its own interface inside the assistant rather than returning text only.; Records with documented Interactive UI

Documented coverage by platform

Counts are over documentation-verified records only. “Not documented” means the record's matrix has no row for that capability at all — a gap in vendor documentation, not a negative finding.

Capability coverage across 24 documentation-verified connection records.
Capability	ChatGPT	Claude	Gemini	Documented as usable
Search / retrieval	8 of 8 records8 supported	10 of 10 records9 supported · 1 limited	5 of 6 records3 supported · 2 limited · 1 not confirmed	23 of 24
Sync / indexing	4 of 8 records2 supported · 2 limited · 2 not confirmed · 2 not documented	2 of 10 records2 limited · 7 not confirmed · 1 not documented	0 of 6 records1 not supported · 3 not confirmed · 2 not documented	6 of 24
Deep research	5 of 8 records4 supported · 1 limited · 3 not documented	0 of 10 records10 not documented	0 of 6 records6 not documented	5 of 24
Read	8 of 8 records8 supported	10 of 10 records10 supported	5 of 6 records4 supported · 1 limited · 1 not confirmed	23 of 24
Create	3 of 8 records2 supported · 1 limited · 5 not confirmed	8 of 10 records5 supported · 3 limited · 1 not supported · 1 not confirmed	1 of 6 records1 supported · 3 not supported · 2 not confirmed	12 of 24
Update	3 of 8 records2 supported · 1 limited · 5 not confirmed	8 of 10 records3 supported · 5 limited · 1 not supported · 1 not documented	1 of 6 records1 supported · 3 not supported · 1 not confirmed · 1 not documented	12 of 24
Delete	0 of 8 records1 not supported · 6 not confirmed · 1 not documented	1 of 10 records1 supported · 1 not supported · 6 not confirmed · 2 not documented	0 of 6 records3 not supported · 2 not confirmed · 1 not documented	1 of 24
Send / dispatch	0 of 8 records1 not confirmed · 7 not documented	0 of 10 records1 not supported · 1 not confirmed · 8 not documented	0 of 6 records1 not confirmed · 5 not documented	0 of 24
Interactive UI	1 of 8 records1 limited · 7 not documented	3 of 10 records2 supported · 1 limited · 7 not documented	0 of 6 records6 not documented	4 of 24

What each status means

The same five values are used on every record page, so a status always means the same thing.

Supported: The vendor documents the capability for this specific connection.
Limited / conditional: Documented, but conditional — an older rollout note, a subset of object types, a plan or app version that not every user has.
Documented as not supported: The vendor's documentation states the capability is not available.
Not confirmed: Documentation is silent. This is not evidence of absence, and Connector Scout will not present it as one.
Not documented in this record: The record has no row for this capability yet, usually because the vendor publishes nothing about it.

Where each capability is documented today

Up to four verified records per capability, taken straight from the dataset.

Update

ChatGPT + Notion (supported)
ChatGPT + HubSpot (supported)
ChatGPT + Slack (limited / conditional)
Claude + Google Drive (limited / conditional)

Delete

Claude + Google Calendar (supported)

Send / dispatch

No verified record documents this capability yet. It stays visible so the gap is explicit rather than hidden.

Interactive UI

ChatGPT + HubSpot (limited / conditional)
Claude + Google Calendar (supported)
Claude + HubSpot (limited / conditional)
Claude + Slack (supported)

What each vendor calls this

People search for “AI connectors”. Vendors use their own names, and the names carry real differences in who operates the connection.

ChatGPT

Vendor terms connectors, apps, plugins (Plugin Directory)

Searched as ChatGPT connectors

OpenAI documents connectors (first-party data connections, some with sync) separately from apps built on the Apps SDK. Both are listed in the Plugin Directory, and plan gating differs between them.

Claude

Vendor terms connectors, custom connectors, MCP servers, integrations

Searched as Claude connectors

Anthropic documents built-in connectors it operates separately from custom connectors, which are remote MCP servers registered by the customer. Operational responsibility differs, so records never present an MCP-backed integration as a first-party feature.

Gemini

Vendor terms Connected Apps, Gemini for Workspace, extensions

Searched as Gemini connectors

Google splits access between administrator-scoped Gemini for Workspace and narrower user-level Connected Apps. A capability documented by Google can still be unavailable to a user whose administrator has not enabled it.

Availability and control facets

These are not capabilities. They decide who may enable a connection and where it works, and they are recorded only where a vendor documents them per connection.

How completely each availability facet is documented across verified records.
Facet	What it decides	Documented
Authentication model	How the connection is authorised: a first-party connector the vendor operates, or a remote MCP server someone else runs.	23 of 24 records
Supported surfaces	Which access modes the record documents — read, write, action — and therefore where the connection can be used.	23 of 24 records
Account requirements	The account or licence a user needs before the connection can be enabled at all.	23 of 24 records
Permissions and scopes	The specific permissions the connection requests. Recorded only where the vendor enumerates them.	0 of 24 records
Admin approval model	Whether an administrator must enable the connection before an individual user can use it.	22 of 24 records
Plan availability	Which paid tiers document the connection. Left empty unless the vendor states it per connection.	0 of 24 records
Regions	Geographic availability. Vendors rarely document this per connection, so it is usually empty.	0 of 24 records

An empty facet is a gap, not a verdict

Plan availability and regions are usually empty because vendors publish them platform-wide rather than per connection. Connector Scout leaves them empty rather than repeating a general statement as if it were connection-specific.

Evidence and freshness

Every capability row on a record page links to the source that documents it.

Capability status is read from the record's structured matrix, and evidence is resolved from the sources that record already cites — first any source attached to that exact capability, then the sources that document the record's capability matrix as a whole. No source is ever attached to a capability it does not support. The most recent verification date in this dataset is 2026-08-04.

Questions about capability data

Looking for a specific assistant instead? ChatGPT connectors · Claude connectors · Gemini connectors