everruns-mcp

Work through Everruns MCP

Use the connected server's tools and resources. A local Everruns installation or shell is unnecessary: query and execute run the everruns command tree inside the server's sandbox. Tool names may carry a client-assigned prefix.

Select the organization and operation

Call me for identity and default organization. Call list_organizations when the user names another organization or the target is ambiguous. Pass the selected organization_id on every org-scoped tool call; there is no persistent current organization switch.

For a known operation, call discover with its exact operation name, such as {"query":"list_agents"}. Its bash_usage and schemas describe the deployed version. Use search for an unfamiliar operation. Discovery describes commands, not whether a particular agent exists: actually list or get the entity.

Use query for reads and execute for authorized writes. Both accept a commands string; returned command output is JSON suitable for jq filtering. For example, after discovering its usage:

{"commands":"everruns agents list"}

The command sandbox has no filesystem redirection. Keep intermediate JSON in variables or pipes, and copy bash_usage rather than probing --help.

Keep output targeted. Read-only resource catalogs at everruns://agents, everruns://harnesses, everruns://models, and everruns://capabilities provide summaries; use the discovered get/list commands when you need details or more than the catalog's bounded listing. Do not guess IDs, fields, or flags.

Run and continue a session

Find the requested agent and use its returned ID with agent_run and the user's message. Retain the returned session_id: creating a session starts work and does not mean the agent has finished. Use session_send_message for follow-ups in that session rather than starting over. Add budget limits when the user specifies them.

Read session_get_status for output and events. Use its last_event_id as since_event_id on subsequent reads to avoid rereading events. Follow returned hints and inspect completion, failure, or required input; session status alone does not prove the requested outcome. Space repeated polls apart and stop polling when user action is required. If the server offers task handles or event subscriptions and the host supports them, use the advertised contract.