Skip to main content
If you have not set the server up yet, start with Install the MCP server.
Symptoms: Commands timeout or show connection errorsFor Cursor:
  1. Check the MCP status icon in the bottom status bar
  2. Make sure that the JSON syntax in ~/.cursor/mcp.json is valid
  3. Make sure that you fully quit and restarted Cursor, not just reloaded it
  4. Check API token is correct and active in NOFire AI dashboard
  5. Test connectivity: curl https://mcp.nofire.ai/mcp/health
  6. Look for errors in Cursor’s developer console (Help → Toggle Developer Tools)
For Claude Desktop:
  1. Make sure that the JSON syntax in claude_desktop_config.json is valid
  2. Make sure that the file path is correct for your operating system
  3. Check file permissions (should be readable)
  4. Make sure that the API token is active in the dashboard
  5. Check Claude’s developer console for error messages
  6. Try removing and re-adding the configuration
Symptoms: MCP servers not loading, IDE shows configuration errorsCommon mistakes:❌ Missing comma between servers:
✅ Correct:
Check your JSON:
  • Use an online JSON validator
  • Use command line: python3 -m json.tool yourfile.json
  • Most code editors have built-in JSON validation
Symptoms: “Invalid API token” or “Unauthorized” errorsChecklist:
  1. Copy the API token correctly (no extra spaces or line breaks)
  2. Make sure that you copied the MCP key, not the agent key
  3. Make sure that the key is active in the NOFire AI dashboard
  4. Check key has not been deleted or deactivated
  5. Make sure quotes are proper JSON double quotes ""
Test connectivity (no auth needed):
Test your API token:
If the health check works but auth fails, regenerate your API token in the dashboard.
Symptoms: Cannot find mcp.json or claude_desktop_config.jsonSolutions:For Cursor: Create the directory and file if they do not exist:
For Claude Desktop:
Symptoms: “No entities found” or empty resultsSolutions:
  1. Make sure that your data sources are connected:
    • If you use an observability stack: make sure that the Grafana, Prometheus, and Loki connections are active
    • If you use the Kubernetes agent: make sure that the agent is deployed and running
  2. Wait for the first data collection, which also builds the production map
  3. If you use the agent, make sure that it has the correct cluster access
  4. Check connection logs for errors in the NOFire AI dashboard
Symptoms: Files mapped to wrong services or not mapped at allSolutions:
  1. Use repository-qualified paths (include repo name)
  2. Make sure that the service names match the deployment labels
  3. Check if service was recently deployed (< 1 hour)
  4. Fuzzy matching requires similar naming between files and services
Symptoms: “MCP keys are read-only” errorIssue: You are trying to perform a write operation with an MCP keySolution: MCP keys are intentionally read-only for security. Write operations (like creating new services) require agent keys through the dashboard.

​
Still stuck

Email [email protected] with the name of your IDE, the contents of your MCP configuration file with the token removed, and the error your IDE shows.