list_agentsLABSCO SUMMARY
The selection audit — what the agent considered and set aside — is the tool that makes the fleet trustworthy.
Anything that autonomously opens PRs from research papers lives or dies on whether you believe its judgment. Being able to ask what else was on the table and why it was rejected turns the agent from an oracle into something you can argue with. Note that trigger_agent_run spends your model budget and their docs tell clients to confirm before calling it — respect that, because a dispatched fleet run is not free. Pausing revokes the key, so resuming means re-provisioning; it is a stop, not a snooze.
What it is
Remyx sits between your coding agents and production, ranking which candidate improvement is worth the engineering time. Their flagship agent, Outrider, opens draft PRs implementing recent research in your repos; this endpoint is how you drive the fleet.
What you get
- Fleet — list_agents, get_agent_activity, get_fleet_report with dispatches, drafts, merged and spend
- Inbox — get_inbox surfaces drafts to review, held discussions and health items such as an unmerged setup PR or a missing model key; dismiss_inbox_item archives one
- Diagnosis — analyze_agent_run root-causes a run from its job log with evidence and a suggested next step; list_agent_runs can include the selection audit, meaning what was considered and set aside
- Control — install_agent provisions on a repo, pause_agent revokes its key, trigger_agent_run dispatches a live run and spends model budget
- Research — search_research and get_research_asset over the index, plus account and connection tools
Requirements
A scoped API key. Keys are opaque and named, carrying an explicit scope set — a call to an unscoped route is refused. Personal keys never expire; automation keys carry a fixed lifetime. Remyx stores only the hash, and the plaintext is shown once.
Setup effort
Paste a URL with a key — add the endpoint to your client
USE CASES
01
Seeing what the fleet did
Headline, KPIs, per-agent state and chronology in one report.
02
Clearing what needs you
Drafts to review, held calls, and health items such as a missing model key.
03
Understanding a failed run
Root cause from the job log, plus what was considered and set aside.
04
Adding or stopping an agent
Provision on a repo, or revoke its key to stop it.
51 tools
Listed in project docs. Your client may show a different list.
get_agent_activityget_fleet_reportget_inboxdismiss_inbox_itemget_artifact_digestanalyze_agent_runlist_agent_runstrigger_agent_runpause_agentinstall_agentfork_repoget_install_statussearch_researchget_research_assetget_account_infolist_connectionscreate_project_from_reposget_project_metricsget_project_experiment_historyrefresh_project_extractionget_digestlist_interestsrefresh_interestsget_paperslist_projectscreate_interestupdate_interestdelete_interestlist_github_repos_for_interestanalyze_repo_for_interestget_repo_analysis_statusregenerate_interest_from_reposet_project_contextget_project_contextclear_project_contextcreate_experimentget_experimentsupdate_experimentlog_decisionget_experiment_contextrun_experiment_implementationget_implementation_statusset_decision_policyget_decision_policyclear_decision_policyprovision_validationcheck_validation_statuscancel_validationget_validation_resultsclose_loopBEFORE YOU INSTALL
What to know first
Tools you get
The project says 50; its docs name 51.
Requires
- an MCP client that can reach a remote endpoint
- A scoped bearer API key — there is no OAuth on this endpoint
Privacy controls
Key scoping (incl. resource-qualified grants), key revocation; no telemetry opt-out documented (server-side logging is product behavior)
INSTALLATION
Connect your client
Add the endpoint to your client.
Server setup
ENDPOINT URL
https://mcp.remyx.ai/mcpRequirements
- A scoped bearer API key — there is no OAuth on this endpoint
