Skip to main content
Managed Research MCP is the agent-client interface for starting, steering, and inspecting runs from Codex, Claude Code, Cursor, and similar tools.

Connect

Set SYNTH_API_KEY in the environment or in your MCP client configuration. Use SYNTH_BACKEND_URL only when targeting a non-production backend.

Smoke test

Ask your MCP client:
The client should call smr_list_projects. An empty list means auth and connectivity are working.

Start a one-off run

Ask your MCP client:
The underlying MCP call is smr_start_one_off_run with initial_runtime_messages.

Start a project-scoped run

Use a project when the worker needs reusable repo bindings, files, datasets, credentials, notes, or budgets. Ask your MCP client:
Useful tools:
  • smr_create_runnable_project
  • smr_attach_source_repo (and GitHub setup tools as needed)
  • smr_prepare_project_setup
  • smr_get_launch_preflight
  • smr_trigger_run

Inspect evidence

Ask:
Useful tools:
  • smr_get_run
  • smr_get_run_execution
  • smr_get_run_transcript
  • smr_list_run_artifacts
  • smr_get_artifact_content
  • smr_list_run_actor_logs
  • smr_get_run_usage

Common launch failures

Launch denials are MCP tool errors, not success payloads with embedded error fields.