Spur
ActiveAn AI agent for Spur. It works in a scene with a live connection to Spur. It asks before it writes, and every run is traced.
Connect Spur to run its AI QA agents from a scene: list suites and tests, run test plans against staging or production, read run overviews with console and network logs, and create plain-English tests and scenario tables. Spur drives real browsers and devices in its own cloud.
What you can connect
Add these to your scene and AI gets access.
Agentic QA for web, mobile, and e-commerce flows. List suites and tests, run test plans against any environment, read run overviews, console and network logs, and create plain-English tests and scenario tables.
Tools
What the agent can do once this is connected.
Reads 20
See data. Nothing changes.
applications
List the applications on the account, or switch the active one.
list_tests
List tests in the active application, with step-level detail for one test.
list_suites
List test suites with their environments and scenario table.
list_folders
List folders and the suites they contain.
list_scenarios
List scenario tables with their columns and rows.
list_environments
List environments and their configured properties.
list_login_tests
List login tests a suite can reuse for saved login state.
list_test_plans
List test plans with suites, environments, and last run time.
get_test_guidance
Return Spur's test-writing guide and step format reference.
generate_test_steps_from_loom
Draft test steps from a public Loom video.
get_test_run_overview
Summarize a run's status, step results, warnings, and failures.
get_test_run_details
Read a run's steps, sub-steps, configuration, and artifacts.
get_test_runs
List the last runs of a test.
get_recent_runs
List recent runs across the application within a time window.
get_coverage_snapshot
Aggregate runs and failures per environment and suite over a window.
get_test_run_console_logs
Read browser console output from a run.
get_test_run_network_logs
Read HTTP requests and responses captured during a run.
get_test_run_screenshots
Fetch screenshots from a run.
get_test_plan_runs
List recent runs of a test plan with pass and fail counts.
get_test_plan_run_overview
Show every result in a plan run, failures first.
Writes 11
Change data in the connected system. Every one of these stages for your approval before it runs.
create_test
Create a test in a suite from plain-English steps.
needs approval
update_test
Update a test's title, environment, or steps.
needs approval
save_suite
Create or update a suite, move tests into it, or set its dependency graph.
needs approval
create_scenario_table
Create a scenario table with columns and rows.
needs approval
update_scenario_table
Edit a scenario table's columns or rows.
needs approval
add_scenario_rows
Add rows to an existing scenario table.
needs approval
connect_scenario_table
Connect or disconnect a scenario table from a suite.
needs approval
run_tests
Run one or more tests in an environment, browser, and viewport.
needs approval
run_test_plan
Run a full test plan across its suites and environments.
needs approval
create_test_plan
Create a test plan grouping suites and environments.
needs approval
update_test_plan
Replace a test plan's suites and environments.
needs approval
Connect Spur over MCP
Daslab is itself an MCP server.
Connect Spur in a scene, then pin that scene's URL in Claude Code, Cursor, or any MCP client. The agent there gets your Spur tools, and your approval gate and trace travel with them.
https://daslab.run/mcp/<your-world>/<your-scene>One scene can hold Spur and everything else you connect, so a single endpoint carries them all. Set up a client.
Use cases
- Run a regression test plan after every deploy and read what failed
- Sweep every product page in a launch before the team logs on
- Reproduce a support ticket as a test run with video and logs attached
- Create tests from tickets and pull requests in plain English
Similar integrations
Others in Developer Tools.
Ready to try Spur with Daslab?
Get started with CLI