jev-conductor-router
MCP server and CLI where Jev decides if a coding task needs a Conductor cloud workspace, how hard it is, and which harness and model run it.
Overview
Conductor Jev Router uses Jev to decide, for a coding task, whether it needs a Conductor cloud workspace, how difficult it is, and which harness and model should run it, then calls Conductor's public API. The same npm package works as a stdio MCP server and a small CLI, so any agent client that can launch a local process can use it.
It is aimed at developers who use Conductor for coding agents and want task, quota and outcome-aware routing. Users bring their own keys: CONDUCTOR_API_KEY plus at least one Jev provider key, with a default provider chain of Orbio, then OpenRouter, then TypeSafe. The list summary says it always uses slow mode. The repository ships plugin layouts for Grok, Claude Code, Cursor and Codex, and the README states nothing calls home and no key is bundled.
What the decision model decides
| Type | Question | Answers |
|---|---|---|
| Yes / no | Does this coding task need a Conductor cloud workspace?(inferred) | — |
| Score | How hard is this task?(inferred) | — |
| Choice | Which harness and model should run it?(inferred) | — |
How it works
- Agent calls the MCP tool or CLI with a task description
- Jev answers workspace, difficulty and harness/model questions via the first available provider
- Router maps answers to a Conductor configuration
- Call Conductor's public API to launch the workspace
Strengths
- Works in any MCP-capable client; ships plugin layouts for several agents
- Provider fallback across Orbio, OpenRouter and TypeSafe
- No bundled keys or telemetry
Caveats
- Requires a Conductor key and at least one Jev provider key
- No accuracy or cost figures given
Getting started
`npx -y jev-conductor-router mcp` with CONDUCTOR_API_KEY and a Jev key (ORBIO_API_KEY, OPENROUTER_API_KEY or TYPESAFE_API_KEY) set.At a glance
- Type
- Project
- Status
- beta
- Language
- TypeScript
- Runtime
- Node 20+ MCP server and CLI
- Has code
- yes
- License
- MIT
Use cases and integrations
How curated lists describe it
Task, quota and outcome-aware Conductor routing with Jev. OpenRouter or TypeSafe; always slow mode.
hellogumbo/awesome-jev
Frequently asked questions
What does Jev decide?
Whether a task needs a Conductor workspace, how hard it is, and which harness and model should run it.
Which Jev providers work?
Orbio, OpenRouter or TypeSafe, tried in that order using whichever keys are set.
How do I run it?
Run `npx -y jev-conductor-router mcp` and register it in your MCP client config.
Related projects
Orchestrator that probes which coding agents are installed and logged in, then has Jev pick the best one for a task.
Agent skillbetaPythonHooks for Claude Code, Codex and pi that use Jev to suggest a skill each turn, plus a rule gate for subagent model routing.
HookbetaJavaScriptStandalone MCP server for T3 Code with one jev_route tool where Jev picks a model and reasoning-effort combination for a task.
MCP serverbetaTypeScriptChooses the model tier, skills and MCP servers for each coding-agent session with two Jev requests, then launches Claude Code or Codex.
MCP serverbetaPythonCursor plugin whose hooks ask Jev whether subagent spawns, file reads, writes and shell commands are worth taking.
PluginbetaJavaScriptPortable Codex skill that asks Jev to choose a model and reasoning tier for independent subtasks, with confidence gating.
Agent skillbetaPython