Prerequisites
Install
arga-context server entry to supported local clients:
~/.cursor/mcp.json~/.claude/mcp.json~/.config/codex/mcp.json
mcpServers entries and uses the device credential stored by arga login.
The installed server points to <api-url>/mcp with a bearer authorization header:
Custom API URL
ARGA_API_URL before running the installer.
Twin tools
get_twin_catalog
get_twin_catalog
Lists available twin names, labels, surface kinds, and twin-hosted MCP paths where available.
create_twin_run
create_twin_run
Provisions and optionally seeds one or more twins.
The result contains the Twin Run ID. Poll
get_twin_run until the status is ready or failed.get_twin_run
get_twin_run
Returns status, per-twin URLs, environment variables, access details, and seed results for a Twin Run.
reset_twins
reset_twins
Restores a ready short-lived Twin Run to the baseline captured at provisioning time.
extend_twins
extend_twins
Extends a Twin Run within the TTL allowed by your plan.
teardown_twins
teardown_twins
Ends a short-lived Twin Run immediately.
Choose a generation mode
For a prompt with complex requirements, an agent can callcreate_twin_run with:
get_twin_run until the run is ready or failed. A saved scenario_id reuses existing seed data; changing the mode does not regenerate it. To save a reusable scenario, use the REST API or the CLI.
Persistent Scenario environment tools
ensure_scenario_twin_environment
ensure_scenario_twin_environment
Creates or returns the persistent twin environment attached to a saved Scenario. Pass
scenario_id, optional comma-separated twins, and optional public access.get_scenario_twin_environment
get_scenario_twin_environment
Returns the status and stable twin URLs for one Scenario.
reseed_scenario_twin_environment
reseed_scenario_twin_environment
Restores a ready persistent environment from its saved Scenario.
delete_scenario_twin_environment
delete_scenario_twin_environment
Tears down the persistent environment attached to one Scenario.
list_scenario_twin_environments
list_scenario_twin_environments
Lists persistent Scenario environments owned by the authenticated account.
Browser test tools
create_test_run
create_test_run
Starts an ad hoc browser Test Run.
Point the application at any required twin endpoints before starting the Test Run.
run_test
run_test
Runs a Saved Test by
test_id. Pass start_url to override the URL stored with the test and prompt to add run-specific guidance.get_test_run
get_test_run
Returns status, events, artifacts, editable TestConfig, and summary fields for a Test Run.
list_tests
list_tests
Lists Saved Tests. Pass
repo_full_name to filter them to one repository.Compatibility tools
Older servers may also exposestart_url_validation, get_validation_results, cancel_validation_run, provision_twins, get_twin_provision_status, and cancel_run. Prefer the Twin Run and Test Run tools above for new agent workflows.
Your MCP client’s tools/list response is the authoritative list for the server version you are connected to.
