Hue MCP

The Hue MCP server lets your coding agent create Worlds, start instances, and inspect what changed. It also reads traces, turns them into cases, and works with eval sets, evaluators, and runs. Hue returns stored data with links that open each object in Hue. The server is at https://mcp.hue.run/mcp. Any MCP client or agent that supports remote servers connects by signing in with Hue (OAuth) or with a project key; Connect has each client’s setup, and Tools lists every tool.

What your agent can do

Area	Read	Change, with write access
Worlds	Worlds and their versions, saved instances, their state, requests, steps and changes	Generate Worlds, import app records, or build from trace evidence; start and stop instances; send Slack user input; save and check cases from finished attempts
Traces	Search traces and spans, read recorded content and files, count and compare with aggregates, confirm a trace arrived	Import trace exports you already hold, queue findings or intent classification for traces that missed them
Classifiers	Attention states and findings, intents, request answers and trace-check results	Define, test and activate trace checks; publish the intent taxonomy
Cases	Check which traces can become cases, read cases and drafts, see where a run diverged from its source trace	Build a case from a trace, review and publish it, convert suggested cases in bulk
Eval sets and evaluators	Eval sets, versions, cases, evaluators and their published versions	Create and edit eval sets and cases, freeze versions, publish and rename evaluators, set tags, archive
Runs	Runs, case results, executions, scoring runs, judge results and alignment	Launch a run on your connected agent or a managed target, rename runs, score saved outputs, label judge results
Project	Projects, context, members and keys	Change project settings, revoke keys, register managed targets, create projects, send product feedback

search_hue_docs also searches these docs from the same connection.

Example requests

Ask your agent	Where to read more
”Generate a World with Slack and Linear for a fictional company’s onboarding tasks.”	Generate a World
”Start an instance of this World and show me what my agent changed.”	Worlds
”What needs attention in the last 24 hours, and why? Link the traces.”	Recipes
”Which tools failed most often this week, and what did they return?”	Recipes
”Import these traces into my Hue project.”	Bulk import existing traces
”How often does the agent hand work to sub-agents?”	Classifiers
”Turn this trace into a case, then run my agent against it.”	Create a case
”Summarize the latest run and compare it with the previous one.”	Run your agent

Recorded content, names and metadata come from your application and its users. The server marks them as untrusted data, so your agent treats instructions inside them as quotes, never as requests.

Tool discovery

A connection doesn’t list every tool by default. Without a selection it lists the production reads and three catalog tools: search_hue_tools finds any other tool your access allows, and execute_hue_tool and execute_hue_write_tool call it with the same checks as a direct call. A tool missing from your agent’s list is therefore one search away, not unavailable. Clients that search their own tool lists, such as Claude Code and Codex, can list everything with ?toolsets=all; choose toolsets shows the other selections. get_project_context reports which toolsets the connection lists and how many tools each one leaves out.

Access

Connection	Can do
A Read key	Every read, including recorded content. No writes.
A Read and write key	Reads and writes for its project.
Sign in with Hue	Reads and writes for the active projects of one organization, within your role.

Writes need write access and no ?read_only=true.
Project settings, key revocation, managed targets, the intent taxonomy, the judge alignment bar, creating projects and queueing findings or intent classification need an owner or admin: the key’s creator, or the member who signed in.
Creating a project key needs a Read and write key created by an owner or admin; a sign-in connection cannot create keys. Creating a project needs a sign-in connection.
Billing and plan changes, invitations and role changes stay in Settings. Telemetry is sent over OTLP, and artifact bytes over HTTP, not through MCP.

Permissions lists each tool’s requirement.

Two MCP servers

https://mcp.hue.run/mcp reads and changes your project’s data. https://docs.hue.run/mcp is a separate, documentation-only server that searches these docs and cannot read a Hue project. The Hue MCP server reaches the same documentation through search_hue_docs, so most agents need only the project server. To add tracing to your application, use the Hue skill and the setup prompt; the MCP server reads what that tracing sends.

Get started

Worlds

MCP

Simulations

Traces

Evals

Traces to cases

Classifiers

Reference

Hue MCP

What your agent can do

Example requests

Tool discovery

Access

Two MCP servers

​What your agent can do

​Example requests

​Tool discovery

​Access

​Two MCP servers

What your agent can do

Example requests

Tool discovery

Access

Two MCP servers