Skip to main content

​
Using Siren MCP with Amazon Q CLI

Configure Amazon Q CLI to use the Siren MCP server: 
q configure mcp add-server siren \
  --command "npx" \
  --args "-y,@trysiren/mcp,--tools=all,--api-key=YOUR_SIREN_API_KEY"

​
Configuration Options

  • Replace YOUR_SIREN_API_KEY with your actual Siren API key
  • The --tools flag specifies which Siren tools to enable (use all for all available tools)
  • The server will be registered with the name “siren” in your Amazon Q CLI configuration

​
Verifying the Setup

  1. List configured MCP servers: 
    q configure mcp list-servers
  2. Test the connection: 
    q mcp execute siren messaging.send --help

​
Usage Example

Send a test message: 
q mcp execute siren messaging.send \
  --channel email \
  --to user@example.com \
  --subject "Test from Amazon Q CLI" \
  --body "This is a test message sent via Amazon Q CLI"

​
Troubleshooting

  • Ensure Node.js and npm are installed and in your PATH
  • Verify your API key has the necessary permissions
  • Check the Amazon Q CLI logs for any error messages
  • Make sure your network allows connections to the Siren API

​
Security Notes

  • Never hardcode API keys in scripts or command history
  • Consider using environment variables for sensitive information
  • Regularly rotate your API keys for enhanced security

​
Security Best Practices

  • Never commit API keys to version control
  • Use IAM roles and policies for AWS access
  • Set appropriate file permissions on config files
  • Regularly rotate your API keys