Skip to main contentThis guide helps you resolve MCP server installation, editor configuration, authentication, and data lookup errors.
Installation issues
- Package not found
- Confirm the package name and your access to the npm registry.
- Try:
npm view testdino-mcp
- Command not found
- If using global install, confirm your npm global bin directory is on your PATH.
- If using
npx, ensure Node.js is installed and npx functions correctly.
- Permission errors
- macOS or Linux may require elevated permissions for global installs.
- Prefer
npx if you want to avoid setting up a global installation.
Editor integration
- Cursor does not show the server
- Validate JSON syntax in the config file.
- Confirm the file path you edited is the one Cursor reads.
- Restart Cursor fully.
- Claude Desktop does not detect the server
- Confirm the config file location for your OS.
- Confirm
npx works in your terminal.
- Restart Claude Desktop.
Authentication
- Missing token
- Set
TESTDINO_PAT in the MCP config under env.
- Restart the MCP client.
- Invalid or expired token
- Generate a new token and ensure it has access to at least one project and module.
- Re-run
health.
Data lookup
- Run ID not found
- Use
list_testruns to confirm the run exists and you have access.
- Test case not found
- Narrow the search by run, branch, environment, or time window.
- Use
list_testcase first, then get_testcase_details for the specific case.
API or network errors
- Confirm internet connectivity.
- Check whether your network blocks outbound requests.
- If you encounter rate limiting errors, reduce the query size and avoid using
get_all unless absolutely necessary.
If issues persist: