Feedock for developers

Feedock has two programmatic surfaces. The MCP server (@feedock/mcp) exposes your workspace to AI agents (Claude, Cursor, Codex, or any MCP client) as tools that drive the whole loop: triage feedback, plan the roadmap, move tasks, and draft changelog entries. The public REST API is the engine behind the hosted portal, the React SDK, and the embeddable widget, and the same endpoints are open for your own integrations.

To put Feedock in front of your users, there are three ready-made surfaces, covered under Integrations below: the hosted portal (zero code), the React SDK (components in your app), and the embeddable widget (one script tag on any site).

Both surfaces are project-bound and public-safe by construction: the MCP server only ever sees sanitized data for the one project its token belongs to, and the REST read models physically cannot carry internal fields. Private items, drafts, emails, and internal notes never leave the API.

The MCP server authenticates with a Personal Access Token (fdk_pat_…). Generate one in Settings → API tokens; it acts as your team member, is revocable at any time, and the full secret is shown once at creation.

The REST API's read endpoints need no authentication. Write endpoints act on behalf of your end users, who stay account-less: they verify once via a magic link (or your app vouches for them over SSO) and receive a short-lived, project-bound visitor token sent as a Bearer header (see Write endpoints below).

The server runs over stdio and is configured entirely by two environment variables: FEEDOCK_API_URL (your API origin) and FEEDOCK_API_TOKEN (the PAT from above).

{
  "mcpServers": {
    "feedock-your-project": {
      "command": "npx",
      "args": ["-y", "@feedock/mcp"],
      "env": {
        "FEEDOCK_API_URL": "https://api.feedock.com",
        "FEEDOCK_API_TOKEN": "fdk_pat_..."
      }
    }
  }
}

claude mcp add feedock-your-project \
  -e FEEDOCK_API_URL=https://api.feedock.com \
  -e FEEDOCK_API_TOKEN=fdk_pat_... \
  -- npx -y @feedock/mcp

Every tool is scoped to the token's project, respects the token holder's role, and returns sanitized, public-safe data. Reads are free-form; writes are marked below, and the two confirm-to-run tools (merge, publish) refuse to act until the agent passes an explicit confirmation. The model drafts; a human approves before anything ships.

The thin REST surface that powers all three public integrations: the hosted portal, the React SDK, and the embeddable widget. Every route hangs off your project's slug; CORS is open, so it's callable straight from the browser:

https://api.feedock.com/public/p/:slug

The zero-code option. Every project gets a hosted public portal at feedock.com/p/your-project with the feedback board, roadmap, updates feed, and any public docs as tabs. Enable it in your project settings and share the link; there is nothing to install.

• Account-less for your users: visitors submit, vote, and comment with just an email, verified once by a magic link.
• Subscribable: a Subscribe button collects update emails with double opt-in, and every email carries one-click unsubscribe.
• Yours to brand: your logo and brand color; on paid plans you can remove the Feedock badge and serve the portal from your own domain, like feedback.yourapp.com.
• SEO-ready: the portal ships its own sitemap and an RSS feed of published updates.

Render the board, roadmap, and changelog inside your own React app with @feedock/react. The components are self-contained (inline styles, no CSS import, no Tailwind dependency) and talk to the public API directly from the browser. Install @feedock/react and wrap the part of your app that shows Feedock:

import { FeedockProvider, FeedbackBoard } from "@feedock/react";

export function FeedbackPage() {
  return (
    <FeedockProvider projectSlug="your-project">
      <FeedbackBoard />
    </FeedockProvider>
  );
}

• Components: FeedbackBoard, Roadmap, Changelog, and LatestUpdate (a dismissible what's-new toast), all inside FeedockProvider.
• Provider props: projectSlug (required), apiBase, theme (brand color, light/dark), and userToken.
• Skip verification for signed-in users: sign a JWT with your project's SSO secret on your backend and pass it as userToken; the SDK exchanges it on mount and your user votes without an email round-trip.
• Headless option: FeedockClient and the useFeedock() hook expose the raw reads and writes if you want your own UI.

For sites that aren't React: one script tag renders a floating launcher that opens a tabbed panel (Feedback, Roadmap, What's New). The widget mounts in a Shadow DOM, so its styles can't leak into your page and your page's styles can't break it. When a new update is published, a small toast invites returning visitors to read it.

<script
  src="https://feedock.com/widget.js"
  data-project="your-project"
  async
></script>

Everything is configured with data-* attributes on the script tag: