Connect another MCP client

Use a client that supports remote MCP over Streamable HTTP. Rukou's Agents → Connect an app → Another MCP client setup provides the address and a configuration example for the agent you selected.

Configure the connection

Make an API key for that agent. Set these values in the client's private connection settings:

Setting	Value
Transport	Streamable HTTP, sometimes labelled HTTP
Server URL	The complete MCP address copied from the agent
Authentication header	Authorization
Header value	Bearer followed by the agent's API key

For clients that accept the mcpServers format, the configuration has this shape:

{
  "mcpServers": {
    "rukou-research": {
      "type": "http",
      "url": "AGENT_MCP_ADDRESS",
      "headers": {
        "Authorization": "Bearer REPLACE_WITH_AGENT_API_KEY"
      }
    }
  }
}

Replace both placeholders before using the configuration. A different client may use another file format; use its documented remote MCP settings with the same address and header. Prefer its secret store or supported environment-variable reference when available. Do not commit a configuration containing a key.

If the client supports OAuth sign-in, you can authorize it in Rukou instead of sending a fixed API key. Choose one authentication method for that connection.

Check it

Ask the client to call rukou_status and check the returned agent and workspace. Then complete the first browsing task.

A successful connection does not automatically give a new key access to saved logins. Return to Agents if its connection needs access.