Skip to main content

​
Debug Mode

Enable verbose logging with the --debug flag: 
npx @trysiren/mcp --tools=all --api-key=YOUR_API_KEY --debug

​
Using MCP Inspector

The MCP Inspector provides a visual interface for debugging your MCP server.
1

First, build the server:

npm run build
2

Run with the MCP Inspector:

# Start MCP Inspector and server with all tools
npx @modelcontextprotocol/inspector node dist/index.js --tools=all --api-key=YOUR_SIREN_API_KEY
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:

docker build -t trysiren/mcp .
2

Run with MCP Inspector:

docker run -p 3000:3000 -p 5173:5173 -v /var/run/docker.sock:/var/run/docker.sock \
mcp/inspector docker run --rm -i trysiren/mcp --tools=all --api-key=YOUR_SIREN_API_KEY

​
Health Check

  • Verify your configuration with a simple health check: 
    npx @trysiren/mcp --tools=messaging.send --api-key=YOUR_SIREN_API_KEY
  • If the server starts successfully, you will see: 
    ✅ Siren MCP Server running on stdio
  • You can also check the version: 
    npx @trysiren/mcp --version

​
Troubleshooting

Some of the common issues and solutions are stated below.
Possible Causes
  • Incorrect format
  • Expired key
  • Key not set properly Solutions
  • Ensure key starts with sk_siren_, sk_test_, or sk_live_
  • Check your environment variables or CLI argument
  • Generate a new API key from the Siren dashboard if needed
Possible Causes
  • Typo in tool name
  • Tool not enabled
  • Outdated MCP package Solutions
  • Verify tool name (case-sensitive)
  • Add the tool to the --tools list in the command
  • Update to the latest MCP version
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
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
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

​
Examples

​
Basic Messaging

# Configure for basic messaging
npx @siren/mcp --tools=messaging.send,messaging.getStatus --api-key=YOUR_API_KEY

​
Template Management

# Configure for template operations
npx @siren/mcp --tools=templates.list,templates.create,templates.update --api-key=YOUR_API_KEY

​
Workflow Automation

# Configure for workflow automation
npx @siren/mcp --tools=workflows.trigger,workflows.schedule --api-key=YOUR_API_KEY

​
Full Access

# Configure all available tools
npx @siren/mcp --tools=all --api-key=YOUR_API_KEY