User feedback for SaaS builders
User feedback. Connected to your workflow.
Collect bug reports and feature requests without building the backend. Send them to your existing tools with webhooks, or let your coding agent read them over MCP. Keep working where you already work.
Free during development · No credit card
Add Noonmark to my app: noonmark.dev/SKILL.mdPaste it into Claude Code, Cursor, or whatever writes your code. The brief at that URL is plain markdown.
how it works
From a user report to your next step.
Noonmark collects and validates the feedback. You decide where it goes and how your team acts on it.
Keep your existing feedback UI. Send a bug report, feature request or other feedback to Noonmark with one JSON request.
Illustrative workflow. Connect your own destination using the webhook guide or MCP setup.
Product feedback
frm_3c9e1f07a2b84d6e5f10c8a4
- ana@acme.comExport ignores the active filterbugacceptednow
- j.roe@kite.appCheckout returns 500 on Safari 18bugaccepted2m
- sam@lumen.devAdd CSV column mapping to the importerfeature19m
- mia@northbeam.ioHow do I rotate a Form's key?question1h
- dev@pixel.coWebhook retries fire twice after a 502bugaccepted3h
setup
Let your coding agent wire it in.
Create a form in Studio, then give your agent noonmark.dev/SKILL.md. It uses the brief to connect your feedback UI and configure the webhook route you need. You review the changes before using them.
01
Paste one line
Into Claude Code, Cursor, or whatever writes your code. It fetches the brief from the URL.
02
Review the integration
Your agent connects your app to Noonmark. Review the request, error handling and any webhook changes in your repo.
03
Send a test report
Check it arrived in Studio, then verify the webhook or MCP connection you will use in your workflow.
mcp
Bring feedback into your coding session.
Connect Claude Code, Cursor or another MCP client. Ask what users reported, retrieve the details and use that context while you work in your repo.
Connect your existing agent
Create a workspace token in Studio and add Noonmark to your MCP client. Choose read-only access or enable the supported write tools.
Ask about incoming feedback
Your agent can search reports and read their context. The example below uses sample data; you decide which issue to investigate next.
your tools
Your workflow chooses the destination.
Use Noonmark to collect feedback, inspect it and make it available to the rest of your stack. Connect the tools where your team already plans and ships.
Receive feedback in your own tools
Signed webhooks deliver new submissions to your endpoint. Use your own integration to create tickets, send notifications or run the automations your team already relies on.
Set up webhooksChoose what goes downstream
The optional Gate checks feedback against your rules. Deliver reports that pass to your webhook and inspect the evaluation and delivery results in Studio.
Explore the GateKeep your app’s feedback UI
Collect bug reports and feature requests from your existing screen with a JSON request. Hosted surveys, contact forms and sign-ups are also available when you need them.
See how to send feedbackFree during development.
Start collecting feedback with no credit card. There is no billing and plan limits are not enforced today.
Start freeAvailable today
- Feedback collection, validation and Studio
- Signed webhooks and optional feedback rules
- MCP access for your coding agent
- Hosted surveys and optional integrations
Optional auto classification and AI field drafts need your OpenAI key. Paid plans and future limits are still being developed.
faq
Before you connect it.
What is the path to my first Submission?
Create a free Workspace, choose a Form template, send a response, and read it in Studio. Survey Forms include a public page you can share. For feedback from your own app, send a JSON request with the Fields your Form requires. The Feedback Template requires an email and message; a Blank Form accepts any object. See the collection guide.
Does Noonmark replace my issue tracker?
Noonmark collects feedback and gives you a place to inspect submissions and delivery results. Your existing tools remain where you plan and complete the work. Connect them through your own webhook integration or let your coding agent read feedback through MCP.
Can I keep my existing feedback UI?
Yes. Send a JSON request from your app, CLI or script; Noonmark validates and stores the submission. Hosted pages are also available for surveys. See the collection guide.
Do I need a coding agent?
No. Your agent can use the setup brief as a shortcut, or you can integrate directly using the docs. No SDK is required.
What can my agent do through MCP?
Read and search forms and submissions with a read-only token. With read and write access, it can also submit feedback, update a submission’s status, tick its checks, re-run the Gate, resend a webhook delivery and create forms. You control the token permissions. See MCP setup.
Do I need an OpenAI key?
Collection, webhooks and MCP do not need an OpenAI key. Optional auto classification and AI field drafts use your key. The Gate can use local rules or your own endpoint; OpenAI is optional there. See AI options.
How reliable are webhook deliveries?
Webhooks are signed and delivery results are visible in Studio. Failed deliveries are retried up to three attempts. Delivery is currently best effort, with no durable queue. Read the delivery and signature details before connecting a critical workflow.
What does it cost?
Noonmark is free during development, with no credit card or billing today. Plan limits are not currently enforced. Paid plans and future limits are still being developed.