Skip to main content
An integration is anything outside your project’s code that the agent, or the app it builds, can use: an app such as Gmail or Slack, a service built into every session such as PostgreSQL, or an MCP server that adds tools. The Integrations catalog holds all of them in one place, and anything you connect there works in every session you own. To sign in to an app, see Connect an app. For hosted or local MCP servers, see MCP servers. To call your connections from the code the agent writes, see Use integrations in your app.
The Integrations dialog, with a close button at its top right. Under the title Integrations, the lede reads: Sign in once and build with it across your sessions, apps and agents. Built-in integrations land in the agent's environment; connectors and MCP servers reach it as tools. Below it are the tabs Connectors (selected), MCPs and Connected, a search box with the placeholder Search — Gmail, Stripe, Notion, maps…, and the dropdowns All auth and All categories. Under them are the sub-tabs Connectors 25 (selected), Built in 6 and Connected 0, with a Refresh button at the right. A three-column grid of cards follows, sorted A to Z: Airtable, arXiv, Browserbase, Cal.com, Cloudflare, E2B, Fireflies, Gmail, Google Calender, Google Docs, Google Drive, Google Sheets, Hacker News, LinkedIn and Mem0, with Netlify, OneDrive and Open Weather Map cut off at the bottom. Each card shows a logo, a blue Verified check, a Connector badge, an API key, OAuth or No auth badge and a one-line description. Cards with API key or No auth show a Connect button; Gmail, the Google apps, LinkedIn and OneDrive, which use OAuth, show Sign in.

The catalog opens on Connectors, where each app offers Sign in or Connect.

​
What counts as an integration?

Each card names its kind with a coloured badge. Built-in services land in the agent’s environment; connectors and MCP servers reach it as tools. Connector and remote MCP sign-ins never enter a session. Sessions and apps hold only a per-session key, never your password or the app’s own token.
If you don’t see an app or MCP server you expected, it isn’t turned on for your Alpha. An admin chooses which apps and hosted MCP servers the catalog offers.

​
Browse the catalog

The catalog opens as a large dialog over whatever you are doing. It has no address of its own, so there is no Integrations page to bookmark. There are three ways in: The dialog has three tabs, and each sub-tab shows a count. Cards are sorted A to Z. Click one to open its detail: what it gives the agent and how to connect it.

​
Read a card

Every card tells you what a thing is, how it signs in and whether it is on.
  1. Logo. A server with no mark of its own shows the MCP glyph.
  2. Verified. Alpha curated it. Servers you add yourself don’t get the check.
  3. Type badge. Connector, Built in, Remote MCP or Local MCP.
  4. Auth badge. OAuth (sign in with the app’s own account), API key (paste a key or credentials) or No auth (one click). Built-ins have none.
  5. Action or status. See the table below.
When a remote server’s sign-in has expired and can’t be refreshed, its detail reads “Sign in again”. Built-in cards show nothing in the corner, because they are always there.

​
Use the built-in services

Connectors → Built in lists the six services every session’s machine already has. The agent switches each one on when your project needs it.
The Integrations dialog on the Connectors tab, with the sub-tabs Connectors 25, Built in 6 (selected) and Connected 0, the All auth and All categories dropdowns and a Refresh button. Six cards sit in a three-column grid, sorted A to Z: Alpha tools, GitHub, Headless browser, Image generation, PostgreSQL and User sign-in. Each card shows its logo, a blue Verified check, a grey Built in badge and a one-line tagline, most of them cut short: Alpha tools' begins Every connected provider and MCP server, callabl, GitHub's Clone repos, push, open pull requests — the GitHu, Headless browser's The agent's own Chromium, for checking its work, PostgreSQL's The session's own database, browsable in the Dat and User sign-in's Google or email accounts for the app's users, host, while Image generation's reads in full Hero images, icons and illustrations from a prompt. No card shows a button or a status pill.

Built in: six services, with no sign-in and no button.

Click a built-in to see what the agent works from: a Built into Alpha box, a What the agent gets list of its variables for those that set any, and a collapsed What the agent will follow section. Expand it to read, word for word, the recipe the agent follows for that service.

​
Where does a connection reach?

A connection belongs to your account, not to one session. Sign in to Gmail once and every session you own can use it. Connections belong to your account alone. Other people’s sessions never get them, even when you share a session with them.

​
When do changes take effect?

Connecting, disconnecting or revoking something updates every running session of yours. If the agent is mid-turn, the change waits for that turn to end, so the new tools arrive with your next message.

​
Check what’s on

The Connected tab lists every connector you signed in to and every MCP server that is on. Built-in services never appear there. Its count matches the badge on the sidebar’s Integrations row. With nothing on, the tab reads “Nothing connected yet — sign in to a connector or install an MCP server.”

​
What if a service isn’t listed?

It still works. Search for it, and when nothing matches the catalog says so: “A service that isn’t here still works as a plain secret — the agent will name the variable.” Ask the agent to use the service. When it needs a key it posts a card in the transcript, such as “The agent needs HARBOR_WEATHER_API_KEY”, with an Add HARBOR_WEATHER_API_KEY button that saves the key as a secret. The agent then reads it as an environment variable. If the service offers an MCP server, you can also add it yourself under MCPs → Add server, as described in MCP servers.
Never paste a key into the composer. Anything typed in the composer lands in the session’s transcript, and Alpha warns you when your message looks like it holds one. Add keys under Secrets or connect the app here.

​
Next steps

Connect an app

Sign in with the popup, connect with a key, test a connection and answer the agent’s Connect card.

MCP servers

Install Context7, sign in to Stripe or Notion, or add a server of your own by URL or command.

Use integrations in your app

Find the session’s key, copy its two .env lines and rotate it if it leaks.

Secrets

For a service with no connector: store its key once and every session gets it.