Connectors: give agents access to MCP tools

Connectors bring tools from MCP servers into your agent conversations. Manage them in Settings → Connectors on the machine that will run the agent. An adapter connects atrium to an AI tool such as Claude Code or Codex; a connector gives that agent additional tools and services.

Add a connector

Open Settings → Connectors to search connected services, curated presets, and the MCP Registry. You can also paste a connector description or configuration into the add flow. Review the publisher, source, and command or server address before adding it.

Local connectors can run from npm or Python packages, Docker images, or an existing command. Remote connectors connect to a server URL. atrium tests the connection and reports progress and failures on the connector's row; adding an entry is not the same as successfully connecting it.

Some connectors need credentials. Enter them in the requested secret fields, or use Sign in to complete browser authentication. A sign-in request can also appear in the chat whose tool call needs it.

Choose which tools a session gets

The composer's Connectors control shows the session's connectors and tools. Where the running adapter supports changing them, you can turn off a connector or an individual tool for that conversation. Controls that cannot affect the current engine are unavailable.

A connector's default determines whether new sessions receive it. A launch profile can override that choice for each connector: on, off, or the default. Changing a default does not promise to reconfigure an already-running session; check its composer control to see its current tools.

Connector configuration belongs to its machine. For a remote project, configure the connector on the location running the agent; credentials on your desktop do not automatically become credentials on every server.

Requests and forms

A tool can ask for information through an in-chat form. Answer or cancel it from its card. Some configuration changes require a person to confirm them; these appear as requests in chat and in Settings. An agent asking for a change has not already been granted it.

Use the connector's status and tool list to diagnose a failed connection. If credentials are missing or a sign-in has expired, complete the requested credential or sign-in step and test again.

From the CLI

atrium connector list
atrium connector test <id>
atrium connector set-default <id> on
atrium connector set-default <id> off
atrium connector requests

The CLI also supports adding local connectors and removing connectors. See CLI → connector for flags and how to provide secrets without putting them in command arguments.