Planned Connectors
These connectors exist as planned registry entries only. Treat them as not implemented until a provider adds executable runtime support, real-provider validation, customer CMS seed policy, and user-facing setup coverage.
Planned / Not Yet Implemented
Section titled “Planned / Not Yet Implemented”| Connector | Key | Provider family | Current note |
|---|---|---|---|
| Google Chat | google-chat |
Planned spaces and messages connector. | |
| Salesforce Accounts | salesforce-accounts |
Salesforce | Planned account records connector. |
| Salesforce Cases | salesforce-cases |
Salesforce | Planned case records connector. |
| Salesforce Opportunities | salesforce-opportunities |
Salesforce | Planned opportunities connector. |
| HubSpot Contacts | hubspot-contacts |
HubSpot | Planned contact records connector. |
| HubSpot Companies | hubspot-companies |
HubSpot | Planned company records connector. |
What Is Missing For Each
Section titled “What Is Missing For Each”- Provider scopes and runtime-required scopes must be specified.
- API runtime extension or provider manifest must define live, indexed, resource-list, config, and smoke behavior.
- Customer CMS seed/catalog behavior must be verified.
- Real-provider smoke coverage must be added when practical.
- Support-dev provider page should be added only when enough operator setup detail exists.
- Provider PAT setup means a dedicated service/bot account credential stored through the shared deployment API-key profile. Do not model employee personal PATs as a web-user connector setup path unless a separate per-user PAT strategy is accepted later.
GitHub Repositories, GitHub Issues, and GitHub Pull Requests are implemented live-only connectors. See GitHub Connector for their current runtime shape and unsupported GitHub products.
Screenshot Placeholder
Planned connector catalog state
Replace later with a screenshot showing how planned or unavailable connectors are communicated in the product UI.
Related Planned Feature
Section titled “Related Planned Feature”Custom MCP connectors are a separate future feature. See Custom MCP Connectors for that direction.
Canonical Sources
Section titled “Canonical Sources”packages/domain/src/connectors/connectorRegistry.tsapps/api/src/connectors/providerManifests.tsdocs/features/connectors/spec.mddocs/features/connectors/spec-mcp-extensions.md