Skip to main content

Canny MCP Server

Canny MCP Server: How to set up Canny's MCP server so you can access Canny data in your AI tools like ChatGPT, Claude, and Cursor.

Written by Canny

What is the Canny MCP Server?

The Canny MCP Server lets AI tools securely interact with your Canny data using the Model Context Protocol (MCP). MCP provides a way for apps and AI models to communicate through a safe, permission-based interface. In simple terms: it's a way to give an AI controlled access to Canny data.

The MCP Server works with ChatGPT, Claude, Claude Code, Codex, Cursor, GitHub Copilot, Microsoft Copilot, Devin, ClickUp, Canva, Missive, and Runlayer. It's also available on the OpenAI marketplace as a one-click connector for ChatGPT users.

ℹ️ Before you connect

Your workspace needs both of these:

  • A Pro or Business plan. Teams on other plans will see "Current plan does not support MCP connectors" when connecting.

  • Canny Ideas enabled. The MCP Server won't work without it, even on a Pro or Business plan.

An Owner has to connect first. The first connector in a workspace has to be set up by someone with the Owner role. After that, any teammate can authorize their own connector, including Managers and Contributors. If you're a Manager and can't connect, it's likely that no Owner has set one up yet.

Everyone can use it, within their role. Managers and Contributors can both connect. The tools available to each person follow their Canny role permissions, so a Contributor can read data, create Ideas, and edit Ideas within the fields their role allows.

With the MCP Server, you can:

  • Pull structured data about your Feedback (Groups, MRR, Insights, opportunity values, and more) into your AI workflows 📊

  • Automate common tasks like summarizing, querying, deduplicating, and analyzing Feedback 🤖

  • Build custom AI-powered tools that operate on your Canny data without sharing your API key directly 🛠️


Supported clients

How you connect depends on your tool. Some clients register themselves automatically and only need the server URL. Others need a client ID and secret, which are included in their setup sections below.

Connect with the server URL only:

  • ChatGPT, using the one-click connector in the OpenAI marketplace

  • Claude and Claude Code

  • Codex

  • GitHub Copilot in VS Code

Need a client ID and secret:

  • Cursor

  • Microsoft Copilot

  • GitHub Copilot in the Copilot CLI, JetBrains, Eclipse, and Xcode

  • Devin

ClickUp, Canva, Missive, and Runlayer are also supported. Add Canny as an MCP connector using the app's own instructions.

Don't see your tool? Any client that supports remote MCP servers over OAuth can connect. See Connecting any other client below. If you'd like us to support a specific tool, let us know here.


Available tools

The MCP Server ships with over 60 tools, and we add more regularly. Access to each tool is governed by the connecting user's Canny role.

Tools available to all roles, including Contributors:

add_user_to_company
create_company
create_idea
create_insight
create_portal_comment
create_user
link_opportunity
list_admins
list_board_categories
list_board_tags
list_boards
list_changelog_entries
list_changelog_labels
list_comments
list_companies
list_groups
list_idea_fields
list_idea_filtering_operations
list_idea_opportunities
list_idea_statuses
list_idea_themes
list_ideas
list_insights
list_portal_comments
list_portal_statuses
list_portal_voters
list_segment_fields
list_segment_operations
list_segments
list_users
list_views
move_idea
retrieve_company
retrieve_group
retrieve_idea
retrieve_user
retrieve_users
send_to_autopilot
unlink_opportunity
update_company
update_idea
update_portal_category
update_portal_comment

Tools available to Managers and Owners only:

create_changelog_entry
create_group
create_segment
create_view
delete_changelog_entry
delete_group
delete_idea
delete_insight
delete_portal_comment
delete_view
merge_ideas
move_insight
remove_user_from_company
update_changelog_entry
update_changelog_entry_status
update_group
update_insight
update_portal_status
update_view

Segmentation is supported across tools: list_ideas, list_companies, and update_view accept a segment, so your AI assistant can scope Ideas, companies, and Views to a specific customer segment. Use create_segment to create new Segments, alongside the existing list_segments, list_segment_fields, and list_segment_operations tools.

For teams on a Business plan using custom roles, each tool that writes data maps to a specific permission (read-only list_ and retrieve_ tools require none). Grant the matching permission on a custom role to expose the tool:

  • Create ideascreate_idea, send_to_autopilot

  • Create insightscreate_insight

  • Create public commentscreate_portal_comment, update_portal_comment

  • Move ideasmove_idea

  • View user detailscreate_company, update_company, add_user_to_company

  • Manage insightsupdate_insight, delete_insight, move_insight

  • Manage groupscreate_group, update_group, delete_group

  • Manage viewscreate_view, update_view, delete_view

  • Manage user segmentationcreate_segment

  • Manage changelogcreate_changelog_entry, update_changelog_entry, update_changelog_entry_status, delete_changelog_entry

  • Merge/unmerge ideasmerge_ideas

  • Delete ideasdelete_idea

  • Delete commentsdelete_portal_comment

  • Delete usersremove_user_from_company

  • Change portal feedback statusupdate_portal_status

create_user, update_idea, update_portal_category, link_opportunity, and unlink_opportunity don't require a dedicated permission. See Admin roles for details.

update_idea additionally enforces per-field permissions: each field you ask the AI to change must be one the connecting user is already allowed to change in the Canny UI.


Common use cases

  • Triage and deduplication — ask the AI to find similar Ideas, suggest merges, or summarize a backlog.

  • Customer impact analysis — ask the AI to surface Ideas with the highest opportunity value, MRR, or Insight count from a specific segment.

  • Roadmap reasoning — feed the AI your Views and statuses and ask for prioritization suggestions based on your scoring formula.

  • Custom workflow automation — wire the MCP Server into your own AI agents to update statuses, create Ideas, or generate reports.


How to set up the MCP Server with ChatGPT

Connect Canny to ChatGPT via the OpenAI marketplace. The marketplace version includes every available tool.

  1. Click Connect and authorize Canny.


How to set up the MCP Server with Claude

ℹ️

  • To set up MCP with Claude, you must be on a paid Claude plan.

  • On Team and Enterprise plans, only an Owner or Primary Owner can add a custom connector (Organization settings → Connectors); other members can then enable it. On individual plans, you can add it yourself.

  • Install is also supported in Claude Code.

  1. Scroll to the Connectors section and click Add custom connector at the bottom of the list.

  2. Complete with the following values:

    1. Name: Canny

    2. Authentication: OAuth

  3. Click Connect, then authorize Canny when the OAuth window opens.


How to set up the MCP Server with Cursor

  1. Go to Settings → Cursor Settings → MCP.

  2. Click Add new MCP server. This opens a text file, mcp.json.

  3. Add the following entry to mcpServers:

    {  "mcpServers": {    "canny": {      "url": "https://api.canny.io/api/mcp/v1",      "auth": {        "CLIENT_ID": "199f9f08-b723-c80d-af03-70a66e75e8d2",        "CLIENT_SECRET": "93e0cbf1-3eb7-2f10-80b9-183694d2e5fb"      }    }  }}


How to set up the MCP Server with Microsoft Copilot

Add Canny as a tool on a Copilot Studio agent.

  1. Go to the Tools page for your agent.

  2. Select Add a tool, then New tool, then Model Context Protocol.

  3. Complete the server details:

    1. Server name: Canny

    2. Server description: Read and update Canny Ideas, Feedback, and Insights.

  4. Set the authentication type to OAuth 2.0, then set Type to Manual. Canny doesn't support dynamic client registration, so the Dynamic discovery and Dynamic options won't work.

  5. Complete the OAuth fields:

    1. Client ID: b8219f4b-407a-2ca2-55ef-87d9308ac888

    2. Client secret: 0686b66d-6dde-87ef-88c5-cd2351acb532

    3. Authorization URL: https://api.canny.io/api/mcp/oauth/authorize

    4. Token URL template: https://api.canny.io/api/mcp/oauth/token

    5. Refresh URL: https://api.canny.io/api/mcp/oauth/token

    6. Scopes: leave blank

  6. Select Create, then Next.

  7. On Add tool, select Create a new connection, authorize Canny, then select Add to agent.


How to set up the MCP Server with GitHub Copilot

How you connect depends on where you use Copilot.

In VS Code, add Canny as a remote MCP Server using only the server URL, https://api.canny.io/api/mcp/v1. VS Code registers itself automatically, so no client ID or secret is needed. Authorize Canny when the OAuth window opens.

In the Copilot CLI, JetBrains, Eclipse, and Xcode, add Canny as a remote MCP Server and supply the client ID and secret when prompted:

⚠️ The Copilot coding agent and Copilot code review don't support remote MCP servers that use OAuth, so Canny can't be connected there.


How to set up the MCP Server with Devin

  1. Add Canny to your Devin MCP configuration:

    {  "mcpServers": {    "canny": {      "url": "https://api.canny.io/api/mcp/v1",      "transport": "http",      "oauthClientId": "fae753c3-c6b1-47d0-b29f-8906527bf8a4",      "oauthClientSecret": "25ac74d8-8f16-0be0-d9ef-9ca56d7f8ed9"    }  }}
  2. Alternatively, add it from the command line:

    devin mcp add canny https://api.canny.io/api/mcp/v1 --oauth-client-id fae753c3-c6b1-47d0-b29f-8906527bf8a4 --oauth-client-secret 25ac74d8-8f16-0be0-d9ef-9ca56d7f8ed9
  3. Run devin mcp login canny and authorize Canny.


Connecting any other client

Any client that supports remote MCP servers over OAuth can connect to Canny. Point it at:

  • MCP Server URL: https://api.canny.io/api/mcp/v1

  • Authentication: OAuth

  • Authorization URL: https://api.canny.io/api/mcp/oauth/authorize

  • Token URL: https://api.canny.io/api/mcp/oauth/token

Clients that support client ID metadata documents register themselves, so they need nothing beyond the server URL. Clients that don't support them need a client ID and secret from us. The pairs listed in the sections above cover every client we support today. If your tool needs a client ID and secret and isn't listed, contact us.


Things to note

  • If you don't see your AI tool listed and want it supported, let us know here.

  • Tools and permissions are evolving. We may extend Contributor access or lock down certain functionality based on Ideas-specific permission rules.

  • We add new tools regularly, and ship them to every client, including the OpenAI marketplace version.


Related articles

Did this answer your question?