Use pmmRush from Claude

1.What it is

pmmRush runs an MCP server, so an AI client can work with your workspace: ask what needs updating now, what a release will make stale, or what is true about a product today, and start the drafts. Answers come from your workspace’s own record and say where they came from. You need a pmmRush workspace to connect.

2.Connect

Claude (web and desktop): open Settings, then Connectors, and add a custom connector with the URL https://www.pmmrush.com/api/mcp. Claude opens pmmRush’s sign-in; sign in with your pmmRush account and allow access.

Claude Code: run claude mcp add --transport http pmmrush https://www.pmmrush.com/api/mcp, then /mcp in Claude Code to sign in.

Other MCP clients: clients that support OAuth sign-in use the same URL. For one that takes a key instead, an admin creates one in pmmRush under Settings and the client sends it as a bearer token.

3.What it can do depends on your role

The connection acts as you, with your role in the workspace you are in now in pmmRush; switch workspace in pmmRush and the connection follows. Everyone can use the read tools. Editors and admins also get the write tools. A connection never approves your messaging, portfolio or collateral: new portfolio entries land as drafts, and redrafts wait for a person in pmmRush unless your workspace lets a surface publish minor redrafts itself. Recording a ship takes effect at once: it adds the item to your roadmap as shipped and marks that product’s surfaces as needing an update. Marking a web page current is an approval, so it needs approval rights.

4.Tools

Read tools:

stale_surfaces

Everything that needs updating now, most urgent first: decks, one-pagers, web pages and messaging, with what made each one stale and where.

asset_shadow

What a roadmap item will make stale when it ships, and who owns each part.

blast_radius

What a change to one product would affect.

whats_new

What shipped and what the approved messaging says, since a date.

ask_ruby

A question answered only from your approved record, with sources.

messaging_diff

Messaging redrafts waiting for a decision, word for word.

autonomy_state

Which surfaces may publish minor redrafts on their own, and why.

positioning_diff

Whether your live homepage still says what your approved positioning says.

rights_exposure

Collateral using an analyst figure past its licence or a customer logo past its consent.

impact_readout

This quarter's numbers from the record: what shipped and what was kept current.

find_unlisted_products

Confirmed products your own website does not mention (it reads your live site).

Write tools (editors and admins):

record_ship

Record something that reached customers as a shipped roadmap item. A recent ship marks that product's messaging and collateral as needing an update and queues redrafts. A dry run first.

stage_updates

Start drafts for chosen stale surfaces. A dry run first.

append_bom_node

Add a product, module or feature to your portfolio as a draft for a person to approve.

mark_page_updated

Mark a stale web page current once the live page matches the approved messaging (needs approval rights).

5.Things to ask

• “What needs updating in pmmRush now?”
• “What will our next release make stale, and who owns each piece?”
• “Does our homepage still say what our approved positioning says?”
• “What shipped since October, and is our collateral up to date with it?”
• “We just shipped team invites. Record it in pmmRush.”

6.Your data

pmmRush receives the tool a client calls and the arguments it sends, not your conversation. Each call is kept in an audit record without your text. The details are in the privacy policy.

7.Troubleshooting

• No write tools: your role in the workspace can only read (a viewer), or the key you use is read-only. An admin can change roles on the Team page.
• A rate-limit error: calls are limited per person (per key for a key), more on paid plans. The error says how long to wait.
• “Not found” for something you can see in pmmRush: the tools read approved records only. Approve it in pmmRush first.
• The wrong workspace: a connection uses the workspace you are in now in pmmRush. Switch in the workspace menu.

8.Help

Email graeme@pmmrush.com. Security reports: security@pmmrush.com.