MCP server

Every account has an MCP server that speaks Streamable HTTP. Agents connected to it can list, create, edit, validate and run workflows, inspect runs and test JavaScript — the same tools Murmurator's own assistant uses — and administer the account itself: billing, the team, AI models and connections.

Server URL: https://murmurator.rubyup.dev/mcp.

Get a token

Open MCP & API tokens in your account and create one. Tokens act as you, with your role, in that one account. They're shown once; revoke them at any time.

An agent can also get its own token without visiting the website. Point it at /mcp with no Authorization header and it sees two tools:

Tool	What it does
sign_up	Create a user and an account, and return a token for them
sign_in	Trade an existing email address and password for a token

Both return an api_token. From then on the agent sends it as a bearer token on the same URL and gets the full tool set. Accounts created this way start on the same free trial as any other, with no card required. Anonymous requests are rate limited per IP address.

sign_up without a password leaves the user without a website login; they can set one with Forgot password.

Connect a client

{
  "mcpServers": {
    "murmurator": {
      "type": "http",
      "url": "https://murmurator.rubyup.dev/mcp",
      "headers": { "Authorization": "Bearer mur_…" }
    }
  }
}

With Claude Code:

claude mcp add --transport http murmurator https://murmurator.rubyup.dev/mcp \
  --header "Authorization: Bearer mur_…"

Tools

Workflows

Tool	What it does
get_reference	The full workflow definition reference
list_workflows, get_workflow	Browse workflows and read definitions
list_connections, list_models	See available tools and models
validate_definition	Check a definition without saving
create_workflow, update_workflow	Save new versions (with optimistic base_version checks)
set_workflow_enabled	Turn triggers on or off
run_workflow, list_runs, get_run	Execute workflows and inspect results
test_javascript	Run code in the same sandbox as javascript steps

The account

Tool	What it does
get_account	The account, your role in it, and what's set up
list_accounts, create_account	Your accounts, and new ones you own
list_api_tokens, create_api_token, revoke_api_token	Manage your own tokens
list_members, invite_member, set_member_role, remove_member	Manage the team

Billing

Tool	What it does
get_billing	Subscription, trial and Murmurator AI spend
start_subscription	A Stripe Checkout link to finish subscribing
open_billing_portal	A Stripe Customer Portal link for the card, invoices and cancellation
set_ai_spend_limit	The monthly Murmurator AI spend limit (owners)

Checkout and the portal are links, not actions: an agent can't type in card details, so it hands the link to a person and calls get_billing afterwards to confirm.

Setting the account up

Tool	What it does
list_setup_options	Connection kinds, the credential fields of the kinds you ask about, and the AI models on offer
add_ai_model, set_default_ai_model, remove_ai_model	Built-in models, or your own provider keys
create_connection, update_connection, verify_connection, delete_connection	Wire up GitHub, Slack, Stripe, Zendesk, databases, email and every other connection

Connections marked Expose tools over MCP also contribute their own tools, e.g. warehouse__query.

Every tool checks the same permissions as the equivalent page: owners and admins manage connections, models and the team, and only owners touch billing.

An agent starting from nothing

1. sign_up → keep the api_token, send it as a bearer token from here on.
2. list_setup_options → add_ai_model and create_connection.
3. get_reference → validate_definition → create_workflow → set_workflow_enabled.
4. run_workflow and get_run to check it works.
5. start_subscription before the trial runs out, and pass the link to a person.