Apps and connectors

The Apps catalog

The catalog at /apps groups apps by category (development, productivity, communication, data and browsing) with a search box. Apps that connect today with one click:

PostgreSQL, MySQL, MongoDB, Fetch and Puppeteer have no vendor-hosted endpoint; their cards offer Connect your own server. You run the vendor’s (or the reference) MCP server, expose it over HTTPS and paste its URL into a dialog that is pre-filled with the app and explains how to host it. The connection keeps the app’s icon, category, approvals and organization policy, exactly like a hosted app. Microsoft Teams alone is still marked Not available yet: Microsoft hosts a Teams server only inside its Agent 365 preview. The Microsoft business apps are a separate collection, described below.

Connect an app

1. Step 101

   Choose Connect on the card

   Akili resolves the vendor’s MCP endpoint and authorization server from the catalog. You never type a URL or a client ID for a catalog app.
2. Step 202

   Sign in with the service

   A centered consent window opens; on a screen narrower than 768 pixels Akili redirects the whole page instead. Approve the scopes the vendor shows, and the window closes itself.
3. Step 303

   Review the tools

   The connection sheet lists the tools the server exposes and marks which are read-only and which can change or delete data, so you know what will ask for approval.

Your token is stored encrypted and belongs to you alone: a colleague who uses the same app signs in separately, and an agent that uses the app on your behalf uses your token, not the agent owner’s.

Add a custom MCP server

Choose Add custom server on the Apps page. The dialog asks for a name and the server URL, then probes the server. If the probe reports that a key is needed, an API key field appears and the key is sent as a Bearer token on every call. If the server advertises OAuth, Akili uses its registered client identity; the Advanced section accepts a client ID and secret for servers that require a pre-registered client. Custom servers speak Streamable HTTP. Connect your own server on a catalog card opens the same dialog pre-filled with that app, with a short hosting note and a link to the vendor’s server guide; the organization’s custom-server rules (allow custom servers, host allow-list) apply to it as well as the app’s own approval.

Approve tool calls

Each server has an approval policy: writes (the default: tools that create, change or delete data ask first; read-only tools run), all (every call asks) or none. Catalog apps use the default; the Microsoft connection sheet lets you pick the policy per server. A tool that does not declare whether it is read-only is treated as a write. When a call needs approval, a card appears inline in the chat with Approve, Approve for this chat and Deny. “For this chat” remembers the decision for that tool in that chat only, until you reload.

The connection indicator in chat

The plug icon in the composer carries a count of connected servers and opens a menu with one row per server.

Give an agent a connector

In the agent builder, the connectors section lists the servers you have enabled with a checkbox per server. An OAuth server is marked per user: each person who talks to the agent signs in with their own account the first time. An API-key server offers Run for everyone, which lets every user of the agent call it with your key. On Team, Business and Enterprise plans an agent can also hold its own credential, independent of any person, through the credential form in the builder. See Knowledge and connectors for agents.

Organization connector policy

Owners manage the policy in Organization settings under connectors: switch connectors on or off, choose Any or Approved only, approve or block individual apps, allow custom servers only on listed hosts, require MFA before connecting, and answer members’ pending requests. Members see the outcome on the Apps page.

Connected accounts

Open Settings and choose Connections. This tab is separate from the Apps catalog: it holds the accounts Akili itself uses to read and write your files and messages.

Google Workspace

Two grants exist. The share grant only lets Akili place files it creates in your Drive (for sharing a Library file). The workspace-tools grant adds Gmail reading and sending, Calendar, Docs, Sheets, read-only Drive and Forms, which the Google actions in flows and agents use. Disconnect revokes the token.

Microsoft OneDrive and SharePoint

Connecting Microsoft grants file read and write plus your profile, which the Library and project folders use. A SharePoint grant adds site reading for connected project folders, and a Dataverse grant lets Akili discover your Dataverse environments for the Microsoft business apps. The tab offers Reconnect and Disconnect with a confirmation.

Slack and Teams channels

The Slack and Teams entries on the same tab are agent channels: they route conversations from a Slack workspace or a Teams tenant to one of your agents. They do not give chat tools in Slack or Teams: for Slack chat tools connect the Slack app in the catalog once an administrator has registered Akili with Slack, and Teams is still marked Not available yet in the catalog.

Microsoft business apps

When an operator enables the Microsoft collection, the Apps page adds Dataverse, Dynamics 365 Sales, Dynamics 365 Customer Service, Dynamics 365 Finance and Operations (preview) and Partner Center. They sign in with your Microsoft Entra account and build the endpoint from your organization URL or the environment you pick, so connect Microsoft under Connections first; otherwise the sheet reports that Microsoft is not connected.

• Plan gating. Dataverse is included on Business and Enterprise; Dynamics 365 and Partner Center are Enterprise only. Other plans see the card and a message that the connector is not on their plan.
• Copilot credits. The connection sheet warns that Microsoft may bill Copilot credits for tool calls. That billing is Microsoft’s, on your tenant, not Akili credits.
• Partner Center is built in. It uses its own Entra sign-in rather than an MCP endpoint.

Good to know

• One-click is the default. An operator can turn it off, in which case the older connect dialog asks for the auth method, client ID and secret by hand.
• Retries are bounded. When a server answers 429 or 503, Akili honors the Retry-After header up to twice, within a few seconds, and then reports the failure in the chat instead of looping.
• Sign-in identities live elsewhere. Google, GitHub, Microsoft and Apple as ways to sign in to Akili are under Connected accounts in Settings; see Security and account.
• Flows can call the same servers. An MCP call node in a flow uses the connections you made here.