Canny MCP connector

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.

Yes. Once Canny is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client, and the Elaichi Agent. You connect Canny once and every client picks it up.

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.

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.

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.

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 restrict even one of the two Canny actions for a role, the restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot, or any other client cannot run it, whatever the prompt says.

Offboarding a person in Elaichi ends their access to Canny at once, across Claude, ChatGPT, Cursor, Microsoft Copilot, 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.

Yes. Canny is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Yes. Both let Claude, ChatGPT or Cursor use Canny. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Canny call.

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Canny: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.