MCP Export

Send pinned user stories to a connected tool — once each, never twice.

In User stories · Out — · Cost Free

What it does

Sends user stories from a connected method out to a tool — a Jira issue, a Linear issue — and remembers what already went, so a second run does not create the ticket twice.

⚠ Only pinned stories leave

An unpinned AI story gets a new id every time the method re-runs. Nothing could recognise it afterwards, so every run would file it again as a new ticket. Pinning a story keeps it verbatim across runs — that is what makes it safe to send, and it is also your say-so that it should go.

Stories written or edited by you count as pinned for this purpose: they survive a re-run the same way.

⚠ Why a second run is safe

Every export is written to a ledger keyed by story and target. The database — not the app — enforces one issue per story per target, so even two runs at the same moment cannot produce a duplicate.

If a story was already sent, you see its issue key instead of a second ticket.

Worth knowing

The field mapping is fixed, not generated. Your title becomes the summary, role / want / benefit become the description, acceptance criteria are appended, and MoSCoW priority maps to the tool’s own scale. No model runs at export time — what you see on the card is what is sent.

This block has no output. What leaves does not come back; a receipt is not material for the next method.

When to reach for it

When the stories are settled and the work moves to whoever builds it. Pin the ones that are ready, send them, and keep writing on the canvas — the unpinned ones stay behind until you decide they are done.

Not before that. A backlog filled with drafts costs someone else the effort of sorting them out again.