Lupa MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lupa_run_testsA | Run Lupa tests and return structured JSON results. Use this to identify failing tests. |
| lupa_list_testsB | List all available test files, suites, and tests without running them. Optionally filter the list. |
| lupa_list_test_filesA | List test files resolved by Lupa config without running tests or starting Vite/Playwright. |
| lupa_initA | Initializes lupa testing framework in a project with default scaffolding, avoiding interactive prompts. MUST be used INSTEAD of running |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool serves a distinct purpose: initialization, listing test files, listing individual tests, and running tests. There is no overlap or ambiguity in their functions.
All tools follow a consistent 'lupa_verb_noun' pattern using snake_case, making the naming predictable and easy to understand.
Four tools is appropriate for a focused testing framework, covering initialization, listing, and execution without unnecessary overhead.
The tool set covers the core testing workflow (init, list, run). Missing features like test filtering within run tests or configuration updates are minor gaps.