Skip to main content

Integrations

Integrations are the third-party services AI Expedite talks to on your behalf — your code host, your communication channels, your analytics, your ad platforms, your cloud, your social accounts, and your custom tool servers. The actual configuration always happens in Account → Settings → Integrations (or the cog icon on the relevant pillar page); this section is the orientation map.

📷 Screenshot: Settings → Integrations tab listing every connected service.

How integrations connect​

Every integration uses one of three handshake patterns:

  • OAuth — the standard browser-redirect flow. You click connect, the third party asks you to confirm, AI Expedite stores a refresh token. Most integrations live here.
  • App install — for GitHub, where you install the AI Expedite GitHub App into the org or repos you want exposed and the install is scoped per-repo.
  • Manual config — for MCP servers, where you supply a command (stdio) or URL (sse) plus credentials.

Tokens are stored encrypted, scoped per workspace, and revocable from the same place you set them. Removing an integration stops AI Expedite from reading or writing through it; existing data the platform pulled before the disconnect stays in the workspace.

Categories​

Each sub-page below covers the integrations in one category — what each one unlocks, where you connect it, and what surface in AI Expedite it shows up on.

Tool servers (MCP) are documented under the agent that calls them — see Agents → MCP.

Reconnecting and scope changes​

When an integration's token is revoked or its scopes change (someone in your org rotates a credential, or the third party deprecates a permission), the affected pages surface a Reconnect action — usually inline on the page that uses the integration most heavily, plus an entry in the integration's row on Settings → Integrations.

Reconnecting walks the OAuth flow again with the new scopes; the workspace stays functional during the disconnected window for any feature that doesn't require the broken integration.

Adding a new integration​

If you want to talk to a service AI Expedite doesn't speak natively, the escape hatch is Custom Actions on Settings → Custom Actions: define an HTTP / DB / script action, store its secrets, and call it from any agent. Combined with MCP servers, that covers most "we use this internal tool" cases without needing a first-class integration.