Skip to main content
Connect a compatible coding agent or developer client to Remyx through the Model Context Protocol. The reference below includes setup instructions for Claude Code, Claude Desktop, and other MCP clients, followed by the server’s registered tool names, arguments, responses, and permissions. A Studio feature is available through MCP only when a corresponding tool is registered. The same service supports the managed Slack agent and Studio’s Ask chat.

Architecture

The MCP server runs as a standalone service at mcp.remyx.ai. Connect using Streamable HTTP at https://mcp.remyx.ai/mcp, or SSE at https://mcp.remyx.ai/sse for clients that require it. Every tool calls the engine’s REST API with your own key, so ownership checks and data match the studio exactly. The same tools are also callable over plain HTTP: GET https://mcp.remyx.ai/api/tools lists them, and POST https://mcp.remyx.ai/api/tools/<name> invokes one with a JSON body of its parameters, for scripts that are not MCP clients.

Connecting

Claude Code

Add to your Claude Code MCP configuration (~/.claude/settings.json or project-level):

Claude Desktop

Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

Other MCP Clients

Any client supporting the MCP Streamable HTTP transport can connect using the URL https://mcp.remyx.ai/mcp with a Bearer token in the Authorization header.
Get your API key under Account > API keys at studio.remyx.ai/account?tab=keys.
MCP keys are scoped: a key only authorizes the tool categories its scopes grant, so a call to a tool outside the key’s scopes is rejected. See API Scopes for the available scopes and how to mint a key with the right ones.
Only scoped API keys (rmxu_… / rmxa_…) authenticate. Legacy JWT API tokens are rejected with 403 — "JWT API tokens have been replaced by API keys. Create one under Account → API keys and use it instead." Mint a key under Account > API keys, and remember the Bearer prefix; a missing prefix returns a 401 telling you so.

Tools

Parameter tables below are taken from the server’s tool signatures. Optional parameters are marked; everything else is required.

Outrider fleet tools

The fleet tool plane mirrors what the studio shows in Agents, Reports, and the Inbox.

Research and account

Discovery

Today’s recommended resources across your Research Interests.Parameters: period (today or week, default today), interests (optional list of interest names or ids), limit (per interest, default 5), include_github (default true).Returns: Recommended resources grouped by Research Interest, with titles, abstracts, relevance scores, and links.Example prompt: “Show me this week’s research digest for my retrieval interest”
List all of your configured Research Interests.Parameters: None.Returns: Array of interests with name, context, daily count, and is_active.
Resources for one Research Interest.Parameters: interest (name or id), period (default today), limit (default 10).Returns: Resources matched to the interest with metadata, scores, and Docker availability.
Trigger a fresh ranking for one or more interests.Parameters: interests (optional list of names or ids; all active interests if omitted).Returns: Confirmation that the refresh started. Results arrive via get_digest after processing.
Create a Research Interest.Parameters: name; optional context (the natural-language description Remyx ranks against), daily_count (default 2), is_active (default true), source_repo_url, project_id (a project-mode interest ranks against that project’s experiments), auto_update_from_experiments, included_experiment_ids, and the repo-analysis fields source_repo_metadata, generated_report, repo_analysis.Returns: The created interest with its id and status.
Update an interest.Parameters: interest_id; optional name, context, daily_count, is_active, source_repo_url, auto_update_from_experiments, included_experiment_ids, and the repo-analysis fields.Returns: The updated interest.Example prompt: “Pause my Long-context retrieval interest” (sets is_active: false)
Delete an interest and its recommendations.Parameters: interest_id.
For a project-mode interest, the project’s experiments with each row marked included or excluded from the curated subset that drives ranking.Parameters: interest_id.

Repo analysis

Generate or refine a Research Interest from a GitHub repository. Remyx profiles the repo and derives the interest context from what the code does.
Repos reachable through your connected GitHub integration.Parameters: None.
Start a repo analysis.Parameters: repo_url.Returns: task_id; poll with get_repo_analysis_status.
Poll an analysis task.Parameters: task_id.Returns: Status, and the generated report plus structured analysis when complete.
Re-run analysis for an existing interest.Parameters: interest_id; optional repo_url to analyze a different repo than the stored source.Returns: task_id; poll with get_repo_analysis_status.

Project context

Set a default project once and omit project_id on later calls. Tools that take a project_id resolve it from this context when the parameter is omitted.

Projects and the quality gate

See Evaluation & decision policy for what a policy contains.

Experiments

Create an experiment.Example prompt: “Create an experiment in Customer Support AI: hybrid search with re-ranking will lift resolution rate by 2 points, target metric resolution_rate, tags retrieval and re-ranking”
List experiments.Parameters: optional status, resource_id, project_id, interest, limit (20).
Update an experiment’s status, links, or results.Parameters: experiment_id; optional status, outcome, ticket_url, pr_url, pr_status, external_ticket_id, ticket_source, statsig_experiment_id, notes, source_type.
Record the team’s decision on an experiment and the reasoning behind it: the why behind a call.Parameters: experiment_id, decision (text with reasoning); optional outcome (ship, iterate, abandon).Example prompt: “Log decision on experiment 12: Ship to 100%. It combined retrieval with few-shot selection and produced our best single-experiment improvement.”

Implementation

Full implementation context for a research-sourced experiment: resource metadata, Docker environment, repo structure, and implementation plan.Parameters: experiment_id.
Reference sources for an experiment: GitHub repos and Docker images.Parameters: experiment_id.
Experiments ready to implement: they have context and no PR yet.Parameters: optional project_id, limit (20).
Launch a sandboxed coding-agent container, using your connected provider key, to implement the experiment and open a PR.Parameters: experiment_id.
Trigger the server-side implementation pipeline; the fallback when no coding agent is available.Parameters: experiment_id.
Poll the pipeline: pipeline_status, PR info, error detail, task_id.Parameters: experiment_id.
Link a PR you opened yourself to the experiment.Parameters: experiment_id, pr_url; optional branch_name, summary.

Experiment validation (Modal / W&B Launch)

These tools run the experiment-level evaluation path on connected compute (Modal or Weights & Biases Launch) against a locked eval template. They are unrelated to Validate, the PR validation agent, which has no MCP tools and is driven from the PR thread or POST /validate/runs.
  • create_eval_template_v2(name, category, project_id?, runtime="lighteval", lighteval_task?, dataset_ref?, variants_schema?, seeds=3, metric_keys?, decision_criteria?, compute_hints?): a draft template with versioning.
  • lock_eval_template(template_id): one-way; a locked template is what runs execute against.
  • launch_eval_run(experiment_id, github_url, variants (list), template_id?, template_config?, seeds=3, pr_number?, pr_url?): builds the environment, runs the variants on Modal sandboxes, receives results by webhook, and computes a verdict.
  • get_eval_run(run_id): status, results received, verdict so far.
  • cancel_eval_run(run_id): terminates sandboxes and marks the run cancelled.
  • get_eval_run_results(run_id): final aggregated results with a Pass / Warn / Fail verdict.
Provision compute and start a validation for an experiment against a locked template.Parameters: experiment_id; optional template_name.Returns: A job handle; poll with check_validation_status.
Parameters: experiment_id.Returns: Job status and progress.
Parameters: experiment_id.
Normalized baseline-vs-feature results for an experiment.Parameters: experiment_id; optional include_raw.
Pulling live treatment vs. control results from Statsig or LaunchDarkly is still pending; those data arrive via update_experiment for now.
Composite: fetch the validation result, update the experiment’s status, close its ticket, and notify a channel.Parameters: experiment_id; optional disposition (shipped, iterating, rejected, abandoned), notify (channel).

HTTP-only tools

create_ticket (create a Linear, Jira, or GitHub ticket for an experiment) is registered for the HTTP surface only: POST https://mcp.remyx.ai/api/tools/create_ticket. Every other tool above is available on both.

Slack Agent

The MCP server also powers the managed Slack agent. When you @mention the Remyx bot in Slack, it uses the same tools to respond: fetching digests, listing agents’ output, logging decisions. See Connectors > Slack for setup.

Studio Ask chat

The ✦ Ask button in the studio topbar opens a chat on every page; the Inbox’s Ask and an agent’s Ask about this agent open the same panel scoped to that agent. The panel docks to the right or the bottom, resizes, and minimizes to a pill. Each answer has Copy and, where it proposes work, Start an agent run from this, which hands the proposal to a confirm-gated dispatch. Two backends:
  • Remyx AI, hosted (the default). Works with nothing connected and answers from the server-assembled context for the agent, run, or Inbox item you opened it from.
  • Bring your own provider. Pick a connected Anthropic, Z.ai, or Moonshot AI key to upgrade the chat to a live agent session with the Remyx tool plane. The choice is remembered in your browser; unconnected providers stay visible but disabled.
A live session can call a read-only allowlist of the tools above with your own authority (fleet, research, project, experiment, and eval reads, plus project context), and the CLI’s web search and fetch tools for public pages such as papers and upstream repos. When you have GitHub or Hugging Face connected, their MCP servers are attached read-only with your own tokens. There is no shell or filesystem. Mutating tools (trigger_agent_run, pause_agent, install_agent, fork_repo) are deliberately absent: the chat proposes those actions in text, and the studio’s confirm-gated buttons execute them through the engine. A turn that fails on a transient error is retried, up to three attempts.

Implementation Pipeline

For research-sourced experiments with a launch context, a connected coding agent can run the full implementation flow:
  1. Fetch the experiment context (resource metadata, Docker environment, repo structure, implementation plan)
  2. Read the target repository
  3. Generate code changes implementing the technique
  4. Push a branch and open a PR
  5. Link the PR back to the experiment
The PR status syncs via GitHub webhooks. When the PR is merged, the experiment status updates automatically. Scheduled agent runs are the always-on version of this same loop.

Registered tools

Every tool the server registers, from the server source at the time of writing.

Next Steps

Agents

The fleet the tool plane drives

Connect Slack

Set up the managed Slack agent

Account > API keys

Mint a scoped key for your MCP client

API Reference

REST API documentation