What is the Murmur MCP server?

A remote MCP server that lets Claude Code and other MCP clients use Murmur. Sign in with your Murmur account, start a run from a typed idea, poll it, and export the PRD, research, brand kit, tech design and roadmap into your repo as a foundation pack.

Which MCP clients work with it?

Claude Code is tested. The server uses OAuth sign-in for remote MCP servers over HTTP, so a client that supports that can add it with the same URL. If yours can't sign in, tell us through the contact page.

Do I need an Atlassian account?

Yes. Murmur needs a free Atlassian account, connected once before your first run. start_run checks the connection before anything runs; without it, the server answers with a link to connect it, creates nothing and uses no idea.

Can I send a voice memo through MCP?

No. MCP runs start from a typed idea of 20 to 600 characters. To talk through an idea instead, record it in the Murmur app; the run and the foundation are the same.

What does a run cost through MCP?

The same as in the app, from the same balance. Your first idea is free, with no card; after that it's $7 per idea, or a monthly plan. An idea is used only when the run delivers, so a failed run doesn't use one. Runs are also rate-limited per account, so a client that starts several in a row may be asked to wait.

What can a connected client do with my account?

The consent screen asks for full access to your Murmur account. Through its tools a client can read your account, runs and foundations, and start runs. None of the tools changes your plan or payment details.

What if I start the same idea twice?

Within 5 minutes, the server returns the run already started for that idea instead of starting another. If that run failed, trying again starts a new one.

Where do the files go?

export_foundation returns the files and your client writes them under foundation/ at your repo root, replacing files with the same names. The server writes nothing to your machine.

How long are runs kept?

Results are kept for 30 days plus a 7-day grace window, then deleted. Export the foundation before then; the Jira project and Confluence space stay in your Atlassian site.

Murmur MCP server

Start a Murmur run from Claude Code, then write the foundation pack into your repo.

The Murmur MCP server lets Claude Code and other MCP clients use Murmur by SprintZero Studios. Sign in once with your Murmur account, then start a run from a typed idea of 20 to 600 characters. Murmur researches competitors, writes the PRD, brand kit, tech design and roadmap, and builds a Jira project and Confluence space in your connected Atlassian site. When the run completes, your client exports the foundation pack into your repo. The four public example runs took 7m 31s to 10m 37s.

Create your account

First idea free · No card

Murmur needs a free Atlassian account, connected once before your first run. Your Jira board and Confluence space are built there.

Terminal

claude mcp add --transport http murmur https://app.trymurmur.studio/api/mcp

Claude Code. In another MCP client, add a remote HTTP server with the same URL.

tools on the server: 6
typed idea accepted by start_run: 20 – 600 characters
files in the foundation pack (manifest + 7 documents): 8
public example run times: 7m 31s – 10m 37s

The tools

Names and inputs as the server registers them. start_run is the only tool that starts anything; the rest read.

Tool
get_account
Input
none
Returns
Balance in ideas, plan, Atlassian connection, links to plans and to connect Atlassian
Changes anything?
No
Tool
start_run
Input
idea (20–600 characters)
Returns
run_id, or why it can't start (Atlassian, balance) with the link to fix it
Changes anything?
Starts a run; one idea is used only when it delivers
Tool
get_run
Input
run_id
Returns
Status (queued, running, completed, failed), current stage, stage timings, failure reason
Changes anything?
No
Tool
list_runs
Input
limit (optional)
Returns
Your runs from every source, newest first
Changes anything?
No
Tool
get_foundation
Input
run_id, kind (optional: prd, competitors, brand, tech, roadmap, transcript)
Returns
A completed run's documents as Markdown, the same text the app downloads
Changes anything?
No
Tool
export_foundation
Input
run_id, target: "repo"
Returns
The foundation pack as files under foundation/ for your client to write
Changes anything?
No (the server writes nothing)

What the server answers

A connected client relays these replies as they come. The text is the server's own, word for word.

When
The run starts
The server answers
Run started. Poll get_run for progress, or follow it here: + link to the run
When
No Atlassian connected
The server answers
Every Murmur run builds a Jira board and Confluence space, so it needs a connected Atlassian site. Connect it, then try again: + link to settings
When
No ideas left
The server answers
You're out of ideas. Pick a plan or top up, then try again: + link to plans
When
The same idea again within 5 minutes, while its run is going
The server answers
That idea was started in the last few minutes and is still running. It's the same run (no new one started). Poll get_run, or follow it here: + link to the run

Atlassian and your balance are checked before anything runs. A refused run uses no idea.

How to connect Murmur to Claude Code

Create your account and connect Atlassian. Your first idea in the Murmur app is free, with no card. Murmur needs a free Atlassian account, connected once before your first run. Connect it under Settings.
Add the server. In Claude Code, run the command above. In another MCP client, add a remote HTTP server with the URL https://app.trymurmur.studio/api/mcp.
Sign in. In Claude Code, run /mcp, then follow the steps in your browser: sign in with your Murmur account and approve the consent screen. If the browser doesn't open, copy the URL Claude Code shows and open it yourself.
Start a run. Ask your client to start a Murmur run with your idea in 20 to 600 characters. It polls get_run until the run completes.
Export the foundation. Ask it to export the foundation. It writes the files under foundation/ at your repo root, overwriting files with the same names.

What lands in your repo

manifest.json: product name, run id, file list, and the Jira and Confluence keys
transcript.md: your idea as Murmur read it
competitors.md: the competitor map with a source link for each
prd.md: features as must / should / could / won't, each with a reason, metrics, risks, open questions
brand.md and brand.tokens.json: name, tagline, colours, type and a logo direction (no logo image)
tech-design.md: the engineering brief
roadmap.md: the Jira board plan, epics and stories by phase

Coding agents can read foundation/ before they build, so the plan, the brand and the backlog travel with the code.

Want an MCP server that writes PRDs into Linear, Notion or Google Docs? See how Murmur compares with ChatPRD.

FAQ

What is the Murmur MCP server?
A remote MCP server that lets Claude Code and other MCP clients use Murmur. Sign in with your Murmur account, start a run from a typed idea, poll it, and export the PRD, research, brand kit, tech design and roadmap into your repo as a foundation pack.
Which MCP clients work with it?
Claude Code is tested. The server uses OAuth sign-in for remote MCP servers over HTTP, so a client that supports that can add it with the same URL. If yours can't sign in, tell us through the contact page.
Do I need an Atlassian account?
Yes. Murmur needs a free Atlassian account, connected once before your first run. start_run checks the connection before anything runs; without it, the server answers with a link to connect it, creates nothing and uses no idea.
Can I send a voice memo through MCP?
No. MCP runs start from a typed idea of 20 to 600 characters. To talk through an idea instead, record it in the Murmur app; the run and the foundation are the same.
What does a run cost through MCP?
The same as in the app, from the same balance. Your first idea is free, with no card; after that it's $7 per idea, or a monthly plan. An idea is used only when the run delivers, so a failed run doesn't use one. Runs are also rate-limited per account, so a client that starts several in a row may be asked to wait.
What can a connected client do with my account?
The consent screen asks for full access to your Murmur account. Through its tools a client can read your account, runs and foundations, and start runs. None of the tools changes your plan or payment details.
What if I start the same idea twice?
Within 5 minutes, the server returns the run already started for that idea instead of starting another. If that run failed, trying again starts a new one.
Where do the files go?
export_foundation returns the files and your client writes them under foundation/ at your repo root, replacing files with the same names. The server writes nothing to your machine.
How long are runs kept?
Results are kept for 30 days plus a 7-day grace window, then deleted. Export the foundation before then; the Jira project and Confluence space stay in your Atlassian site.