Troubleshooting

Troubleshooting

Common issues

Authentication Failures

  • Verify your auth tokens are valid.
  • Check that environment variables are properly set and match the expected names:
    • BUGSNAG_AUTH_TOKEN for BugSnag
    • REFLECT_API_TOKEN for Reflect
    • SWAGGER_API_KEY for Swagger
    • QMETRY_API_KEY for QMetry
    • ZEPHYR_API_TOKEN for Zephyr
  • Ensure you have the correct token type (Auth Token vs API Key) for each desired service.

Build and Installation Problems

  • Ensure Node.js is installed and compatible (check requirements in package.json).
  • Verify that npm run build completed successfully and created the dist/index.js file.
  • Check that the path to dist/index.js is correct in your MCP client configuration.

Connection Problems

  • Confirm the MCP server builds and runs locally using the MCP Inspector.
  • Check your MCP client configuration syntax and file paths.
  • Verify that the dist/index.js file exists and is executable.

Npx cache issues for local MCP server

Github issue link - 4108.

There can be issues when npx can cache some of the dependencies and this can result in your MCP server not running correctly. To fix this you will have to clear your local npx cache.

On Unix and Unix-Like systems (macOS and Linux):

On Windows:

After doing the above you can reinstall the MCP server.

Getting help

For additional support and troubleshooting:

  • Visit the GitHub repository for documentation and issues.
  • Check the MCP specification for protocol details.
  • Contact SmartBear support for account-specific issues.
  • Join the community discussions for tips and best practices.