MCP Server
Connect Feedjolt to Claude Desktop, Cursor, Windsurf, and other AI clients via the remote MCP server. Read, triage, and manage your whole roadmap without leaving your editor.
Feedjolt ships a remote MCP (Model Context Protocol) server so you can talk to your roadmap from any MCP-compatible AI client - Claude Desktop, Cursor, Windsurf, and others.
What you can do
37 tools cover the full feedback surface, not just triage:
- Search and read posts, comments, boards, statuses, tags, the roadmap, and the changelog.
- Triage: change post statuses, tag posts, comment, merge and unmerge duplicates.
- Manage the backlog: create, update, and delete posts, boards, tags, and statuses.
- Ship a changelog: draft entries and publish them when they're ready.
- Every write goes through the same audit trail as the dashboard. Webhooks fire as usual.
What a principal can actually call depends on its scopes - see Permissions.
Requirements
- Available on Startup and Scale (not Growth) - same as the REST API.
- Sign in and approve in the browser (OAuth, the default) or use an
fjk_API key. Both work. See OAuth.
Server URL
https://api.feedjolt.com/mcp/The machine-readable server card is at https://www.feedjolt.com/.well-known/mcp.json.
See Setup for client-specific instructions.
API pagination
Paginate Feedjolt API list endpoints with limit and offset. Common pattern, an iterator example, offset caveats on fast-changing data, and the OpenAPI reference.
MCP Setup
Connect Feedjolt to Claude Desktop, Cursor, and Windsurf over MCP. OAuth with a URL is the default; API keys remain a fully supported alternative.