What Are Connections?
Connections are MCP (Model Context Protocol) servers that extend what your agents can do. Instead of being limited to built-in tools, connections let agents reach into external systems - your company wiki, project tracker, code repositories, communication platforms, and more.
Confluence
Search and read your company's knowledge base directly from an agent conversation.
GitHub
Browse repositories, read issues, and review pull requests without leaving Rush.
Jira
Look up tickets, check sprint status, and update issues through natural language.
Slack
Search message history and channel archives to find context fast.
Any tool that speaks MCP can become a connection. The ecosystem is growing fast - hundreds of servers are already available in the public registry.
Adding Connections
There are two ways to add a connection in Rush:
Browse Registry
Search the MCP server registry. Find a server, click to add. One step.
Custom
Pick a runner (npx, uvx, bunx, or docker), enter the package name, and save. For servers not yet in the registry.
Open Settings > Integrations, scroll to Connections, and click "Add Connection" to get started.
Security
Connections run as local processes on your machine. To keep things safe, Rush only allows sandboxed package runners - not arbitrary shell commands.
npx, uvx, bunx, docker
bash, sh, node, python, or any other direct command
Package runners download and execute published packages from npm, PyPI, or container registries. This means every server you add is a versioned, published package - not an arbitrary script.
Environment variables you configure for a connection stay local to that process and are never sent to Rush servers.
Per-Agent Access
By default, every connection is available to all your agents. If you want to restrict access - for example, giving only your research agent access to Confluence - you can toggle connections on or off per agent.
Open an agent's settings and scroll to the Connections section to configure which connections it can use.