# Canny MCP connector The Canny connector brings your Canny feedback boards to Claude, ChatGPT, Cursor, and the Elaichi Agent, so anyone on your team can ask which boards exist and pull up a board's details inside the person's own Canny access. Source: https://elaichi.ai/connectors/canny/ ## Facts | | | | --- | --- | | Application | Canny | | Category | Survey | | AI tools | 2 | | Authentication | Connects with an API key | | Needs your own OAuth app | No | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | Yes | ## What you can ask once Canny is connected - List every Canny board and its post count. - Summarize the top voted posts on the Feedback board. - Which Canny boards got new posts this week? ## Connect Canny in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Canny. 2. Optionally set Share with, then press Connect. 3. Paste a Canny API key. One person generates a token in Canny and pastes it once. Everyone else works through Share with, and never sees it. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Canny tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Connect Canny to Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 4. Sign in and approve. On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves. ## Connect Canny to ChatGPT Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 3. Leave Authentication on OAuth, then tick the risk acknowledgement. 4. Press Create, then sign in and approve. Works on the web today. The plugin directory lives at chatgpt.com/plugins. ## Connect Canny to Cursor Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect Canny to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a Canny tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with Canny through Elaichi ### See every feedback board at a glance Product. Ask for a rundown of all your Canny boards before a roadmap review, so you know which feature request, bug, and idea boards are live without opening Canny. ### Find the right board for a customer Support. When a customer raises a request on a ticket, ask which Canny board it belongs on and get the board's name and link to share back in one reply. ### Prepare board links before a renewal call Customer Success. Pull the details of the Canny board tied to an account's product area, then paste the link into the call notes so the customer can follow along. ### Check which boards are public Marketing. Before a launch post, confirm which Canny boards are open to customers and grab their links for the announcement. ### Audit the boards you actually have Operations. List every Canny board and spot duplicates or stale ones that should be merged or archived, then hand a tidy list to the product team. ### Get a quick lay of the land Leadership. Ask how many Canny boards exist and how large each one is to understand where customer feedback is piling up before a planning session. ## Frequently asked questions ### How do I connect Canny to Claude? Connect Canny in Elaichi first, which asks for a Canny API key from your Canny settings and nothing else. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude will ask you to sign in to Elaichi as yourself, and Canny is available from then on. ### Does Canny work with ChatGPT and Cursor as well as Claude? Yes. Once Canny is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Canny once and every client picks it up. ### What can an AI agent actually do with my Canny data? With this Canny connector, an agent can list all the feedback boards in your Canny workspace and pull up a single board's details, such as its name, its link, and how many posts it holds. That means you can ask which boards exist, find the right board for a customer request, or get a board's link without opening Canny. It cannot read individual posts, votes, or comments, and it cannot create or change anything in Canny. ### Does connecting Canny give the AI everything in my workspace? No. When Canny is connected through Elaichi, the agent only sees the boards that the connected Canny account is allowed to see, and it works inside that access rather than around it. Elaichi can narrow that access further, for example limiting which people or teams can use Canny at all, but it can never widen it beyond what Canny itself allows. ### Can my team share one Canny connection? Yes. One person connects Canny in Elaichi with an API key and shares the connection with a team, and nobody else ever handles or sees that key. Each teammate still signs in to Elaichi as themselves, so every Canny lookup in the audit log is tied to the person who made it, not to a shared account. ### Can I stop an agent from deleting or changing things in Canny? This Canny connector only reads boards, so there is nothing an agent can delete or change in Canny through it. Restrictions in Elaichi also work per action, so if you want to hide even one of the two Canny actions from a team, the blocked action is never advertised to Claude, ChatGPT, Cursor, or any other client, and no prompt can reach it. ### What happens to a Canny connection when someone leaves? Offboarding a person in Elaichi ends their access to Canny at once, across Claude, ChatGPT, Cursor, and every other client they used. If Canny was connected through a shared connection, it keeps working for everyone else on the team. If you disconnect Canny in Elaichi, it is removed from every client in one step. ## All 2 Canny tools Every tool below is callable through https://api.elaichi.ai/mcp once Canny is connected, subject to the toolbox it is in and the restrictions on the caller. - **List all Canny boards** (List). List all boards in Canny. Returns an array of board objects including id, name, created, isPrivate, postCount, privateComments, token, and url. - **Get single Canny board by ID** (Get). Retrieve board details in Canny using id. Returns fields like id (board identifier), name (board name), postCount (number of posts), isPrivate (privacy status), and url (board link).