DocsConfigure
MCP servers
Connect GitHub, Atlassian or any Model Context Protocol server so agents and canvas tasks can use external tools.
The Model Context Protocol (MCP) lets agents use tools and data that live outside your repository: documentation, issue trackers, internal services. Open MCP Integration in the left rail to manage servers.
The page has three tabs:
- GitHub: guided setup for the GitHub MCP server, using NPX, Docker, a remote HTTP endpoint, or a custom command.
- Atlassian: guided setup for Jira and Confluence, using UVX, Docker, NPX or a remote HTTP endpoint.
- Generic / Custom Servers: add any other MCP server yourself.
The guided tabs pre-fill sensible defaults and can test the connection live, so start there for GitHub and Atlassian.
Add a custom server
In the Generic / Custom Servers tab, add a server and fill in the form.
Identity
| Field | Rules |
|---|---|
| Name | Required. Lowercase letters, numbers, - and _ only, and unique among your servers. |
| Display name and Description | Optional, for your own reference. |
| Enabled | Turn a server off without deleting it. |
Transport
Choose how Rusty connects:
| Transport | Use for | You provide |
|---|---|---|
| HTTP (Streamable) | Remote servers over HTTP. The default. | A valid http(s) URL. |
| SSE (Server-Sent Events) | Remote servers using SSE. | A valid http(s) URL. |
| WebSocket | Remote servers over WebSocket. | A valid ws(s) URL. |
| Stdio (local process) | A server Rusty starts on your machine. | A command, plus optional arguments and environment variables. |
Authentication
| Method | Fields |
|---|---|
| None | |
| API Key (header) | The header name and the key value. |
| Bearer Token | The token. |
| OAuth 2.0 | Client ID, client secret, token URL and scopes, with a grant type of Client Credentials or Authorization Code. |
Secret fields are password inputs and are never shown again in plain text after you enter them. The API key value, bearer token and OAuth client secret accept ${ENV_VAR} references, so the real secret can come from the environment instead of being typed into the form:
${GITHUB_TOKEN}Advanced
| Setting | Default |
|---|---|
| Timeout | 30000 ms |
| Max retries | 3 (allowed range 0 to 10) |
| Retry delay | 1000 ms |
Test the connection
Use Test Connection in the form. What it can check depends on the transport:
- HTTP and SSE: makes a request to the URL with a timeout.
- WebSocket: checks that the URL is valid, because browsers cannot probe
ws://endpoints. - Stdio: a simulated check, because starting the real process happens in the backend.
The result appears inline in the form.
Use MCP servers
Once configured, MCP servers are available to:
- Skills. A skill can include MCP access. See Skills.
- Canvas tasks. Connect an MCP node to a task when the work depends on information outside the repository. See Rusty Canvas.
Server definitions, including their credentials, are saved in Rusty's encrypted configuration. See Data, storage & privacy.