Connectors

Connectors are the primary CoreSpeed v0 product surface. They let an agent act through software accounts already owned by a member or organization. CoreSpeed stores and refreshes the OAuth credential; the agent receives MCP tools, not the provider token.

Inventory

The registry currently contains 37 connectors. 29 are visible through the authenticated index; 8 remain hidden while upstream OAuth approval or launch validation is incomplete. Hidden implementations keep their code and stored credentials, but they do not appear in GET /connectors or tools/list.

Do not hard-code the count or connector list into a client. Read:

curl https://api.corespeed.io/connectors \
  -H "Authorization: Bearer $CORESPEED_API_KEY"

Connection lifecycle

1. The user opens Dashboard → Connectors.
2. They authorize a private member account or a shared organization account.
3. CoreSpeed stores the grant inside that organization boundary and refreshes it when the provider permits.
4. The connector's namespaced tools appear in tools/list on the existing /mcp endpoint.
5. Any MCP agent using the same CoreSpeed identity can use the connection; no provider token is copied into the client.

Account context

One connector can expose multiple account aliases. The alias selects a stable account without putting a provider account ID or access token into prompts. Private accounts belong to a member; shared accounts are available inside the organization according to its access rules.

Use GET /connectors for the index and account state. Each account includes its scope, health status, and whether the current caller can_remove it.

Reauthorization

needs_reauth is a recoverable state. The connector remains known, but its upstream grant can no longer be used. Send the user to the dashboard to reauthorize the account; do not rotate the CoreSpeed key or delete client configuration.

Connectors are their own switch

Built-in capabilities have organization/member visibility controls. Connectors do not: connecting and disconnecting the OAuth account is the connector's enable/disable lifecycle.