MCP Troubleshooting
This guide helps resolve common issues with MCP configuration and usage.
Connection issues
Authentication failed
Symptoms:
- Error: “401 Unauthorized"
- "Invalid token” message
- Connection refused by MCP server
Solutions:
-
Verify token format:
Terminal window # Correct format with Bearer prefixAuthorization: Bearer YOUR_PERSONAL_TOKEN# Note: Cursor uses Token prefixAuthorization: Token YOUR_PERSONAL_TOKEN -
Check token validity:
- Navigate to Azion Console
- Verify token is active and not expired
- Ensure token has necessary permissions
-
Test with MCP Inspector:
Terminal window npx @modelcontextprotocol/inspectorConfigure as
streamable-http
with your token to validate connection.
Never share your Personal Token or commit it to version control.
Connection timeout
Symptoms:
- Request times out after 30+ seconds
- No response from MCP server
- ”Network error” messages
Solutions:
-
Check server URL:
- Correct URL:
https://mcp.azion.com
- Ensure no typos in URL
- Correct URL:
-
Test network connectivity:
Terminal window # Test server availabilitycurl -I https://mcp.azion.com -
Try alternative connection:
- Consider using a different network connection
- Check if VPN is interfering
-
Check firewall/proxy settings:
- Ensure HTTPS traffic to mcp.azion.com is allowed
- Verify proxy configuration if applicable
Tools not appearing
No tools listed in assistant
Symptoms:
- Code assistant doesn’t show Azion tools
- ”No tools available” message
- Commands not recognized
Solutions:
-
Verify MCP support:
- Ensure your code assistant version supports MCP
- Update to latest version if needed
-
Check configuration syntax:
Claude Code
Terminal window claude mcp list # Should show azion-mcpCursor
Verify JSON syntax in settings is validWindsurf
Check.codeium/windsurf/mcp_config.json
exists and is valid JSON -
Restart the assistant:
- Close and reopen the application
- For Claude Code:
claude serve --restart
Tool execution errors
”Tool not found” error
Symptoms:
- Specific tool names not recognized
- ”Unknown tool” errors
Solutions:
-
Verify tool name: Correct tool names:
search_azion_docs_and_site
search_azion_code_samples
search_azion_cli_commands
search_azion_api_v3_commands
search_azion_api_v4_commands
search_azion_terraform
create_rules_engine
create_graphql_query
deploy_azion_static_site
-
Check API profile:
- v3 profiles may have limited tool access
- Consider upgrading to v4 profile
Empty or incomplete responses
Symptoms:
- Tools return no results
- Partial responses
- Generic answers instead of Azion-specific information
Solutions:
-
Refine your query:
❌ "Help with cache"✅ "How do I configure cache TTL for images in Azion?" -
Use specific tool hints:
"Search Azion docs for Rules Engine cache configuration" -
Break complex requests:
- Split multi-part questions
- Ask for clarification if needed
Configuration file issues
JSON parsing errors
Symptoms:
- “Invalid JSON” errors
- Configuration not loaded
Solutions:
-
Validate JSON syntax:
Terminal window # Use a JSON validatorcat mcp_config.json | python -m json.tool -
Common JSON issues:
- Missing commas between properties
- Trailing commas (not allowed in JSON)
- Incorrect quote types (must use double quotes)
- Unclosed brackets or braces
-
Example valid configuration:
{"mcpServers": {"azion": {"command": "npx","args": ["mcp-remote","https://mcp.azion.com","--header","Authorization: Bearer YOUR_TOKEN"]}}}
Node.js related issues
npx command not found
Symptoms:
- “npx: command not found"
- "Node.js is required”
Solutions:
-
Install Node.js:
Terminal window # Check if installednode --versionnpm --version# Install via package manager# macOSbrew install node# Ubuntu/Debiansudo apt install nodejs npm -
Update npm:
Terminal window npm install -g npm@latest
mcp-remote package issues
Symptoms:
- “Cannot find module ‘mcp-remote‘“
- Package installation fails
Solutions:
-
Clear npm cache:
Terminal window npm cache clean --force -
Install globally:
Terminal window npm install -g mcp-remote -
Use specific version:
Terminal window npx mcp-remote@latest
Performance issues
Slow response times
Solutions:
-
Optimize connection:
- Ensure stable network connection
- Minimize concurrent requests
-
Optimize queries:
- Be specific in requests
- Avoid overly broad searches
-
Check network latency:
Terminal window ping mcp.azion.com
Getting help
If issues persist after trying these solutions:
-
Contact support:
- Include error messages
- Specify code assistant and version
- Provide configuration (without tokens)
- Describe steps to reproduce
-
Community resources: