Documentation Index
Fetch the complete documentation index at: https://docs.trysiren.io/llms.txt
Use this file to discover all available pages before exploring further.
Using Siren MCP with Other Clients
The Siren MCP server is compatible with any client that supports the Model Context Protocol standard. Here are configuration examples for popular MCP-compatible platforms:5ire Desktop
Configure in 5ire’s MCP settings:FLUJO
Add to FLUJO’s workflow configuration:Zed Editor
Configure in Zed’s assistant settings:3. Custom Implementation
Here’s a basic example of how to implement an MCP client in Python:Authentication
Siren MCP uses API key authentication. Include your API key in theAuthorization header:
Rate Limiting
- Default rate limit: 60 requests per minute
- Response headers include rate limit information:
X-RateLimit-Limit: Maximum requests allowedX-RateLimit-Remaining: Remaining requests in the windowX-RateLimit-Reset: Time when the limit resets (UTC timestamp)
Error Handling
Handle these common HTTP status codes:200 OK: Request successful400 Bad Request: Invalid request parameters401 Unauthorized: Invalid or missing API key403 Forbidden: Insufficient permissions404 Not Found: Resource not found429 Too Many Requests: Rate limit exceeded500 Internal Server Error: Server error
Best Practices
- Error Handling: Implement retry logic for transient failures
- Timeouts: Set appropriate timeouts for API calls
- Logging: Log all API interactions for debugging
- Security: Never expose API keys in client-side code
- Monitoring: Track API usage and error rates