Skip to main content
Resolve MCP server installation, editor configuration, authentication, and data lookup errors.

Quick Reference

Installation Issues

The package name is incorrect or your npm registry is misconfigured.Verify the package exists:
If this returns package info, the registry is fine. Check for typos in your MCP config. If it returns a 404, check your npm registry setting:
It should be https://registry.npmjs.org/.
Your npm global bin directory is not on your PATH.Find where npm installs global packages:
Add it to your PATH. On macOS and Linux, global commands live in its bin subdirectory. On Windows, they live in the prefix directory itself:
Or skip the issue entirely by using npx:
macOS and Linux may block global installs without elevated permissions.Fix by changing npm’s default directory:
Or use npx instead of a global install. It requires no special permissions.

Editor Integration

Verify the server was added:
If testdino does not appear, re-run the add command. Pass the token through the TESTDINO_PAT environment variable, which is what the server reads:
A token passed only as a --pat flag is ignored, so the server connects but fails authentication with a “Missing TESTDINO_PAT” error. Check that your token is correct and set as the environment variable.
  1. Open your config file and validate JSON syntax (trailing commas, missing brackets):
  1. Confirm the file path Cursor reads. Common locations:
    • Project: .cursor/mcp.json
    • macOS/Linux home: ~/.cursor/mcp.json
    • Windows home: %USERPROFILE%\.cursor\mcp.json
  2. Restart Cursor fully. Quit and reopen, not reload window.
  3. Go to Settings → Tools & MCP and check if TestDino appears.
  1. Confirm config file location for your OS:
    • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
    • Windows: %APPDATA%\Claude\claude_desktop_config.json
    • Linux: ~/.config/Claude/claude_desktop_config.json
  2. Verify npx works in your terminal:
  1. Restart Claude Desktop completely (quit from system tray/dock, reopen).

Authentication

The token is expired, revoked, or was copied incorrectly. An expired or revoked token can also return Token has expired or Token has been revoked.
  1. Go to app.testdino.com → User Settings → Access Tokens
  2. Check the token’s expiration date and status
  3. If expired or revoked, generate a new token
  4. Copy the new token and update your MCP config
  5. Restart your MCP client
  6. Run health again
The token exists but has no project access granted.
  1. Go to app.testdino.com → User Settings → Access Tokens
  2. Open the token’s ⋯ menu and select View details to see its scope
  3. Ensure at least one project is included
  4. A token cannot be edited. To add a project, generate a new token that includes it, then revoke the old one with Revoke token
The token does not include the project in the tool call. Tokens do not limit access by module: selecting Test Runs or Manual Tests for a project gives the token access to that whole project.
  • Confirm the projectId matches a project health lists. Project names are not accepted; use the project ID.
  • To add a project, generate a new token that includes it, then revoke the old one.

Data Lookup

Filters may be too narrow. Try widening your query:
  • Remove by_branch, by_environment, or by_author filters
  • Extend by_time_interval to weekly or monthly
  • Confirm you are querying the correct project
If the project is new and has no uploads yet, results will be empty.
  • The testrun_id may be from a different project than what the token can access
  • Provide the projectId of the project that holds the run. Project names are not accepted
  • Use list_testruns first to confirm the run exists and get its exact ID
The debug_testcase tool aggregates historical execution data. If the test case has only run once or has no recorded failures, there is not enough data for root cause analysis.Run the test case across multiple runs to build a failure history before using debug_testcase.

Network Errors

The MCP server cannot reach TestDino APIs.
  1. Check internet connectivity:
  1. If behind a corporate firewall or VPN, ensure outbound HTTPS (port 443) to *.testdino.com is allowed
  2. Check the Network Endpoints page for the full list of domains to allowlist
Reduce query scope:
  • Lower limit values
  • Avoid rapid sequential calls. Add short delays between queries.
If rate limiting persists, contact support@testdino.com.

Still Stuck?

Discord

Join the community for real-time help

Email Support

Last modified on November 12, 2026