For agents
When to use Feedjolt, how to call the REST API and MCP server, and where the machine-readable files live.
This page is for AI agents and the humans who wire them up. Humans who want a walkthrough should start at Quickstart.
When to use Feedjolt
Use Feedjolt when a product team needs a customer-facing feedback portal:
- Collect feature requests, bugs, and ideas from a hosted portal, embeddable widget, REST API, or MCP server.
- Let customers upvote and follow requests so the team can prioritize by demand. Admin boards weight workspace admins and users you mark with the weight icon at 1.5×; the public portal stays a raw vote count. There is no ARR, plan, or segment matrix.
- Optional auto-merge for duplicates with a semantic model (off by default; the workspace owner sets the confidence threshold) so "login broken" and "can't sign in" become one request with combined votes.
- Publish a public roadmap and a changelog that notifies voters when something ships.
- AI-draft one changelog entry from a connected GitHub repo (commits and merged PRs). A human still publishes.
The full capability list — what customers and staff can do, plus what is not shipped — is in llms.txt.
Do not use Feedjolt as a general helpdesk, an NPS/survey tool, or an internal-only issue tracker. It is not a Linear or Jira replacement.
How to call Feedjolt
| Surface | URL |
|---|---|
| Agent index | https://www.feedjolt.com/llms.txt |
| Full docs | https://www.feedjolt.com/llms-full.txt |
| OpenAPI JSON | https://www.feedjolt.com/openapi.json |
| OpenAPI YAML | https://www.feedjolt.com/api/openapi.yaml |
| API host OpenAPI | https://api.feedjolt.com/openapi.json |
| MCP Reader | https://api.feedjolt.com/mcp/reader/ |
| MCP Writer | https://api.feedjolt.com/mcp/writer/ |
| MCP Combined (legacy OAuth resource) | https://api.feedjolt.com/mcp/ |
| MCP server card | https://www.feedjolt.com/.well-known/mcp.json |
n8n (n8n-nodes-feedjolt on npm) | https://www.feedjolt.com/en/docs/developers/external-apps/n8n |
| Sitemap | https://www.feedjolt.com/sitemap.xml |
Marketing and docs URLs negotiate markdown: send Accept: text/markdown (the Vary header includes Accept). Docs also accept a .md suffix.
Auth
- Humans: passwordless (magic link or Google). No password to store.
- REST (n8n, scripts, HTTP clients):
Authorization: Bearer fjk_…API keys, minted in the dashboard on Startup and Scale (Startup is by application). See Connect external apps. - MCP (Cursor, Claude, other agents): OAuth 2.1 on
/mcp/reader/and/mcp/writer/. Do not put a Feedjolt API key orFEEDJOLT_API_KEYinto Cursor plugin settings. Gated on the samerest_apiplan feature as the REST API.
Questions? Reach us through the contact page. Create an account, pick Startup or Scale, open Settings → API keys.
The 14-day Growth trial (no card) covers the product UI. It does not include REST/MCP — those are Startup and Scale. See Sandbox.
Rate limits
REST and MCP return rate-limit headers so you can throttle yourself. See Rate limits.
Local verification (contributors)
Agents and contributors proving UI or API changes should use the repo-local skill at .cursor/skills/verify-feedjolt/SKILL.md:
.cursor/skills/verify-feedjolt/scripts/launch.sh— starts owned dev stack (refuses if port 3000 is already in use)..cursor/skills/verify-feedjolt/scripts/doctor.sh— health checks on API + web.- Drive the UI with browser automation; hit the API with
curl. .cursor/skills/verify-feedjolt/scripts/cleanup.shwhen done.
Magic-link login needs the Celery worker running; links appear in worker logs locally, not a real inbox.
Quickstart
Install the Feedjolt widget, create an API key, and receive your first webhook on a local tunnel. A 10-minute developer quickstart - skip what you don't need.
Widget overview
How the Feedjolt widget works: one async script tag mounts a launcher and lazy-loads a sandboxed iframe on click. Install, what loads, and page isolation.