Connect to Uno MCP

Before you connectCopy Anchor Link

Finish Uno sign-in, access, and onboarding. Make sure you belong to the workspace you want the client to use.

Use a client that supports Streamable HTTP MCP and OAuth. A native client can discover the authorization server from Uno's endpoint.

Claude CodeCopy Anchor Link

Add Uno:

claude mcp add --transport http uno https://api.uno.engineering/mcp

Open /mcp in Claude Code, select Uno, and authenticate. Complete the Uno sign-in flow in the browser, choose a workspace, and review the permissions before approving.

Other clientsCopy Anchor Link

Add a remote HTTP server with the URL https://api.uno.engineering/mcp, then use the client's OAuth sign-in action. For clients that use this JSON format:

{
  "mcpServers": {
    "uno": {
      "type": "http",
      "url": "https://api.uno.engineering/mcp"
    }
  }
}

Use your client's documented settings; this JSON format is not universal. Clients without dynamic OAuth registration require a pre-registered public client with the correct callback URL and PKCE support. Never put a client secret in a desktop configuration.

Verify the connectionCopy Anchor Link

Ask “Use Uno to list my tasks.” Or call uno_get_workspace to confirm the selected workspace and repository IDs.

A task read is a useful first check before starting execution that can consume credits.

Change workspace or disconnectCopy Anchor Link

Open MCP connections in Uno. Revoke the connection, then authenticate again to select another workspace.

Deleting a server from your client only removes its local configuration. Revoke it in Uno to remove server-side access.