Troubleshoot MCP

MCP Server Not Responding

Symptoms: Commands timeout or show connection errorsFor Cursor:

Check the MCP status icon in the bottom status bar
Make sure that the JSON syntax in ~/.cursor/mcp.json is valid
Make sure that you fully quit and restarted Cursor, not just reloaded it
Check the API token is correct and shows Enabled on API keys
Test connectivity: curl https://mcp.nofire.ai/mcp/health
Look for errors in Cursor’s developer console (Help → Toggle Developer Tools)

For Claude Desktop:

Make sure that the JSON syntax in claude_desktop_config.json is valid
Make sure that the file path is correct for your operating system
Check file permissions (should be readable)
Make sure that the API token shows Enabled on API keys
Check Claude’s developer console for error messages
Try removing and re-adding the configuration

JSON Syntax Errors

Symptoms: MCP servers not loading, IDE shows configuration errorsCommon mistakes:❌ Missing comma between servers:

{
  "mcpServers": {
    "server1": {...}  // Missing comma here!
    "NOFireAI": {...}
  }
}

✅ Correct:

{
  "mcpServers": {
    "server1": {...},
    "NOFireAI": {...}
  }
}

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

API Token Issues

Symptoms: “Invalid API token” or “Unauthorized” errorsChecklist:

Copy the API token correctly (no extra spaces or line breaks)
Make sure that you copied the MCP token, not an ingestion token
Make sure that the token shows Enabled on API keys
Check key has not been deleted or deactivated
Make sure quotes are proper JSON double quotes ""

Test connectivity (no auth needed):

curl https://mcp.nofire.ai/mcp/health

Test your API token:

curl -X POST https://mcp.nofire.ai/mcp \
  -H "Authorization: Bearer your-key-here" \
  -H "Content-Type: application/json"

If the health check works but auth fails, create a new MCP token on API keys.

Configuration File Not Found

Symptoms: Cannot find mcp.json or claude_desktop_config.jsonSolutions:For Cursor: Create the directory and file if they do not exist:

# macOS/Linux
mkdir -p ~/.cursor
touch ~/.cursor/mcp.json
echo '{"mcpServers":{}}' > ~/.cursor/mcp.json

# Windows (PowerShell)
New-Item -Path "$env:APPDATA\.cursor" -ItemType Directory -Force
'{"mcpServers":{}}' | Out-File "$env:APPDATA\.cursor\mcp.json"

For Claude Desktop:

# macOS
mkdir -p ~/Library/Application\ Support/Claude
echo '{"mcpServers":{}}' > ~/Library/Application\ Support/Claude/claude_desktop_config.json

# Linux
mkdir -p ~/.config/Claude
echo '{"mcpServers":{}}' > ~/.config/Claude/claude_desktop_config.json

# Windows (PowerShell)
New-Item -Path "$env:APPDATA\Claude" -ItemType Directory -Force
'{"mcpServers":{}}' | Out-File "$env:APPDATA\Claude\claude_desktop_config.json"

No Services Found

Symptoms: “No entities found” or empty resultsSolutions:

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
Wait for the first data collection, which also builds the production map
If you use the agent, make sure that it has the correct cluster access
Open Connections and check for connections that show Failing

Inaccurate File Mapping

Symptoms: Files mapped to wrong services or not mapped at allSolutions:

Use repository-qualified paths (include repo name)
Make sure that the service names match the deployment labels
Check if service was recently deployed (< 1 hour)
Fuzzy matching requires similar naming between files and services

API Token Permission Denied

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) need an ingestion token from API keys.

Get Started

Production readiness

Change management

Incidents

Always-On Workflows

Analytics

Setup & Integrations

Security

Still stuck

​Still stuck

Still stuck