Install one
- From the agent panel
- Ask the agent
- From the API
Open the Connectors tab, search the library, and click the connector. Rerun tells you what it needs before you commit.
How a connector authenticates
A service can offer several ways to connect, and you pick one at install time.Statuses
Every connector on an agent shows one of three states:active
Connected. Its tools are available to the agent.
needs_auth
Waiting for you to sign in.
needs_config
Waiting for a credential, or for you to pick between several ways to connect.
needs_auth or needs_config will tell you so rather than silently failing.
Where credentials live
Credentials go to your Box and stay there. Rerun’s database keeps only a reference to the variable name, never the value. That holds everywhere:- The API accepts no secret at all.
- When an agent needs a key, it opens a masked form. The value never enters the conversation, and the agent only learns which variable name was filled.
- Capturing an agent into a template ships the variable names, never the values.
Missing a connector
Two ways forward. Ask for it. The Connectors tab has a request form. Requests go to the Rerun team and the library grows from them. Add the MCP server yourself. Switch on expert mode, open the MCP tab, and register any Model Context Protocol server: HTTP, SSE or a local command, with its own headers, OAuth or environment variables. Anything with an MCP server works with Rerun today, connector or not. Reference a stored secret in an MCP config with${VARIABLE_NAME}. It resolves on your Box at run time.