Troubleshooting

Troubleshooting covers installation problems, editor integration issues, authentication failures, and general tool-level errors.

1. Installation Issues

• Package not found

  Verify your internet connection and confirm the package is published with: npm view testdino-mcp.

• Command not found

  Ensure npm's global bin directory is included in your system PATH.

• Permission errors

  Use sudo on macOS/Linux when required, or configure npm to use a different prefix.

2. Editor Integration

• Cursor not detecting server

  Check JSON syntax in mcp.json, verify the file path, and restart Cursor.

• Claude Desktop is not detecting the server

  Confirm the config file location, check that Node.js and npx are installed, and restart the app.

• Other MCP-compatible editors

  Point the editor's MCP configuration to the same server command and environment variables. If you need help with a specific editor, contact Discord or support.

3. Authentication Issues

• Missing API key

  Set TESTDINO_API_KEY in your MCP config under env, restart the editor, and retry.

• Invalid or expired token

  Check that your API key or token is correct, not expired, and has the required permissions.

4. Data Lookup Issues

• Run ID not found

  Use list_testruns to confirm the run ID or counter value.

• Test case not found

  Add additional filters such as branch, commit, status, or time interval. Confirm that the test case exists in the selected run.

5. API and Network Errors

• API request failed Check the returned error message for HTTP status codes or rate limits. Verify internet connectivity and token validity.
• Network issues Ensure stable internet access. Without a connection, most tools cannot retrieve data.

If issues persist, reach out to us:

• Discord (opens in a new tab)
• Email: support@testdino.com