cucumberstudio_find_action_words_by_tags
Find action words by tags in a project
LABSCO SUMMARY
Everything here reads; nothing writes.
The 14 tools cover the reporting side of Cucumber Studio end to end — scenarios, action words, runs, executions, builds, environments — which is enough to answer why did this fail and what is this test really checking from an editor. Authoring, re-running and any repair still happen in Cucumber Studio itself, so this sits beside that workflow rather than replacing it.
What it is
A read-only client for Cucumber Studio, 14 tools covering projects, scenarios, action words, test runs, executions, builds and execution environments.
What you get
- Projects listed for the authenticated account and fetched in detail, with filtering and pagination on the list calls
- Scenarios listed per project, fetched individually, or found by the tags they carry
- Action words — the reusable steps a scenario is assembled from — listed, fetched and searched by tag, so a scenario can be read down to what it actually does
- Test runs listed and fetched, with cucumberstudio_get_test_executions returning the individual results inside a run
- Builds listed and fetched for a project
- Execution environments listed, which is how a result gets tied to where it ran
Requirements
A Cucumber Studio account with API access, supplying CUCUMBERSTUDIO_ACCESS_TOKEN, CUCUMBERSTUDIO_CLIENT_ID and CUCUMBERSTUDIO_UID.
Setup effort
One command plus credentials — npx cucumberstudio-mcp, then supply credentials
USE CASES
01
Working out why last night's run failed
List the project's recent runs, open the one that failed, and pull its individual executions to see which tests failed rather than that the run did.
02
Understanding what a scenario actually checks
Read the scenario, then read the action words it is assembled from — the reusable steps are where the real behaviour lives, and a scenario title alone will not tell you what it asserts.
03
Pulling out the slice of the suite that carries a tag
Find the scenarios tagged for the release you care about, and the action words carrying the same tag, to see how far a change to one shared step reaches.
04
Matching a failure to the build and environment it ran on
List the project's builds and open the one the failing run belongs to, then check the execution environments to rule out the failure being about where it ran rather than what changed.
14 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
cucumberstudio_find_scenarios_by_tags
Find scenarios by tags in a project
cucumberstudio_get_action_word
Get detailed information about a specific action word
cucumberstudio_get_build
Get detailed information about a specific build
cucumberstudio_get_project
Get detailed information about a specific project
cucumberstudio_get_scenario
Get detailed information about a specific scenario
cucumberstudio_get_test_executions
Get test executions (individual test results) for a test run
cucumberstudio_get_test_run
Get detailed information about a specific test run
cucumberstudio_list_action_words
List all action words (reusable test steps) in a project
cucumberstudio_list_builds
List all builds in a project
cucumberstudio_list_execution_environments
List all execution environments in a project
cucumberstudio_list_projects
List all projects accessible to the authenticated user
cucumberstudio_list_scenarios
List all scenarios in a project
cucumberstudio_list_test_runs
List all test runs in a project
BEFORE YOU INSTALL
What to know first
Tools you get
14 tools when we connected. Every tool only reads; nothing creates, edits, runs or deletes anything in Cucumber Studio.
Requires
- npx on PATH
- CUCUMBERSTUDIO_ACCESS_TOKEN in your environment
- CUCUMBERSTUDIO_CLIENT_ID in your environment
- CUCUMBERSTUDIO_UID in your environment
Where it runs
Both documented setups run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 14 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx cucumberstudio-mcpMCP Clients
Any MCP client — npx
ANY MCP CLIENT — NPX · JSON
{
"mcpServers": {
"cucumberstudio": {
"command": "npx",
"args": [
"cucumberstudio-mcp"
],
"env": {
"CUCUMBERSTUDIO_ACCESS_TOKEN": "<YOUR_CUCUMBERSTUDIO_ACCESS_TOKEN>",
"CUCUMBERSTUDIO_CLIENT_ID": "<YOUR_CUCUMBERSTUDIO_CLIENT_ID>",
"CUCUMBERSTUDIO_UID": "<YOUR_CUCUMBERSTUDIO_UID>"
}
}
}
}Any MCP client — Docker Hub
ANY MCP CLIENT — DOCKER HUB · JSON
{
"mcpServers": {
"cucumberstudio": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"--env-file",
"<YOUR_PATH_TO_ENV>",
"herosizy/cucumberstudio-mcp"
]
}
}
}
