Mutator

Official16 tools

by mutator

Build and test short-form marketing automations from your agent. Nothing it does can post.

app.mutator/mutator MCP Server

This MCP server is named app.mutator/mutator and is described as enabling the building and testing of short-form marketing automations from an agent. The description also states a posting restriction: nothing it does can post.

🛠️ Key Features

Build and test short-form marketing automations from your agent
Posting is disabled (“Nothing it does can post”)

🚀 Use Cases

Developing short-form marketing automation logic via an agent workflow
Verifying behavior of automation runs without publishing/posting

⚡ Developer Benefits

Supports agent-driven creation and testing for short-form marketing automations
Clear constraint that prevents posting side effects

⚠️ Limitations

Cannot post; the server’s actions are restricted from publishing

Captured live from the server via tools/list.

mutator_whoami

Confirm the API key works and report which Mutator workspace it reaches and what it may do. Call this first when the connection is new or a later call fails with an authorization error.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

mutator_list_automations

List every automation in the workspace with its id, name and status (draft, active or paused). Start here when the user refers to an automation by name and you need its id.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

mutator_get_automation

Read one automation in detail: status, its schedule if it has one, and its own spending limits. Use it before starting a run to check the automation is active and what a run may cost.

Parameters1

automationId

string

required

Automation id from mutator_list_automations.

Raw schema

{
  "type": "object",
  "properties": {
    "automationId": {
      "type": "string",
      "description": "Automation id from mutator_list_automations."
    }
  },
  "required": [
    "automationId"
  ],
  "additionalProperties": false
}

mutator_list_runs

List recent runs of one automation, newest first, with status, whether each was a dry run, and what it cost. Use it to answer 'did it work' and 'what did it cost'.

Parameters2

automationId	string	required	Automation id from mutator_list_automations.
limit	integer	optional	How many runs to return. Defaults to 10.

Raw schema

{
  "type": "object",
  "properties": {
    "automationId": {
      "type": "string",
      "description": "Automation id from mutator_list_automations."
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 50,
      "description": "How many runs to return. Defaults to 10."
    }
  },
  "required": [
    "automationId"
  ],
  "additionalProperties": false
}

mutator_get_run

Read one run with its per-step detail, so a failure can be traced to the step that caused it. Runs are asynchronous: a run still marked running has not finished, so poll rather than assume.

Parameters1

runId

string

required

Run id, as returned by mutator_start_run.

Raw schema

{
  "type": "object",
  "properties": {
    "runId": {
      "type": "string",
      "description": "Run id, as returned by mutator_start_run."
    }
  },
  "required": [
    "runId"
  ],
  "additionalProperties": false
}

mutator_list_approvals

Always empty. Approvals were removed on 20 September 2026: a run publishes nothing, and a post is made by a person picking a file, an account and a time in Mutator. Tell the person that, rather than reporting an empty queue as if something were wrong. Use mutator_get_run to report what a run made.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

mutator_get_analytics

Read how published content performed over a window of days — the same report the dashboard shows. Use it to answer what worked and to suggest what to run next.

Parameters1

days

integer

optional

Window in days. Defaults to 30.

Raw schema

{
  "type": "object",
  "properties": {
    "days": {
      "type": "integer",
      "minimum": 1,
      "maximum": 365,
      "description": "Window in days. Defaults to 30."
    }
  },
  "additionalProperties": false
}

mutator_get_spend_limits

Report the workspace's daily and monthly spending ceilings and how much of each is already committed. Generation runs on Mutator's own accounts and is paid for in credits, and the ceilings still apply, so check this before starting anything that generates — a run that would pass a ceiling is refused before any provider is contacted.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

mutator_start_run

Start a run of an automation. Defaults to a DRY RUN, which skips publishing but not generation: it makes the same paid generation calls a real run makes, costs the same credits or provider charges, and counts against the same spend limits. So start one only when the user wants a run, and leave it dry unless they have asked for a real run in this conversation. A real run still publishes nothing on its own: anything it generates goes to the workspace's library, and is posted only when a person schedules it in Mutator. Requires an idempotencyKey; replaying the same value returns the original run instead of starting a second one, so retry with the same key rather than a new one.

Parameters3

automationId	string	required	Automation id from mutator_list_automations.
idempotencyKey	string	required	Your own key for this attempt, 8-80 characters. Reuse it verbatim when retrying.
dryRun	boolean	optional	Defaults to true. Pass false only when the user has explicitly asked for a real run.

Raw schema

{
  "type": "object",
  "properties": {
    "automationId": {
      "type": "string",
      "description": "Automation id from mutator_list_automations."
    },
    "idempotencyKey": {
      "type": "string",
      "minLength": 8,
      "maxLength": 80,
      "description": "Your own key for this attempt, 8-80 characters. Reuse it verbatim when retrying."
    },
    "dryRun": {
      "type": "boolean",
      "description": "Defaults to true. Pass false only when the user has explicitly asked for a real run."
    }
  },
  "required": [
    "automationId",
    "idempotencyKey"
  ],
  "additionalProperties": false
}

mutator_list_brands

List the brands in the workspace. Every automation belongs to one, so this is the first call when creating anything: mutator_create_automation needs a brandId from here. The brand carries the voice an automation writes in — audience, tone, call to action.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

mutator_list_connections

List the accounts and providers this workspace has connected, with the id a publishing step needs. A publish step points at a connection, not at a platform name — there is no 'post to TikTok' field, only 'post to this account, which happens to be TikTok'. Read this before wiring one, because a publish step with no connection is refused at activation rather than saved and forgotten.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

mutator_list_formats

The content formats this product actually knows, and the niches they suit. Use one of these when building — do not invent a format. There is no trend, virality or discovery data anywhere in Mutator: nothing here knows what is performing on any platform this week, and a niche only ORDERS this list, it never filters it. If a user asks for 'viral formats in my niche', these are the formats, ordered by fit, and the word viral is not something this tool can stand behind.

Parameters1

niche

string

optional

Optional niche id to order the list by fit. Formats that suit no niche still appear.

Raw schema

{
  "type": "object",
  "properties": {
    "niche": {
      "type": "string",
      "description": "Optional niche id to order the list by fit. Formats that suit no niche still appear."
    }
  },
  "additionalProperties": false
}

mutator_list_step_types

The complete vocabulary of steps, with the settings each one takes. An automation is a graph of these joined by edges. Read this before building one: the step list is closed, and a graph naming a type that is not here is refused. Most settings have defaults, so a step can usually be sent with an empty config and still run.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

mutator_create_automation

Create a new automation as a DRAFT, optionally with its steps already wired. It is never activated and never runs: a draft has no active version, the scheduler only fires active automations, and nothing here can activate one. The person opens it, reads it, and turns it on. An invalid graph is still saved — the problems come back as `issues` for you to fix and save again, rather than the whole call failing. Report what you built and what is left to decide; do not describe it as live.

Parameters4

brandId	string	required	From mutator_list_brands.
name	string	required
description	string	optional
graph	object	optional	Optional. The steps and their connections. Omit to create an empty draft.

Raw schema

{
  "type": "object",
  "properties": {
    "brandId": {
      "type": "string",
      "description": "From mutator_list_brands."
    },
    "name": {
      "type": "string",
      "minLength": 1,
      "maxLength": 120
    },
    "description": {
      "type": "string",
      "maxLength": 600
    },
    "graph": {
      "type": "object",
      "description": "Optional. The steps and their connections. Omit to create an empty draft.",
      "properties": {
        "nodes": {
          "type": "array",
          "items": {
            "type": "object"
          }
        },
        "edges": {
          "type": "array",
          "items": {
            "type": "object"
          }
        }
      },
      "required": [
        "nodes",
        "edges"
      ],
      "additionalProperties": false
    }
  },
  "required": [
    "brandId",
    "name"
  ],
  "additionalProperties": false
}

mutator_save_automation_graph

Replace an automation's steps with the ones given, saved as a DRAFT. An active automation keeps running its current version until a person activates the draft, so editing something live is safe. Problems come back as `issues` rather than failing the call — read them and save a corrected graph.

Parameters2

automationId	string	required	Automation id from mutator_list_automations.
graph	object	required

Raw schema

{
  "type": "object",
  "properties": {
    "automationId": {
      "type": "string",
      "description": "Automation id from mutator_list_automations."
    },
    "graph": {
      "type": "object",
      "properties": {
        "nodes": {
          "type": "array",
          "items": {
            "type": "object"
          }
        },
        "edges": {
          "type": "array",
          "items": {
            "type": "object"
          }
        }
      },
      "required": [
        "nodes",
        "edges"
      ],
      "additionalProperties": false
    }
  },
  "required": [
    "automationId",
    "graph"
  ],
  "additionalProperties": false
}

mutator_set_schedule

Set when an automation would run, saved switched OFF. Turning a schedule on requires an already-active automation, so this can only ever prepare one — the settings survive until a person activates it. A schedule runs an automation AT MOST ONCE A DAY: it holds a single time, and frequency chooses which days rather than how many times within one. Two posts a day is not a schedule setting: it is one daily run producing two items, with maxPostsPerDay on the publishing step.

Parameters5

automationId	string	required	Automation id from mutator_list_automations.
frequency	string	required
timeOfDay	string	required	24-hour local time, "HH:mm".
timezone	string	required	IANA zone, e.g. "America/New_York".
weekdays	array	optional	ISO weekdays, Monday is 1. Used by weekly and custom.

Raw schema

{
  "type": "object",
  "properties": {
    "automationId": {
      "type": "string",
      "description": "Automation id from mutator_list_automations."
    },
    "frequency": {
      "type": "string",
      "enum": [
        "daily",
        "weekdays",
        "weekly",
        "custom"
      ]
    },
    "timeOfDay": {
      "type": "string",
      "description": "24-hour local time, \"HH:mm\"."
    },
    "timezone": {
      "type": "string",
      "description": "IANA zone, e.g. \"America/New_York\"."
    },
    "weekdays": {
      "type": "array",
      "items": {
        "type": "integer",
        "minimum": 1,
        "maximum": 7
      },
      "description": "ISO weekdays, Monday is 1. Used by weekly and custom."
    }
  },
  "required": [
    "automationId",
    "frequency",
    "timeOfDay",
    "timezone"
  ],
  "additionalProperties": false
}

Install

Tools (16)

mutator_whoamimutator_list_automationsmutator_get_automationmutator_list_runsmutator_get_runmutator_list_approvalsmutator_get_analyticsmutator_get_spend_limits

Remote endpoint

Streamable HTTP

Hosted server - connect over the network, no local install.

url

https://mutator.app/mcp

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "mutator": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mutator.app/mcp"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.

app.mutator/mutator MCP Server

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

mutator_whoami

mutator_list_automations

mutator_get_automation

mutator_list_runs

mutator_get_run

mutator_list_approvals

mutator_get_analytics

mutator_get_spend_limits

mutator_start_run

mutator_list_brands

mutator_list_connections

mutator_list_formats

mutator_list_step_types

mutator_create_automation

mutator_save_automation_graph

mutator_set_schedule

Install

Remote endpoint

Related servers