Skip to main content
Continue official logo

​
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 .continue/mcpServers/dreamtune.yaml. Preserve any other servers or settings.
Install @dreamtune/sdk globally, then supply DREAMTUNE_API_KEY through Continue’s secrets configuration. Keep name, version and schema in the standalone file. This guide uses the documented local stdio form. Restart the agent after changing server settings.

​
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 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 for 401, missing scopes, timeouts and key/environment problems. Configuration verified against the official client documentation.