Custom MCP
server.

Open Rally → Settings → Connections → Custom MCP server, then choose Connect for me for a connection only you can use, or Connect workspace to share one with everybody in the workspace. A workspace connection requires a Rally workspace administrator.

Give the connection a name, paste the server’s HTTPS endpoint, and choose how Rally should authenticate:

1. 1

   Sign in through the server. Rally registers itself with the server and sends you to its own authorization page. On a workspace connection, the one account you sign in with is the account every member reaches the server as.

2. 2

   Send request headers you provide. Rally stores the header names and values encrypted, sends them with every request, and never shows or returns them again. Change one by adding the server again and removing the old connection.

Either way, Rally checks that the server answers and offers a tool this connection may actually use before it reports success, so a mistyped address, a wrong header, or a read-only setting the server has nothing to satisfy is reported immediately rather than days later inside a task.

A workspace connection carries a tool policy, on Settings → MCP tools: All tools, or Read-only tools, which exposes only the tools the server itself marks as read-only. That marking is the server’s own claim about its tools, not something Rally can verify, so it narrows what is offered rather than relaxing anything: every tool call still asks for confirmation before it runs.

A personal connection has no such setting. It acts with your own identity on that server and is available to nobody else, so it offers exactly what you can already do there.

The same screen lists what the server currently advertises, with the tools the policy is holding back still shown and marked, so you can see what changing it would allow.

1. 1

   Open Settings → MCP tools. Rally reads the catalog live each time that screen opens, so it reports what the server is answering right now.

2. 2

   For a server you signed in to, choose Authorize again. Access can be withdrawn on the server’s side without Rally being told.

3. 3

   For a server authenticated with headers, add it again with the current values and remove the old connection.