Connect external tools to Uno

Workspace MCP connections let Uno use tools from your issue tracker, documentation system, or other services. This is separate from connecting an external coding agent to Uno.

Add a serverCopy Anchor Link

1. Open Workspace settings → MCP Servers as an owner or admin.
2. Choose a name and the server's exact public HTTPS Streamable HTTP endpoint.
3. Select no authentication, or configure one authentication header.
4. Test the connection and enable it.
5. Start a new session to include the server.

For bearer authentication, use Authorization as the header name and the complete Bearer <token> value as its secret. Use the provider's documented header for an API key. Keep credentials out of the URL.

Import configurationCopy Anchor Link

You can import one server at a time:

{
  "mcpServers": {
    "issue-tracker": {
      "url": "https://mcp.example.com/mcp",
      "headers": { "Authorization": "Bearer replace-me" }
    }
  }
}

Import fills the form. Review it, test, and save to enable the connection.

Supported connectionsCopy Anchor Link

Tool access can let the agent change data in the connected service. Use an upstream credential with the permissions your task requires; there are no per-tool allowlists or approval policies in this connection flow.

Session behaviorCopy Anchor Link

A new session captures its enabled servers. Adding a server later does not add it to an existing session. A disabled or deleted server cannot be used by a bound session, and credential changes are checked before later work.

Every bound server must connect and list its tools before an engineering turn starts. One unavailable server can block that turn. Test the server in settings, check its endpoint and credential, then retry after fixing the connection.

An empty MCP resource list does not mean the tools are missing: these connections expose tools. Non-engineering agent roles do not receive workspace MCP tools.