Debug Mode
Enable verbose logging with the--debug flag:
Using MCP Inspector
The MCP Inspector provides a visual interface for debugging your MCP server.1
First, build the server:
2
Run with the MCP Inspector:
3
Open the inspector in your browser at `http://localhost:6274`
ECHO is off.
Docker Debugging
For Docker-based debugging:1
Build the Docker image:
2
Run with MCP Inspector:
Health Check
- Verify your configuration with a simple health check:
- If the server starts successfully, you will see:
- You can also check the version:
Troubleshooting
Some of the common issues and solutions are stated below.Invalid API Key
Invalid API Key
Possible Causes
- Incorrect format
- Expired key
- Key not set properly Solutions
- Ensure key starts with
sk_siren_,sk_test_, orsk_live_ - Check your environment variables or CLI argument
- Generate a new API key from the Siren dashboard if needed
Tool Not Found
Tool Not Found
Possible Causes
- Typo in tool name
- Tool not enabled
- Outdated MCP package Solutions
- Verify tool name (case-sensitive)
- Add the tool to the
--toolslist in the command - Update to the latest MCP version
Connection Issues
Connection Issues
Possible Causes
- Network problems
- Firewall blocking
- API endpoint down Solutions
- Check your internet connection
- Configure firewall exceptions for outbound calls
- Verify Siren API availability at status.trysiren.io
Permission Denied
Permission Denied
Possible Causes
- Insufficient API key permissions
- Workspace-specific access restrictions Solutions
- Ensure your API key has required scopes
- Check your workspace access level
- Contact Siren Support if the issue persists
Rate Limiting
Rate Limiting
Possible Causes
- Too many requests in a short time
- Plan quota exceeded Solutions
- Implement retry logic or request throttling
- Upgrade your Siren plan if you are consistently hitting limits