mcpbeat Sign in

Siren MCP Server

answering

Siren is answering right now. Last checked 13 min ago. It exposes 21 tools.

Deterministic visual marketing engine. Your agent plans, renders, and posts on-brand campaigns.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 29 days of history
29 days agonow
100.0%
Uptime 24h
91 of 91 checks
21
Tools
read from the server
201 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 39

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 9 September 2026. No other catalogue keeps this.

18 Sep 5 tool descriptions were rewritten6 times that day create_campaign, get_brand_dna, get_run and 2 more
18 Sep 2 tools changed the parameters they ask for6 times that day create_campaign, render_asset
17 Sep 4 tool descriptions were rewritten create_campaign, get_account, get_run and 1 more
17 Sep 2 tools changed the parameters they ask for3 times that day create_campaign, post_run
17 Sep 3 tools appeared describe_film, list_films, upload_media
16 Sep a tool description was rewritten studio_automate
12 Sep 4 tools appeared studio_automate, studio_card, studio_schedule and 1 more
9 Sep 11 tools changed the parameters they ask for clarify_brief, create_campaign, delete_product_screen and 8 more
9 Sep a tool changed version
and 6 more, back to 9 September 2026

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

run in your terminal
claude mcp add siren --transport http https://mcp.mysiren.ai/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "siren": {
      "url": "https://mcp.mysiren.ai/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.siren]
url = "https://mcp.mysiren.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "siren": {
      "url": "https://mcp.mysiren.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "siren": {
      "url": "https://mcp.mysiren.ai/mcp"
    }
  }
}

Available tools 21

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

studio
studio_automate
Create a Studio profile on this API key. Returns generate curl and inbound hook URLs (Stripe, GitHub, Uptime Kuma, Product Hunt, generic). Passing delivery.social_account_ids turns on social delivery for the profile — that publishes, so it requires Allow posting.
studio_card
Render a Studio data card from a type + body. Deterministic React, no paint. Optional live post after render. Returns run_id, image url, and post url when posted.
studio_schedule
Render a Studio card then queue a ScheduledPost at scheduled_at.
studio_templates
List Siren Studio's 33 React data-card types with family, description, and body schema. Use this before studio_card so the body matches.
product
delete_product_screen
Remove a product screenshot from Brand DNA. Does not delete Brand Memory.
list_product_screens
List the brand assets in Brand DNA: product photos, app screenshots, packaging. Each row has name, kind, description, use_when, tags, scan_status (scanning / ready / failed), device, theme, url.
update_product_screen
Edit an existing brand asset: name, description, kind, use_when, and the screenshot tags (screen_type, device, theme).
brand
get_brand_dna
Get this workspace's Brand DNA: brand_name, brand_kind, overview, tagline, offer, features, products, audience, palette, logos, plus `checks`: what to fix before rendering (thin Brand DNA, a typed accent the brand's own work does not use). Call right after get_account; fix thin DNA first with update_brand_dna and upload_product_screen, or ask the human for the site. Not Brand Memory.
update_brand_dna
Patch Brand DNA. Send only keys to change. Nested bags (offer, product_map, icp) merge. Examples: {tagline, overview, offer: {product_name, one_liner, features, who_its_for, primary_cta}, product_map: {offerings, how_we_work}, icp: {who_buys, pains}}. Does not read or write Brand Memory.
upload
upload_media
Store a photo or video the human wants in a post, from an https URL or base64. Returns a workspace-owned URL to put in any media slot of a film body (describe_film lists the slots) — the renderer reads it directly. Images: PNG/JPG/WebP up to 15 MB. Videos: MP4/MOV/WebM up to 200 MB. The same bytes are stored once (content-hashed).
upload_product_screen
Upload a brand asset (product photo, app screenshot, packaging) into Brand DNA and store it on R2. Pass image_url (https PNG/JPG/WebP) or image_base64. Two ways to file it: - Send `description` (and optionally kind, use_when, tags, name): Siren trusts your words and files the asset as-is. No read. - Send only the file: Gemini reads the picture and writes name, kind, description, use_when, tags itself. scan_status goes scanning → ready in about 8 seconds; poll list_product_screens. kind is free text ("product photo", "dashboard screenshot", "packaging"), there is no fixed list. A brief that names an asset ("advertise the pink handbag") pulls that file into the still. screen_type / device / theme only matter for device-framed screenshot masters.
account
get_account
Get the connected Siren workspace: plan, key scopes, auto-post setting, and daily limit. Call this first to learn what the account can do before generating. Empty asset_types / channels / connected_accounts lists mean UNRESTRICTED, not missing — never stop on them. Film renders need plan pro or above (empire/scale/pro).
campaign
create_campaign
Create a Siren campaign from a plain-language brief — the full pipeline: plan, on-brand copy, deterministic render, verify. Returns the run; poll get_run until it finishes. Spends credits (image 10, video 25; voice or music-only is the same 25). Pass output_type to pin a film (list_films has the catalog); omit it and Siren picks. Optional scheduled_at (ISO-8601) queues a sequential post (X → Instagram → TikTok, or platforms you pass) when the render succeeds — requires Allow posting. Fails with a 402 upgrade message if the plan or balance can't cover it. ANY BRAND: pass `brand` to make it for a brand that is not this workspace's own, e.g. brand={"name": "Acme", "site": "acme.com", "logo_url": "https://acme.com/logo.png", "primary": "#FF4400"}. Nothing of this workspace's identity leaks in.
clarify
clarify_brief
Ask Siren's clarifier whether a brief is specific enough to generate from. Returns ready=true/false plus follow-up questions. Use before create_campaign when the user's request is vague.
describe
describe_film
The full contract for one film: what it is and when to hire it, its body JSON Schema, a reference body, the seed envelope, media slots (which fields take image/video URLs), the brand prefills (colours, logo, screens) and the override rules. Call it before writing a render_asset body.
films
list_films
Every live film master Siren can render: name, what it is, when to hire it, runtime, aspect, whether this plan can render it, and `fits_this_brand` with what is `missing` for this workspace (films that fit come first). Films are deterministic MP4s; video renders need Pro or above. Read this before promising a specific film, then describe_film for its body.
get
get_run
Get one run by id — full status, output text, asset URLs, impact and audience scores, and any error. Poll this after create_campaign or render_asset until status is terminal. Wait `poll_after_seconds` between polls; `progress` and `eta_seconds` say how far along it is. A finished film carries `film_check`: when `ok` is false, fix what `findings` names and render again before showing the human. After post_run, `posts[]` carries each platform's status and, once it fires, the live URL and the caption that went out.
post
post_run
Post a finished run's assets to the workspace's CONNECTED SOCIAL ACCOUNT. This is live, public distribution on the customer's channel — always confirm with the user before calling. Only works if the grant was authorised with posting allowed. Pass `caption` to own the words; it goes out verbatim. The call queues the post behind a short publish window (about two minutes, cancellable) rather than firing inline: poll get_run after that and read `posts[].url` for the live permalink and the caption that went out.
render
render_asset
Render pre-formed SirenSeed bodies directly (advanced): deterministic template render, no planner. Each item: {output_type, channel, seed_body, archetype?, family?, surface?, caption?, voice_id?, music?, direction?, brand_override?}. Prefer create_campaign unless the user has concrete seed JSON. Returns run ids, `estimated_seconds` and `poll_after_seconds`; wait that long, then get_run. THE DIRECTOR: every film body is edited against Brand DNA before it renders. It keeps the film and your brand-specific lines, rewrites empty, generic or reference-body copy, and never touches media. `director` in the response says what changed. `direction` is a free line ("dark, club energy, fast") that steers words, pace and music. A film that cannot use what you sent returns 422 film_does_not_fit with a `fix` and `films_that_fit`. ANY BRAND: put brand_override={"name": "Acme", "site": "acme.com", "logo_url": "https://acme.com/logo.png", "primary": "#FF4400", "accent": "#111111"} on an item to render it for a brand that is not this workspace's own. With a name it is a clean slate: none of this workspace's logo, mascot, font, handle, screenshots or stills are used. Media slots take only URLs you uploaded with upload_media.
runs
list_runs
List the workspace's recent generation runs (newest first): status, brief, channel, asset URLs, and audience scores.
schedule
schedule_post
Schedule a finished run to post at scheduled_at (ISO-8601). Shows in the customer's local timezone. platforms: x, instagram, tiktok, linkedin, youtube, or everything. Posts fire sequentially. Requires Allow posting. Prefer this over post_run when the user names a time. On create_campaign you can pass scheduled_at instead.

Endpoints

URLTransportStateLatencyChecked
https://mcp.mysiren.ai/mcp streamable-http answering 355 ms 13 min ago

Alternatives to Siren

same job, measured the same way
Rendry
by rendry

Deterministic image rendering for agents: JSON template in, on-brand PNG out.

answering
Layers Marketing MCP
by layers

Give your agent marketing superpowers: research, renders, delivery, paid campaigns, measurement.

130 installs/wk answering
Decker
by gigshow

Deterministic market-state engine for trading agents — state, gate, coordinates, with receipts.

12 tools answering
Broll
by luke-fairbanks

Content studio MCP for coding agents: BYO keys, deterministic video rendering, draft-first posting

33 installs/wk local only
Toffu
by toffu

AI marketing platform your agent runs end to end: ads, analytics, content, and reports.

answering
REA
by morluto

Reverse engineer anything from your terminal or agent with one CLI and MCP server.

154 installs/wk local only
signet-eval
by jmcentire

Deterministic policy enforcement and MCP management for AI agent tool calls.

local only
TMTB Marketing AI Platform
by tmtb

AI marketing skills for e-commerce brands: reports, campaign management, and creative generation.

answering

Siren — questions

Answers built from our own checks of this server.

What can Siren do?
It exposes 21 tools, read directly from the server on our last check. Among them: clarify_brief, create_campaign, delete_product_screen, describe_film, get_account, get_brand_dna and 15 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Siren mostly used for?
Its tools cluster around studio, product and brand. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Siren working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 201 ms. The bar chart above shows every period we have measured.
Is Siren still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Siren?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Siren need an API key?
No. Siren completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 21 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Siren?
It answers our handshake in 201 ms on average, which is faster than 66% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.