The short version of how Mowa works, who it is for, and how to reach someone when you need help.
🐾What is Mowa?
Mowa helps teams track the prompts their product actually uses, review changes together, and ship improvements without waiting on a file edit every time.
Do I need to move prompts into Mowa first?
No. The point is to meet prompts where they already live. You can scan repositories, add prompts manually, and connect MCP-compatible tools that read the current version directly.
Can non-engineers work on prompts?
Yes. Product, support, operations, and anyone else on the team can read prompts, review them, and suggest improvements without digging through code.
What happens when a prompt changes?
Mowa keeps the tracked version current, and connected tools read what is live right now. That means less copy-paste, fewer stale prompt versions, and less guesswork.
How does MCP fit in?
MCP lets tools like Cursor or Claude read prompt context from Mowa where your team already works. Mowa sits behind the tools instead of forcing everyone into another tab.
Can I add prompts manually?
Yes. The prompt board includes an inline drawer for manual prompts, which is useful for prompts that are not in a connected repo yet or need to be tracked before the next scan.
How do I get help?
Use the contact link on the site or email hello@mowa.dev directly for now.