Canny MCP Server

Canny

Canny collects and prioritizes customer feedback via boards, posts, votes, comments, and changelog entries.

Data Model

• Boards — top-level containers for feedback (e.g. "Feature Requests", "Bugs"). Each has a unique ID, name, URL, and post count.
• Posts — individual feedback items within a board. Have a title, description, vote count, status (open / under review / planned / in progress / complete / closed), author, category, and tags.
• Votes — user endorsements on posts. Track who voted, when, and on which post.
• Comments — threaded discussion on posts. Have text, author, and timestamps.
• Categories — board-level groupings for posts (e.g. "UI", "Performance").
• Tags — cross-cutting labels applied to posts for filtering.
• Companies — organizational accounts linked to users and posts. Track monthly spend and user counts.
• Users — people who interact with the feedback system. Have email, name, vote count.
• Changelog entries — published product updates. Have title, description, labels, and publication date.
• Status changes — audit trail of post status transitions. Track old/new status, timestamp, and who made the change.

Capabilities

Read: List boards, categories, changelog entries, comments, companies, posts, status changes, tags, users, votes. Fetch a single post by ID. Most list-style reads support skip/limit pagination and filtering by boardID.

Common Workflows

1. Feedback triage: List boards to find the right one, then list posts filtered by board and sorted by score or trending to find top-priority items.
2. Post deep-dive: Get a post by ID to see full details, then list comments and votes for that post.
3. Progress tracking: List status changes filtered by board to see what moved from "planned" to "in progress" recently.
4. Company feedback: List companies to identify key accounts, then list posts to see their feature requests.

Gotchas

• Request shapes are uniform: pass the parameters each tool declares—there is no separate “query string vs body” split to manage from here.
• Pagination uses skip (number of items to skip) and limit (max 100). Page forward by increasing skip in fixed steps.
• Post statuses are strings: "open", "under review", "planned", "in progress", "complete", "closed".
• boardID, postID, authorID are Canny's internal 24-character hex IDs.