Canny
Canny is a customer feedback management platform that helps teams collect, analyze, and prioritize user feedback to build better products.
Verdict
Common use cases
- Log feature requests from support chats
- Bulk-update post statuses during sprint planning
- Tag feedback themes across customer conversations
- Draft and publish changelog entries at release
- Sync user profiles when onboarding new accounts
Integration
- Vendor
- Canny
- Category
- other
- Auth
- API_KEY
- Tools
- 25
- Composio slug
canny
Tools
- Add Post Tag
Tool to add a tag to a specific post. use when you need to categorize or group content by applying an existing tag.
- Change Post Status
Tool to change a post's status. use when you need to update a post's workflow stage and optionally notify voters.
- Create Changelog Entry
Tool to create and optionally publish a new changelog entry. use when you need to add a product update record, control publish timing, and notify users. example: "create changelog entry titled 'version 1.2' with details '...' and publish im
- Create Comment
Tool to create a new comment on a post. use when you have the authorid and postid and want to submit feedback or replies.
- Create or Update User
Tool to create or update a user in canny. use when you need to provision a new user or synchronize updates to an existing user profile. example: "create or update user with email user@example.com"
- Create Post
Tool to create a new post on a board. use when you have the boardid and userid and need to submit new feedback.
- Create Tag
Tool to create a new tag. use when you have the boardid and tag name and need to categorize posts.
- Create Vote
Tool to create a vote for a post. use when you need to record or migrate a user's vote on a post, optionally setting priority or original creation time. example: create a vote for postid abc123 with voterid user 456.
- Delete Commentdestructive
Tool to delete a comment. use when moderation is required to remove a specific comment by its id. example: "delete the comment with id 553c3ef8b8cdcd1501ba1238."
- Delete Postdestructive
Tool to delete a post. use when you need to permanently remove a post by its id. example: "delete the post with id 553c3ef8b8cdcd1501ba1238."
- Delete Userdestructive
Tool to delete a user and their comments and votes. use when you need to fully remove a user's account and all associated data (e.g., gdpr compliance).
- Delete Votedestructive
Tool to delete a vote. use when you need to remove a user's vote from a specific post by its id. example: "delete the vote from postid abc123 for voterid user 456."
- List Boards
Tool to list all boards. use when you need to retrieve every board for your company after authentication.
- List Categories
Tool to list categories. use when fetching categories for a specific board by its id.
- List Comments
Tool to list comments for posts, boards, or authors. use after authentication to fetch comments with optional filters.
- List Companies
Tool to list companies associated with your canny account. use after authentication to retrieve companies with pagination support.
- List Opportunities
Tool to list opportunities linked to posts. use when you need to fetch customer opportunities synced from crm.
- List Posts
Tool to list posts with various filters. use after selecting a board or to search/filter posts.
- List Tags
Tool to list tags. use when fetching tags optionally filtered by board id and handling pagination.
- List Users
Tool to list end-users in your workspace. use when you need to fetch and paginate through your workspace's users.
- List Votes
Tool to list votes for a post. use after retrieving post details to view voters.
- Retrieve Board
Tool to retrieve details of a board by its id. use when you need metadata for a specific board.
- Retrieve Tag
Tool to retrieve details of a tag by its id. use after obtaining a valid tag id.
- Retrieve User
Tool to retrieve user details by canny user id, app user id, or email. use when you have exactly one identifier and need full user information. example: "retrieve user with email user@example.com"
- Update Post
Tool to update post details. use when you need to change a post's title, details, eta, images, or custom fields.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the MCP integrations page. 2. Click 'Add Integration' and select Canny from the list. 3. In a separate tab, log into your Canny account, go to Settings > API, and generate a new API key with permissions for boards, posts, comments, votes, and users. 4. Copy the key and paste it into the Switchy connection dialog, then click 'Connect'. 5. Switchy will verify the key and list your accessible boards. 6. Open any Space, type '@Canny create post on [board name] titled [your title]' and send — if Canny replies with a post URL, the connection works. 7. To test tagging, try '@Canny add tag [tag name] to post [post ID]' using an existing post. 8. Grant the integration to teammates who triage feedback or manage your roadmap.
What teammates see: by default, memories from Canny are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Log Customer Request
@Canny create a post on the Feature Requests board titled 'Bulk export to CSV' with details 'Customer asked for ability to export all records at once during onboarding call.'Open in a Space →
Update Triage Status
@Canny change the status of post ID abc123 to 'planned' and notify voters that we've added it to the Q2 roadmap.Open in a Space →
Tag Feedback Theme
@Canny add the 'mobile' tag to post ID def456 so we can track all mobile-related feature requests together.Open in a Space →
Publish Release Notes
@Canny create a changelog entry titled 'CSV Export Now Live' with details 'You can now export all records to CSV from the settings page' and publish it immediately.Open in a Space →
Sync New User Profile
@Canny create or update user with email jane@example.com, name 'Jane Doe', and company 'Acme Corp' so her feedback is properly attributed.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Canny what are the top 5 most-voted feature requests on our roadmap board right now?
Based on the current state of your roadmap board, here are the top 5 most-voted requests: 1) Dark mode support (247 votes), 2) API rate limit increase (189 votes), 3) Bulk export functionality (156 votes), 4) SSO integration (142 votes), 5) Mobile app notifications (128 votes). This snapshot reflects votes as of now; totals may shift as users continue voting.
This example shows read-only retrieval of prioritized feedback. Requires API key with read access to boards. Vote counts are illustrative—actual numbers depend on your account's live data. Useful for sprint planning or stakeholder updates without leaving your workspace.
@Canny create a new post titled 'Add webhook retry logic' on the API Improvements board from user sarah@example.com, and tag it 'backend' and 'reliability'
Post created successfully. Title: 'Add webhook retry logic' has been added to the API Improvements board under sarah@example.com's account. Applied tags: 'backend', 'reliability'. The post is now visible to your team and voters. Post ID: pst_abc123xyz can be referenced for future updates or status changes.
This demonstrates creating and categorizing feedback in one step. Requires write permissions and valid board/user identifiers. If the user doesn't exist in Canny, you'll need to provision them first using the create-or-update-user tool. Tags must already exist on the target board.
@Canny review all posts tagged 'urgent' that are still in 'under review' status and draft a summary email explaining why each is blocked
Found 4 posts tagged 'urgent' in 'under review' status. Here's a draft summary: Post 1 (OAuth refresh tokens) is blocked pending security audit completion. Post 2 (CSV import) awaits database schema migration in Q2. Post 3 (Multi-language support) requires localization vendor contract. Post 4 (Real-time sync) is deprioritized due to infrastructure cost concerns. Each item includes voter count and original submission date for context.
This synthesis example pairs Canny's filtering with AI reasoning to explain blockers. The AI infers context from post metadata and comments—accuracy depends on how thoroughly your team documents status reasons in Canny. Useful for stakeholder communication but verify technical details before sending.
Use-case deep-dives
When Canny MCP speeds up weekly feature prioritization
A 10-person SaaS startup runs a Friday feature-review meeting where the PM and two engineers decide what to build next. They pull the week's top-voted Canny posts, tag them by theme (billing, onboarding, integrations), and update statuses to 'planned' or 'under review'. The Canny MCP handles this in one Switchy session: list posts by votes, bulk-tag by keyword patterns, change statuses, and drop a changelog entry for shipped items. The API key setup takes two minutes. This works cleanly until you hit 500+ posts per board—then the list-all calls slow down and you want filtered views the MCP doesn't expose. If your feedback volume is under that threshold and you're triaging weekly, the MCP cuts the meeting from 45 minutes to 20.
Using Canny MCP to sync feature requests into CRM notes
A 6-person customer success team at a B2B company tracks enterprise feature requests in Canny, then manually copies them into Salesforce opportunity notes before renewal calls. The Canny MCP automates the handoff: query posts by a customer's email domain, pull comments and vote counts, format a summary, and paste it into the CRM (via a separate MCP or API). The team runs this in Switchy the day before each QBR. The catch: Canny's user model doesn't enforce email domains, so if customers submit feedback under personal emails, you'll miss requests unless you tag posts by company name first. If your CS team already tags by account and runs structured pre-call prep, this MCP saves 30 minutes per renewal cycle.
When Canny MCP isn't the right call for changelog automation
A 3-person open-source project uses Canny's public roadmap to show what's shipping next. They want to auto-publish a changelog entry every time a GitHub release drops. The Canny MCP can create and publish changelog entries, but it doesn't listen to webhooks or poll external sources—you'd need a separate automation layer (Zapier, n8n, or custom code) to trigger the MCP call. At that point, you're better off hitting Canny's REST API directly from the automation tool. The MCP wins if you're manually writing changelog entries in Switchy and want to pull post data or user names into the draft. If you're chaining external triggers, skip the MCP and use the API.
Frequently asked
What does the Canny MCP let me do in Switchy?
It connects your Canny feedback boards so AI agents can read posts, create comments, update statuses, publish changelog entries, and manage tags. You can ask an agent to triage feature requests, draft release notes from closed posts, or tag incoming feedback by theme — all without leaving Switchy's chat interface.
Do I need admin access to connect Canny?
Yes. The MCP uses an API key, which you generate from your Canny account settings. Only workspace admins can create API keys, so you'll need owner or admin permissions in Canny to set this up. The key grants full read-write access to posts, comments, votes, and changelog entries.
Can the Canny MCP automatically vote on posts or change their status?
Yes to both. The MCP includes tools to create votes on behalf of users and to change post statuses (e.g. from 'open' to 'planned' or 'complete'). You can also configure it to notify voters when a status changes, which is useful for closing the loop on shipped features.
How is this different from logging into Canny and updating posts manually?
The MCP lets AI agents act on Canny data in response to natural-language prompts. Instead of clicking through the Canny UI to tag fifty posts or draft a changelog, you describe the task once and the agent executes it. It's faster for bulk operations and integrates Canny into cross-tool workflows.
Who on my team should connect the Canny integration?
Whoever owns product feedback triage or release communications. Typically a product manager or customer success lead. They'll need Canny admin rights to generate the API key, and they should understand which boards and tags your team uses so agents don't misfile posts.