The Siren Model Context Protocol server enables seamless integration with Siren APIs through function calling. This protocol provides a comprehensive suite of tools for interacting with Siren’s messaging, templates, users, workflows, and webhooks systems.

What is MCP?

Model Context Protocol (MCP) is a framework that allows external systems to pass structured, real-time information to large language models (LLMs) like GPT during each interaction. It bridges the gap between stateless systems such as REST APIs or command-line tools and the varying contextual needs of modern applications. By supplying this additional context, MCP enables the model to produce more accurate, relevant, and consistent responses. At a technical level, MCP works by attaching a structured JSON payload to the user’s prompt at runtime. This payload carries background details such as the user’s identity, recent actions, task-specific instructions, or relevant domain knowledge. This is referred to as runtime context — data that helps the model understand the situation in which it’s being used, without needing to ask for that information in the prompt itself. While invisible in the model’s final response, this context directly influences how the model interprets the prompt and generates output.

What is the Siren MCP Server?

When it comes to Siren, the Model Context Protocol (MCP) Server serves as the integration layer that enables LLM-powered environments to interact with the Siren platform using standardized function calls. It acts as a communication bridge, allowing language models to trigger messaging workflows and retrieve delivery insights in real time. Rather than manually composing HTTP requests or managing channel-specific logic, AI agents can call predefined functions like messaging.send, users.add, or workflows.schedule. These are optimized for channels including Email, Slack, SMS, WhatsApp, and others, making it easy to embed messaging actions into intelligent, event-driven workflows. By abstracting the messaging infrastructure behind clean, callable interfaces, the Siren MCP Server allows developers to build smarter, more responsive AI agents that can operate autonomously across user-facing communication channels.

Quick Start

Requirements

Installation

# Install globally
npm install -g @trysiren/mcp

# Or use with npx without installation
npx -y @trysiren/mcp

Basic Usage

To run the Siren MCP server:
# To set up all available tools
npx -y @trysiren/mcp --tools=all --api-key=YOUR_SIREN_API_KEY

# To set up specific tools
npx -y @trysiren/mcp --tools=messaging.send,templates.list,workflows.trigger --api-key=YOUR_SIREN_API_KEY
Important: Replace YOUR_SIREN_API_KEY with your actual Siren API key. You can also set the SIREN_API_KEY environment variable instead.

Available MCP Clients

Siren MCP supports various AI assistants and development environments. Choose your preferred client for setup instructions:

Available Tools

The Siren MCP server provides the following tools for integration:

Messaging Tools

ToolDescription
messaging.sendSend a message to a recipient via a chosen channel
messaging.getStatusGet the status of a sent message
messaging.getRepliesGet replies to a sent message

Template Management Tools

ToolDescription
templates.listList available message templates
templates.createCreate a new message template
templates.updateUpdate an existing message template
templates.deleteDelete a message template
templates.publishPublish a template for use

User Management Tools

ToolDescription
users.addAdd a new user to the system
users.updateUpdate an existing user
users.deleteDelete a user

Workflow Tools

ToolDescription
workflows.triggerTrigger a workflow execution
workflows.triggerBulkTrigger multiple workflow executions
workflows.scheduleSchedule a workflow for future execution

Webhook Configuration Tools

ToolDescription
webhooks.configureNotificationConfigure notification webhooks
webhooks.configureInboundConfigure inbound webhooks

Tool Categories

For convenience, you can use predefined tool categories in your configuration:
CategoryIncluded ToolsUsage Example
communicationmessaging.send, messaging.getStatus, messaging.getReplies--tools=communication
contenttemplates.list, templates.create, templates.update, templates.delete, templates.publish--tools=content
identityusers.add, users.update, users.delete--tools=identity
automationworkflows.trigger, workflows.triggerBulk, workflows.schedule--tools=automation
integrationwebhooks.configureNotification, webhooks.configureInbound--tools=integration
You can combine categories with specific tools:
npx @trysiren/mcp --tools=communication,templates.create,automation --api-key=YOUR_API_KEY

Configuration Options

Command Line Arguments

ArgumentDescriptionDefaultExample
--toolsComma-separated list of tools to enablenone--tools=messaging.send,templates.list
--api-keyYour Siren API keynone--api-key=sk_siren_...
--workspaceSiren workspace IDDefault workspace--workspace=ws_abc123
--portPort for HTTP server mode3000--port=8080
--debugEnable debug loggingfalse--debug

API Key Format

Siren supports multiple API key formats:
FormatDescriptionUse Case
sk_siren_...Standard Siren API keyGeneral purpose
sk_test_...Test environment keyDevelopment and testing
sk_live_...Production environment keyProduction systems

Workspace Configuration

If you’re working with multiple Siren workspaces, specify the workspace ID:
npx @trysiren/mcp --tools=all --api-key=YOUR_API_KEY --workspace=ws_your_workspace_id

Environment Variables

You can set environment variables instead of passing API keys as arguments:
# API key
export SIREN_API_KEY=sk_siren_your_api_key

# Workspace ID (optional)
export SIREN_WORKSPACE=ws_your_workspace_id

# Run with environment variables
npx @trysiren/mcp --tools=all

Getting Started with Siren MCP Server Integrations

To get started with the Siren MCP server, you’ll need an API key to authenticate your access. If you’ve already signed up, you may have received this key during onboarding. Otherwise, you can generate one from the Siren Dashboard under Settings > Configuration > API Keys. Once you have the API key, you can configure the Siren MCP server within any AI application that supports the Model Context Protocol (MCP). While we’ve included integration examples for specific tools, the same approach applies to any MCP-compatible environment.

Available Platform Integrations

Siren MCP is compatible with a variety of platforms and development environments. Here are the currently supported integrations:
  • Claude Desktop - Set up Siren MCP with Claude’s desktop application
  • VS Code - Configure Siren MCP in your VS Code environment
  • Cursor - Integrate Siren MCP with the Cursor editor
  • Amazon Q CLI - Use Siren MCP with Amazon Q command-line interface
  • Other MCP Clients - Configuration examples for additional MCP-compatible platforms
Each integration guide provides specific instructions for setting up and using Siren MCP within that environment. The core functionality remains consistent across platforms, but the configuration steps may vary slightly.