> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dreamtunelabs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Roo Code (legacy)

> Connect Roo Code (legacy) to Dreamtune MCP and install scoped workflow skills.

<img src="https://mintcdn.com/dreamtune/alDlJCy5wJhi5BBd/images/agents/roo-code.png?fit=max&auto=format&n=alDlJCy5wJhi5BBd&q=85&s=9afb155708533d3fe3fc8befe7a8b298" alt="Roo Code (legacy) official logo" width="48" height="48" data-path="images/agents/roo-code.png" />

## Before you connect

Create a Dreamtune workspace API key with only the permissions you need.
Hosted HTTP setup needs no Dreamtune package installation. Local stdio setup
requires Node.js 22.20 or later and the published CLI.

## Configure

Merge this server entry into the configuration opened from Roo's MCP settings. Preserve any other servers or settings.

```json theme={null}
{
  "mcpServers": {
    "dreamtune": {
      "type": "streamable-http",
      "url": "https://mcp.dreamtunelabs.com/mcp",
      "headers": {
        "X-Dreamtune-API-Key": "YOUR_DREAMTUNE_KEY"
      }
    }
  }
}
```

Roo Code's official repository reports that its extension shut down on May 15. This configuration is retained for existing compatible installations, not as a recommendation to install an unsupported client. Consider an actively maintained client such as Cline. Replace the key privately; Roo's transport spelling differs from Cline's.

## Verify the connection

Restart the client after changing settings or its environment. Open its MCP
server/tool status view and check that Dreamtune tools are listed. Ask it:

> Use Dreamtune to read model request limits. Do not execute a model, tool or GPU.

Confirm model\_limits returns limits before authorizing paid work. Then inspect a
catalog schema and use one explicitly approved operation. Keep client approval
controls enabled. Never put the key in a chat message, URL or repository.

## Add workflow instructions

Install the [Dreamtune skills](/connect/skills-install) into the skills directory
supported by your client, or copy the platform skill into a user instruction
workflow. A skill guides the agent; MCP provides execution. Neither grants extra
key permissions. See [troubleshooting](/errors) for 401, missing scopes, timeouts
and key/environment problems.

Configuration verified against [the official client documentation](https://docs.roocode.com/features/mcp/using-mcp-in-roo).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.