Connectors

A connector gives your agents access to an outside service, such as Slack, through your own account. You connect it once, and every session in your World can use its tools. Your sign-in stays on your machine.

How it works

A connector is a package that declares the tools it offers and the hosts it may reach. When you connect it, you sign in to the service, and the credential is kept on the machine that connected it. It never goes into a document, a release or a session's log, and no package can read it.

The connector's code runs in its own process and can reach only the hosts it declared. Your token is added to each request on the way out, so the connector's code never sees it either.

Once connected, its tools are available to every session in the World, alongside Mod's own tools. A connector that is installed but not yet connected still shows its tools, and they tell the agent to ask you to connect it first.

Connectors are one of two ways an agent reaches an outside service. The other is a grant: when an agent in a VM needs to call an API with your key, it asks, you put the key in your Mac's Keychain, and the Mac adds it on the way out to that one host. See authentication.

Using it as you build

Connect a service from the Mod app. After that, agents call its tools like any other:

slack_list_channels
slack_read_channel   { "channel": "#launch" }
slack_send_message   { "channel": "#launch", "text": "Reset screen v3 is in review." }

To build your own connector, declare its tools and the hosts it reaches in its package, the same way an app declares its package tools (see tools and packages).

Limits

• Connectors call outside services over their APIs. A connector built from a remote MCP server, or from a command-line tool that holds its own sign-in, is not built yet. soon
• A connector's sign-in is kept on the machine that connected it, in a file readable only by you, so each machine connects once.