Skip to main content

What is the Orq MCP?

The Orq Model Context Protocol (MCP) server provides AI code assistants with direct access to the Orq.ai workspace. With 38 specialized tools, manage experiments, create datasets, configure evaluators, and analyze traces without leaving the IDE.

Installation

Point the assistant at the MCP server and authenticate with an API key:

Code Assistants

See detailed documentation for the following code assistants:

Claude Code

Official Anthropic CLI for Claude with MCP integration

Claude Desktop

Use Orq MCP in Claude’s desktop application

Codex

AI coding assistant with MCP protocol support

Cursor

AI-first code editor with native MCP support

VS Code

AI-powered editor with GitHub Copilot and native MCP support

Warp

AI-powered terminal with native MCP support

Key Capabilities

Agent Creation

Create, update, and configure agents with instructions, tools, models, evaluators, and guardrails

Experiment Management

Run experiments, compare prompts or models side-by-side, and export results

Dataset Operations

Create datasets, add or edit datapoints, and generate synthetic test data

Analytics & Insights

Query usage, cost, latency, and error metrics across the workspace

Evaluator & Guardrail Configuration

Create and update LLM-as-a-Judge and Python evaluators, and attach guardrails to agents

Docs Exploration

Search the Orq.ai documentation without leaving your IDE

Available Tools

The Orq MCP provides 38 tools across 11 categories:

Examples

Create an agent from scratch
The assistant will:
  1. Use create_agent with the name, instructions, and model (openai/gpt-4.1)
  2. Return the agent key and configuration summary

Review and update agent instructions
The assistant will:
  1. Use get_agent to retrieve the current configuration
  2. Display the existing instructions
  3. Use update_agent with the revised instructions field, versionIncrement, and versionDescription
  4. Confirm the update and new version
Use invoke_model to call any model directly via the Responses API.Parameters
Call an o-series model with reasoning
The assistant will:
  1. Use invoke_model with model: "openai/o3" and reasoning: { effort: "medium", summary: "concise" }
  2. Return the model response along with the reasoning summary

Include encrypted reasoning content
The assistant will:
  1. Use invoke_model with model: "openai/gpt-5" and include: ["reasoning.encrypted_content"]
  2. Return the response with the encrypted reasoning block attached
Find errors from the last 24 hours
The assistant will:
  1. Calculate the unix timestamp for 24 hours ago
  2. Use list_traces with filter status:=ERROR && timestamp:>TIMESTAMP and sort by timestamp:desc
  3. Display trace IDs, names, durations, and timestamps
  4. Summarize the most common error types and their frequency

Detect regressions after a model switch
The assistant will:
  1. Use query_analytics with metric: "latency" and group_by: ["model"] for the period before the switch
  2. Repeat for the period after the switch
  3. Compare average latency per model across both windows and surface any regressions

Find the slowest traces
The assistant will:
  1. Use list_traces sorted by duration_ms:desc, filtered to today, limit 5
  2. Use list_spans with each trace_id to retrieve the full span tree
  3. Surface bottlenecks and latency outliers

Filter traces by thread ID
The assistant will:
  1. Use list_traces with thread_id: "thread_abc123"
  2. Return all traces associated with that conversation thread
  3. Surface turn count, total cost, and any errors across the session
Compare two models on an existing dataset
The assistant will:
  1. Search for the “user-queries” dataset using search_entities
  2. Use create_experiment with two model configurations and auto_run enabled
  3. Return the experiment ID once both configurations have run

Compare two prompt strategies
The assistant will:
  1. Search for the dataset using search_entities
  2. Use create_experiment with two prompt variants and auto_run enabled
  3. Use get_experiment_run to retrieve evaluation metrics
  4. Compare the variants and summarize which performed better

Export experiment results
The assistant will:
  1. Use list_experiment_runs to find the most recent run
  2. Use get_experiment_run with CSV export format
  3. Return a signed download URL for the CSV file
Create a synthetic dataset
The assistant will:
  1. Generate 50 synthetic question/answer pairs
  2. Use create_dataset to create the dataset
  3. Use create_datapoints to add all entries in bulk, each formatted as { inputs: { question: "..." }, expected_output: "..." }

Import data from code
The assistant will:
  1. Parse the JSON from the selection or context
  2. Use create_dataset with an appropriate name
  3. Use create_datapoints to add each entry as a datapoint

Update or clean up a dataset
The assistant will:
  1. Use search_entities to find the “staging-tests” dataset and retrieve its ID
  2. Use list_datapoints to retrieve all entries
  3. Filter for datapoints with empty expected_output
  4. Use delete_datapoints to remove them in batches
Retrieve an evaluator’s configuration
The assistant will:
  1. Search for the evaluator using search_entities to resolve its ID
  2. Use get_llm_eval or get_python_eval to retrieve the full configuration
  3. Display the prompt, model, output type, and other settings

Create an LLM-as-a-Judge evaluator
The assistant will:
  1. Use create_llm_eval with a scoring rubric for tone classification
  2. Confirm the evaluator ID and configuration

Create a Python evaluator
The assistant will:
  1. Write a Python snippet that parses the response and validates JSON structure
  2. Use create_python_eval to register it in the workspace

Create an experiment with evaluators
The assistant will:
  1. Search for the dataset using search_entities
  2. Use search_entities to find the evaluator and get its key, or use the key returned by create_llm_eval / create_python_eval if created in the same session
  3. Use create_experiment with both the dataset ID and evaluator ID, with auto_run enabled

Update an existing evaluator
The assistant will:
  1. Search for the evaluator using search_entities
  2. Use update_llm_eval with the evaluator ID, updated prompt, and output_type: "boolean"
  3. Confirm the new configuration
Delete a workspace entity
The assistant will:
  1. Search for the experiment using search_entities
  2. Use delete_entity with type: "experiment" and the resolved ID
  3. Confirm deletion
Supported type values: agent, prompt, experiment, evaluator, knowledge, memory_store, prompt_snippet (Skills), sheet, tool. Use delete_dataset to delete a dataset along with all its datapoints.
Look up a feature in the Orq.ai docs
The assistant will:
  1. Use search_docs with a relevant query
  2. Return matching documentation sections with guidance and examples
  3. Summarize the answer in context

Get started with a specific product area
The assistant will:
  1. Use search_docs to find Router onboarding content
  2. Return setup steps, configuration options, and quick-start examples
Get a workspace snapshot
The assistant will:
  1. Use get_analytics_overview with a 7-day range
  2. Return total requests, cost, tokens, error rate, latency, and top models

Drill into a specific model’s performance
The assistant will:
  1. Use query_analytics with metric: "errors", filtered by model and a 7-day range
  2. Use query_analytics with metric: "cost", filtered by model and a 7-day range
  3. Surface error rate trends and cost breakdown side by side

Identify the most expensive models
The assistant will:
  1. Use query_analytics with metric: "cost", group_by: ["model"], and a 30-day range
  2. Aggregate cost per model across all time buckets and rank them by total spend

Skills

Orq Skills layer pre-built multi-step workflows on top of these MCP tools: build agents, run experiments, analyze trace failures, and more with a single command.

Orq Skills

Pre-built workflows and slash commands for the full Build, Evaluate, Optimize lifecycle