@testsprite/testsprite-mcp
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Contacts while installing and starting: nothing
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y @testsprite/testsprite-mcp@0.0.48
Installing a package runs its code. Use a sandbox for anything you have not read.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
1 tool with commands in capitals or very long text
- Gives the agent orders in
testsprite_bootstrap:t-time project initialization when no configuration exists. NEVER call for: adding new test cases, modifying tests, re-running tests, or any operation on an already-
Common and usually harmless: it is how many makers stress how a tool should be used.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
testsprite_bootstrap localPort, pathname, type, projectPath, testScope
BEFORE calling this tool, check if testsprite_tests/tmp/config.json exists in the project. If config.json EXISTS, DO NOT call this tool - proceed directly with other tools instead. This tool is ONLY for first-time project initialization when no configuration exists. NEVER call for: adding new test cases, modifying tests, re-running tests, or any operation on an already-configured project. Note: this MCP tests a locally-running app — it tunnels your local server, so make sure it's running before you proceed.
testsprite_generate_code_summary projectRootPath
Analyze the project repository and summarize the codebase.
testsprite_generate_standardized_prd projectPath
Generate a structured standard PRD.
testsprite_generate_frontend_test_plan projectPath, needLogin
Generate test plan for frontend test.
testsprite_generate_backend_test_plan projectPath
Generate a backend test plan with Testsprite.
testsprite_generate_code_and_execute projectName, projectPath, testIds, additionalInstruction, serverMode
Generate and execute tests. Before calling this tool, ensure the local project is running — preferably in production mode (e.g. `npm run build && npm run start` for Next.js, `npm run build && npm run preview` for Vite). If you started the project with a production build+serve command, set serverMode to 'production' (note: serverMode is also auto-detected from the running process). If running a dev server (e.g. npm run dev), leave serverMode as default — frontend tests will be limited to 15 high-priority tests to prevent dev server overload. If local server is running and test plan is already generated, call this tool directly — DO NOT call testsprite_bootstrap first. AI assistant analyzes the test results and saves a markdown report. This runs against your locally-running server.
testsprite_open_test_result_dashboard projectPath, modificationContext
Open an interactive web dashboard to review and modify finished test cases. Use this tool when users want to review test results, fix failing tests, or modify test steps. The dashboard displays all test cases with their execution status, allows users to view test details, edit individual steps, and re-run tests from any step. Prerequisites: (1) Tests must have been generated first using 'testsprite_generate_code_and_execute', (2) Local project must be running on the configured port for re-running tests.
testsprite_check_account_info
Check the current user's TestSprite account: name, email, workspace, plan (or Paused), and remaining credits.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | BUSL-1.1 |
|---|---|
| Needs | node >=22 |
| Source | not stated |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-bLQZAgXEw5NVRZAMpjhuwvrC6smuznEakPpyTG2MAynTPoNdepl3iGL10JUoIF54CMF7qv522tTfqVDs6U2xPg== |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40testsprite/testsprite-mcp)
New version out? Ask for a fresh report.