Connect MCP tools

Aya, the AI assistant, can use tools from external MCP servers you connect, on top of AY Inbox's built-in ones. Connect your own server or a third-party one, review the tools it offers, and enable it. From then on Aya can call those tools, always asking you first.

Connections live under Settings, Connections and require the Manage settings permission.

Connecting a server

Press Add server and provide:

• Name: how the connection appears, and part of each tool's name in Aya.
• Server URL: an https URL to a streamable-HTTP MCP endpoint. Only public https URLs are allowed; internal or private addresses are rejected.
• Authentication: None, or a Bearer token. A bearer token is stored encrypted with your workspace key and is never shown again or returned by the API.

When you connect, AY Inbox reaches out to the server, runs the MCP handshake, and lists the tools it offers. The connection starts disabled so nothing is exposed to Aya until you have looked at the tools.

Reviewing and enabling

Each connected server shows the tools AY Inbox discovered. Read them, and when you are comfortable, flip the toggle to enable the server. Only enabled servers' tools reach Aya.

If the server could not be reached, the connection shows the error instead of a tool list. Fix the URL or token and press the refresh icon to try discovery again. Refresh also picks up any new tools a server has added.

How Aya uses external tools

External tools behave like AY Inbox's own write actions with one important difference: they are always approval-gated. Aya can never run an external tool automatically, even when a settings manager has chosen "Always allow" for built-in actions. Every external tool call shows you what it will do and waits for your approval.

Each tool appears in Aya namespaced by your connection, so it is always clear which server a tool belongs to.

Removing a connection

Disconnect a server any time from its card. Its tools are removed from Aya immediately, and the stored credentials are deleted.