Connect your spec to your issue tracker
and the AI tools you already use
Approve a card in Manyfast chat, and finalized items become Linear, GitHub, Jira, or monday.com issues. Connect Claude Code, Cursor, ChatGPT, and other tools over MCP so they read the spec when they need it and propose changes back.
Issue trackers on Pro and up. On Starter, MCP can write PRDs only
Claude Code
Build approval delegation from the Manyfast spec.
Found a missing case while building and sent a spec edit.
2 Approvals & delegation › 2.2
Approval delegation
Spec items become issues
Create issues in Linear, GitHub, Jira, or monday.com. The link on each issue takes you back to its spec item.
Always the current spec
Your AI tools read the spec as it is each time they ask. When it changes, there's nothing to export or paste again.
You approve first
Issues get created only once you approve the card in chat. Spec changes from your AI tools wait as proposals until you sign off.
Send finalized features
to your issue tracker
Review the issue drafts in Manyfast chat, approve them, and your spec items become Linear, GitHub, Jira, or monday.com issues. Each issue links back to its spec item, and you can change status, assignees, and labels from chat. Issue trackers connect through Manyfast chat, not MCP, and are available on Pro and up.
Read the spec first,
propose changes as you build
Coding tools like Claude Code and Cursor search and read the spec, including your team's comments, before they build. Decisions made along the way come back as proposed changes and land in the spec once you approve them on the web or in the tool.
MCP connection: PRDs only on Starter, all features on Pro and Team
Works with the AI tools you rely on
Each tool has a setup guide. Any tool that supports MCP can connect, even if it isn't listed.
- ChatGPT
- Claude
- Codex
- Claude Code
- Antigravity
- Cursor
- Lovable
- Other MCP tools
What AI tools can do over MCP
| Area | What it can do |
|---|---|
| Projects | Create, read, search, rename, and duplicate |
| Spec writing and approval | Write the PRD, requirements, features, specs, and policies, change progress status, and approve proposed changes (PRD only on Starter) |
| User flows and wireframes | Read, generate, regenerate, and make partial edits |
| Sources | Write sources and organize decisions |
| History | Read chat threads, versions, the activity log, and comments |
Spec items written by AI tools stay as proposed changes until you approve them. Issue trackers work through Manyfast chat, not MCP.
How to use it
- Enterprise PM
Send finalized features to Jira or Linear, and engineers open the spec item straight from the link on the issue.
- Dev agency
Skip the separate handoff doc. Your developers' Cursor or Claude Code reads the spec the client signed off on.
- Solo founder
Create a project and draft the PRD from ChatGPT or Claude over MCP, then keep building in Lovable or Cursor.
- Developer
Read features and dev-readiness slots without leaving your IDE. Anything that changes while you build goes back to the spec as a proposal.
Bring your spec into the tools your team works in
Get 5,000 credits when you sign up, plus 3,000 credits every day.
Plan up to 3 projects for free.

