> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Connect AI agents to the Canny MCP server

The Canny MCP connector routes your AI agent's tool calls to Canny's own MCP server through Scalekit. Each user signs in to Canny once, and Scalekit stores and refreshes their tokens, so your agent never handles credentials. It comes with 64 tools.

**Authentication:** OAuth 2.1/DCR
**Categories:** Customer Support, Project Management
**Tools:** 64: 29 read, 14 write, 21 destructive
**Users sign in with:** OAuth
**OAuth app:** Your own Canny MCP server app
**Built by:** Vendor MCP
**Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=CANNYMCP)

## Setup

1. ### Install the SDK

   **Node.js**

   ```bash
   npm install @scalekit-sdk/node dotenv
   ```

   **Python**

   ```bash
   pip install scalekit-sdk-python python-dotenv
   ```

2. ### Set your credentials

   Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**.

   ```sh title=".env"
   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>
   ```

3. ### Create the Canny MCP connection

   In **AgentKit > Connections**, create a Canny MCP connection and copy its redirect URI. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/).

4. ### Register an OAuth app

   Canny MCP server connections use your own OAuth app. Register one with Canny MCP server and add the redirect URI you copied.

   Then enter the app's Client ID and Client Secret on the Canny MCP connection.

5. ### Authorize a user and make your first call

   **Node.js** (`quickstart.mts`)

   ```typescript
   import { ScalekitClient } from '@scalekit-sdk/node'
   import 'dotenv/config'
   import { createInterface } from 'node:readline/promises'

   const scalekit = new ScalekitClient(
     process.env.SCALEKIT_ENVIRONMENT_URL,
     process.env.SCALEKIT_CLIENT_ID,
     process.env.SCALEKIT_CLIENT_SECRET,
   )
   const actions = scalekit.actions

   const connector = 'cannymcp'
   const identifier = 'user_123'

   // Generate an authorization link for the user
   const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
   console.log('Authorize Canny MCP:', link)
   const rl = createInterface({ input: process.stdin, output: process.stdout })
   await rl.question('Press Enter after authorizing...')
   rl.close()

   // Make your first call
   const result = await actions.executeTool({
     connector,
     identifier,
     toolName: 'cannymcp_list_admins',
     toolInput: {},
   })
   console.log(result)
   ```

   ```bash
   npx tsx quickstart.mts
   ```

   **Python** (`quickstart.py`)

   ```python
   import os
   from scalekit import ScalekitClient
   from dotenv import load_dotenv
   load_dotenv()

   scalekit_client = ScalekitClient(
       env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),
       client_id=os.getenv("SCALEKIT_CLIENT_ID"),
       client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
   )
   actions = scalekit_client.actions

   connection_name = "cannymcp"
   identifier = "user_123"

   # Generate an authorization link for the user
   link_response = actions.get_authorization_link(
       connection_name=connection_name,
       identifier=identifier,
   )
   print("Authorize Canny MCP:", link_response.link)
   input("Press Enter after authorizing...")

   # Make your first call
   result = actions.execute_tool(
       tool_input={},
       tool_name="cannymcp_list_admins",
       connection_name=connection_name,
       identifier=identifier,
   )
   print(result)
   ```

   ```bash
   python quickstart.py
   ```

   Each user signs in once. See [Authorize a user](/agentkit/tools/authorize/) for the full flow and statuses.

## Tools

Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool).

**Node.js**

```typescript
const result = await actions.executeTool({
  toolName: 'cannymcp_list_admins',
  toolInput: {},
  connector: 'cannymcp',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="cannymcp_list_admins",
    tool_input={},
    connection_name="cannymcp",
    identifier="user_123",
)
```

`result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call.

### `cannymcp_list_admins`

List Admin Teammates · Read-only

Read-only: Returns all admin teammates, including each admin name so callers can identify users. By default, admin IDs are omitted. To include IDs for use with other tools that accept admin IDs, pass `include: ["ids"]`. This tool is not idempotent: underlying data can change between calls, so avoid relying on cached results during longer conversations.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `include` (`array`, optional): Optional response fields to include. Pass `["ids"]` to include admin IDs for cross-tool usage.

Example input: `{}`

### `cannymcp_list_board_categories`

List Board Categories · Read-only

Read-only: Returns categories that belong to the provided board. Categories may be nested via `parentID`.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `boardID` (`string`, required): The ID of the board whose categories should be returned.
- `limit` (`number`, optional): The maximum number of categories to return. Default: `25`.
- `skip` (`number`, optional): The number of categories to skip. Default: `0`.

Example input: `{"boardID":"<boardID>"}`

### `cannymcp_list_board_tags`

List Board Tags · Read-only

Read-only: Returns tags that belong to the provided board sorted by newest first.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `boardID` (`string`, required): The ID of the board whose tags should be returned. Use `list_boards` to discover valid board IDs.
- `limit` (`number`, optional): The maximum number of tags to return. Default: `25`.
- `skip` (`number`, optional): The number of tags to skip. Default: `0`.

Example input: `{"boardID":"<boardID>"}`

### `cannymcp_list_boards`

List Boards · Read-only

Read-only: Returns all boards. This tool is not idempotent: underlying data can change between calls, so avoid relying on cached results during longer conversations.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs: none.

Example input: `{}`

### `cannymcp_list_changelog_entries`

List Changelog Entries · Read-only

Read-only: Returns changelog entries, filtered and sorted by the given parameters.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `labelIDs` (`array`, optional): Filter to entries that have any of these label IDs. Discover valid IDs via `list_changelog_labels`.
- `limit` (`number`, optional): The maximum number of changelog entries to return. Default: `10`.
- `skip` (`number`, optional): The number of changelog entries to skip. Default: `0`.
- `sort` (`string`, optional): How to sort the returned entries. One of: `created`, `lastSaved`, `nonPublishedFirst`, `publishedAt`. Default: `nonPublishedFirst`.
- `type` (`string`, optional): Filter to entries of this type. One of: `fixed`, `new`, `improved`.

Example input: `{}`

### `cannymcp_list_changelog_labels`

List Changelog Labels · Read-only

Read-only: Returns all changelog labels. Labels are used to categorize changelog entries.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs: none.

Example input: `{}`

### `cannymcp_list_comments`

List Idea Comments · Read-only

Read-only: Returns idea comments from a specific idea's activity tab. Use `create_comment` to add one. Mentions in comment text are converted to readable plaintext names. By default, user-related identifiers are omitted. Pass `include: ["users"]` to include them.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `ideaID` (`string`, required): The ID of the idea whose comments should be returned.
- `include` (`array`, optional): Optional response fields to include. By default, user-related identifiers are omitted. Pass `["users"]` to include them.

Example input: `{"ideaID":"<ideaID>"}`

### `cannymcp_list_companies`

List Companies · Read-only

Read-only: Returns a list of all companies associated with your company, ordered by created date, optionally filtered by search query or scoped to a segment.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `cursor` (`string`, optional): The pagination cursor. Use the `nextCursor` value from a previous response to fetch the next page. Not supported with `search`.
- `limit` (`number`, optional): The maximum number of companies to return. Default: `10`.
- `search` (`string`, optional): A search query to filter companies by name.
- `segmentID` (`string`, optional): The ID of a segment to scope companies to. Use the `list_segments` tool to discover valid IDs. Only a segment's company-scoped attributes are applied, so a segment whose `objectType` is 'mixed' narrows the results by part of its definition, and one whose `objectType` is 'user' is rejected because it cannot narrow companies at all.

Example input: `{}`

### `cannymcp_list_groups`

List Groups · Read-only

Read-only: Returns all groups used to organize ideas. Groups are organizational units that group ideas together. Each idea belongs to one or no group. Groups can be nested to create a hierarchy of groups. This tool is not idempotent: underlying data can change between calls, so avoid relying on cached results during longer conversations.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs: none.

Example input: `{}`

### `cannymcp_list_idea_fields`

List Idea Fields · Read-only

Read-only: Returns all fields that can be used when filtering ideas, including default fields and company-specific custom, score, and formula fields. Each field includes its ID, type, label, whether it has predefined options, and whether it is a default or custom field. For default fields with predefined options, use `list_groups` for the `group` field, `list_idea_statuses` for the `status` field, and `list_idea_themes` for the `themes` field to discover valid option IDs. Use this together with `list_idea_filtering_operations` when constructing the `filtering` parameter for `list_ideas`. This tool is not idempotent: underlying data can change between calls, so avoid relying on cached results during longer conversations.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs: none.

Example input: `{}`

### `cannymcp_list_idea_filtering_operations`

List Idea Filtering Operations · Read-only

Read-only: Returns all the filtering options that can be used in idea filters, including the input type they expect and which idea field types they apply to. Use this together with `list_idea_fields` to construct valid `filtering.filters` entries for the `list_ideas` tool. This tool is not idempotent: underlying data can change between calls, so avoid relying on cached results during longer conversations.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs: none.

Example input: `{}`

### `cannymcp_list_idea_opportunities`

List Idea Opportunities · Read-only

Read-only: Returns a paginated list of opportunities linked to an idea. An opportunity represents a potential customer, synced in from Salesforce or Hubspot. Opportunities linked to descendant ideas are included and deduplicated. To link or unlink opportunities, use the `link_opportunity` and `unlink_opportunity` tools respectively.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `ideaID` (`string`, required): The ID of the idea to list linked opportunities for. To discover valid IDs, call the `list_ideas` tool.
- `cursor` (`string`, optional): The pagination cursor. Use the `nextCursor` value from a previous response to fetch the next page.
- `limit` (`number`, optional): The maximum number of opportunities to return. Default: `50`.

Example input: `{"ideaID":"<ideaID>"}`

### `cannymcp_list_idea_statuses`

List Idea Statuses · Read-only

Read-only: Returns all idea statuses. Use this to filter ideas by status when calling the `list_ideas` tool. This tool is not idempotent: underlying data can change between calls, so avoid relying on cached results during longer conversations.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs: none.

Example input: `{}`

### `cannymcp_list_idea_themes`

List Idea Themes · Read-only

Read-only: Returns all idea themes. Themes are used to categorize ideas into more general topics. Each idea can be assigned to one or no theme. Use these to filter ideas by theme when calling the `list_ideas` tool. This tool is not idempotent: underlying data can change between calls, so avoid relying on cached results during longer conversations.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs: none.

Example input: `{}`

### `cannymcp_list_ideas`

List Ideas · Read-only

Read-only: Returns a list of ideas, filtered and sorted by the given parameters. Use the `list_idea_fields` and `list_idea_filtering_operations` tools to discover which fields you can filter and sort by using this tool. By default, user-related identifiers are omitted, and user-typed fields (default and custom) are excluded from `fields`. Pass `include: ["users"]` to include user-related identifiers and user-typed fields. Pass `segmentID` to scope segmentable metrics to a company segment. To find ideas a company requested, filter on the `companies` field with `resource: insightField` and condition `isOneOf`, using company IDs from `list_companies`. Note this tool lists *Canny Ideas*, not to be confused with *Canny Posts*. This tool is not idempotent: underlying data can change between calls, so avoid relying on cached results during longer conversations. If you already know the idea ID or urlName (for example, parsed from a Canny URL), prefer the `retrieve_idea` tool — it is faster and more accurate than searching with this tool.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `cursor` (`string`, optional): The pagination cursor. Use the `nextCursor` value from a previous response to fetch the next page. A cursor is only valid for the same parameters that produced it; changing `sort`, `filtering`, or `segmentID` invalidates it.
- `filtering` (`object`, optional): Filters to apply to ideas. To discover available fields and operations, first call the `list_idea_fields` and `list_idea_filtering_operations` tools.
- `groupID` (`string`, optional): The ID of the group to scope ideas to. If provided, only ideas within this group will be returned.
- `include` (`array`, optional): Optional response fields to include. By default, user-related identifiers and user-typed fields are omitted. Pass `["users"]` to include them. Pass `["totalCount"]` to include a `totalCount` field reflecting the total number of ideas matching the filters (independent of pagination). `totalCount` cannot be combined with `search`.
- `limit` (`number`, optional): The maximum number of ideas to return. Default: `25`.
- `parentID` (`string`, optional): The ID of a parent idea. If provided, only ideas that are children of this parent will be returned.
- `search` (`string`, optional): The search query to filter ideas by. Note: search does not support pagination or custom sorting, and cannot be combined with a filter on a segmented field while `segmentID` is applied.
- `segmentID` (`string`, optional): The ID of a segment to scope segmentable idea metrics to (the default Insight, User, and Company Count and ARR factors, plus any score field that consumes one). Field values in the response then reflect only in-segment activity, and can be sorted and filtered on. Use the `list_segments` tool to discover IDs; only segments whose `objectType` is `company` can be applied. When `viewID` is provided and this is omitted, the view’s own segment (if any) is applied.
- `sort` (`object`, optional): How to sort the returned ideas. If omitted, a default sort is applied. If `search` is provided, this will be ignored. Provide a `field` (from `list_idea_fields`) and a `direction` (asc, desc).
- `viewID` (`string`, optional): The ID of a view whose filters should be applied when listing ideas. Cannot be combined with `filtering`; provide one or the other.

Example input: `{}`

### `cannymcp_list_insights`

List Idea Insights · Read-only

Read-only: Returns a paginated list of insights linked to a specific idea, including priority, source, the company each is attributed to, and linked comment/vote IDs. By default, user-related identifiers are omitted — pass `include: ["users"]` to include them.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `ideaID` (`string`, required): The ID of the idea whose insights should be returned.
- `cursor` (`string`, optional): The pagination cursor. Use the `nextCursor` value from a previous response to fetch the next page.
- `include` (`array`, optional): Optional response fields to include. By default, user-related identifiers are omitted. Pass `["users"]` to include them.
- `limit` (`number`, optional): The maximum number of insights to return. Default: `25`.
- `type` (`string`, optional): Filter to insights of this type: "vote" (linked to a vote), "comment" (linked to a comment), or "all" (every insight, including ones linked to neither, such as feedback captured from other sources). One of: `all`, `vote`, `comment`. Default: `all`.

Example input: `{"ideaID":"<ideaID>"}`

### `cannymcp_list_portal_comments`

List Portal Comments · Read-only

Read-only: Returns a paginated list of comments left on the portal. By default, it returns portal comments across all published ideas in the company. Mentions in comment text are converted to readable plaintext names. By default, user-related identifiers are omitted. Pass `include: ["users"]` to include them. These are portal comments, distinct from the idea comments managed by the `list_comments` and `create_comment` tools.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `cursor` (`string`, optional): The pagination cursor. Use the `nextCursor` value from a previous response to fetch the next page.
- `ideaID` (`string`, optional): The ID of a published idea. When provided, returns portal comments on that idea only.
- `include` (`array`, optional): Optional response fields to include. By default, user-related identifiers are omitted. Pass `["users"]` to include them.
- `limit` (`number`, optional): The maximum number of comments to return. Default: `25`.

Example input: `{}`

### `cannymcp_list_portal_statuses`

List Portal Statuses · Read-only

Read-only: Returns all portal statuses (the public-facing statuses shown on the portal/roadmap). Use this to discover valid status IDs and names before changing a status or filtering by one.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs: none.

Example input: `{}`

### `cannymcp_list_portal_voters`

List Portal Voters · Read-only

Read-only: Returns the end-users who voted on a specific idea, each with the vote's priority, the voter's company, and when they voted. By default, user identifiers and emails are omitted — pass `include: ["emails"]` for each voter's email and `include: ["ids"]` for their user ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `ideaID` (`string`, required): The ID of the idea whose voters should be returned.
- `cursor` (`string`, optional): The pagination cursor. Use the `nextCursor` value from a previous response to fetch the next page.
- `include` (`array`, optional): Optional response fields to include. By default, user identifiers and emails are omitted. Pass `["emails"]` to include each voter's email and `["ids"]` to include each voter's user ID.
- `limit` (`number`, optional): The maximum number of voters to return. Default: `50`.

Example input: `{"ideaID":"<ideaID>"}`

### `cannymcp_list_segment_fields`

List Segment Fields · Read-only

Read-only: Returns all fields that can be used to define user segments, including both standard and custom fields. Each field includes its ID, source (`standard` or `custom`), fieldType (`boolean`, `number`, `date`, or `string`), objectType (`company` or `user`), and human-readable name. Use this before creating or updating segments to understand available attributes. This tool is not idempotent: underlying data can change between calls, so avoid relying on cached results during longer conversations.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs: none.

Example input: `{}`

### `cannymcp_list_segment_operations`

List Segment Operations · Read-only

Read-only: Returns all operations that can be applied to segment attributes, with a short human-readable description of each. Use this to understand how to define attribute filters when creating or editing segments. This tool is not idempotent: underlying data can change between calls, so avoid relying on cached results during longer conversations.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs: none.

Example input: `{}`

### `cannymcp_list_segments`

List Segments · Read-only

Read-only: Returns all user segments, ordered by name. Use this to understand how users are segmented. Attribute `id`s are field identifiers: use the `list_segment_fields` tool to resolve them to human-readable fields and `list_segment_operations` to interpret each `op`. This tool is not idempotent: underlying data can change between calls, so avoid relying on cached results during longer conversations.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs: none.

Example input: `{}`

### `cannymcp_list_users`

List Users · Read-only

Read-only: Returns end-users in this workspace, optionally filtered by name or email. To fetch a specific set of users by their IDs, use `retrieve_users` instead.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `cursor` (`string`, optional): Pagination cursor. Pass the `nextCursor` value from a previous response to fetch the next page. Cannot be combined with `search`.
- `include` (`array`, optional): Optional response fields to include. Pass `["ids"]` to include user IDs for cross-tool usage. Pass `["emails"]` to include each user's email address.
- `limit` (`number`, optional): The maximum number of users to return. Default: `25`.
- `search` (`string`, optional): Search query to filter users by name or email. Cannot be combined with `cursor`.

Example input: `{}`

### `cannymcp_list_views`

List Views · Read-only

Read-only: Returns saved idea views, including their filters, grouping, and sort configuration. Use this to discover view IDs and settings you can reference when calling the `list_ideas` tool (for example via the `viewID` parameter) or when constructing custom filters. This tool is not idempotent: underlying data can change between calls, so avoid relying on cached results during longer conversations.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `groupID` (`string`, optional): The ID of the group whose saved idea views should be returned. To discover valid IDs, first call the `list_groups` tool. To fetch views that are not assigned to any group, pass null. Views that do not belong to any group represent global views (applied to all ideas, not only ideas within a group).

Example input: `{}`

### `cannymcp_retrieve_company`

Retrieve Company · Read-only

Read-only: Returns a single company looked up by its ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `id` (`string`, required): The company's unique identifier. Discover valid IDs via the `list_companies` tool.

Example input: `{"id":"<id>"}`

### `cannymcp_retrieve_group`

Retrieve Group · Read-only

Read-only: Returns a single group looked up by its ID or its urlName. Groups are organizational units that group ideas together. Exactly one of `id` or `urlName` must be provided. Discover valid IDs via the `list_groups` tool.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `id` (`string`, optional): The ID of the group to retrieve. Mutually exclusive with `urlName`. Discover valid IDs via the `list_groups` tool.
- `urlName` (`string`, optional): The urlName of the group to retrieve. Mutually exclusive with `id`. urlNames appear in Canny group URLs (for example, `https://<subdomain>.canny.io/admin/ideas?group=<urlName>`).

Example input: `{}`

### `cannymcp_retrieve_idea`

Retrieve Idea · Read-only

Read-only: Returns a single idea looked up by its ID or by a link to it. Exactly one of `id` or `url` must be provided.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `id` (`string`, optional): The ID of the idea to retrieve. Mutually exclusive with `url`. Discover valid IDs via `list_ideas`.
- `include` (`array`, optional): Optional response fields to include. By default, user-related identifiers and user-typed fields are omitted. Pass `["users"]` to include them.
- `url` (`string`, optional): A link to the idea to retrieve. Mutually exclusive with `id`. Accepts the admin idea link `https://<subdomain>.canny.io/admin/ideas?idea=<urlName>` (the `url` other tools return), a public post link `https://<subdomain>.canny.io/<board-urlName>/p/<post-urlName>`, an admin post link `/admin/feedback/<board-urlName>/p/<post-urlName>` or `/admin/board/<board-urlName>/p/<post-urlName>`, links on a custom domain, or a bare idea urlName.

Example input: `{}`

### `cannymcp_retrieve_user`

Retrieve User · Read-only

Read-only: Returns a single end-user looked up by `id` or `email`.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `email` (`string`, optional): The user's email address. Mutually exclusive with `id`. Discover valid emails via `list_users` with `include: ['emails']`.
- `id` (`string`, optional): The user's unique identifier from Canny. Mutually exclusive with `email`. Discover valid IDs via `list_users` with `include: ["ids"]`.
- `include` (`array`, optional): Optional response fields to include. Pass `["ids"]` to include the user's ID. Pass `["emails"]` to include the user's email address.

Example input: `{}`

### `cannymcp_retrieve_users`

Retrieve Users · Read-only

Read-only: Bulk-fetches end-users in this workspace by their IDs (max 50). Only IDs that resolve to a user in this workspace are returned; unknown IDs are silently skipped. Discover valid IDs via `list_users` with `include: ["ids"]`.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `ids` (`array`, required): The user IDs to fetch (max 50).
- `include` (`array`, optional): Optional response fields to include. Pass `["ids"]` to include user IDs for cross-tool usage. Pass `["emails"]` to include each user's email address.

Example input: `{"ids":[]}`

### `cannymcp_add_user_to_company`

Add User To Company · Write

Adds an association between the given user and company.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `companyID` (`string`, required): The ID of the company to add the user to. To discover valid IDs, call the `list_companies` tool.
- `userID` (`string`, required): The ID of the user to add. To discover valid IDs, call the `list_users` tool with `include: ["ids"]`. If the user does not exist, call the `create_user` tool to create it first.

Example input: `{"companyID":"<companyID>","userID":"<userID>"}`

### `cannymcp_create_changelog_entry`

Create Changelog Entry · Write

Creates a new changelog entry, optionally publishing it immediately or scheduling it for later. Entries are created as drafts unless `published` or `scheduledFor` is provided.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `details` (`string`, required): The details of your changelog entry.
- `title` (`string`, required): The title of your changelog entry.
- `ideaIDs` (`array`, optional): A list of idea IDs to link to your changelog entry. Each idea must already be published to the portal and not linked to another entry. Discover valid IDs via `list_ideas`.
- `labelIDs` (`array`, optional): A list of label IDs to assign to your changelog entry. Discover valid IDs via `list_changelog_labels`.
- `notify` (`boolean`, optional): Whether to notify users by email after publishing. Default is false.
- `published` (`boolean`, optional): Whether you want to publish the changelog entry immediately or not. Default is false.
- `publishedOn` (`string`, optional): If `published` is set to true and you would like to set a published date in the past, in ISO 8601 format.
- `scheduledFor` (`string`, optional): The date you want the changelog entry to be published, in ISO 8601 format. This has to be in the future.
- `type` (`string`, optional): The type of your changelog entry. One of: `fixed`, `new`, `improved`.

Example input: `{"details":"<details>","title":"<title>"}`

### `cannymcp_create_comment`

Create Idea Comment · Write

Creates an idea comment on the idea's activity tab, authored by the connected user. Idea comments are visible only to admins, never appear on the portal, and do not change the idea's status or notify voters, so use them for internal progress notes. To post on the portal, use `create_portal_comment` instead. Pass `mentionedAdminIDs` to notify admins; they are appended to the comment as a "cc" line. Pass `parentID` to reply to an existing root-level idea comment. By default, user-related identifiers in the returned comment are omitted. Pass `include: ["users"]` to include them.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `ideaID` (`string`, required): The ID of the idea to comment on.
- `value` (`string`, required): The text content of the comment. Must not be empty.
- `include` (`array`, optional): Optional response fields to include. By default, user-related identifiers are omitted from the returned comment. Pass `["users"]` to include them.
- `mentionedAdminIDs` (`array`, optional): Optional IDs of admins to mention and notify. Each must be an admin. Discover valid IDs via `list_admins` with `include: ["ids"]`. Do not write mentions into `value`.
- `parentID` (`string`, optional): Optional ID of a root-level idea comment to reply to. The parent comment must be on the same idea and must not itself be a reply. Discover valid IDs via the `list_comments` tool.

Example input: `{"ideaID":"<ideaID>","value":"<value>"}`

### `cannymcp_create_company`

Create Company · Write

Creates a new company. Recurring revenue is optional, but `spend` and `spendType` (`mrr` for monthly recurring revenue, `arr` for annual recurring revenue) are all-or-nothing: provide both or neither. When asking a user for revenue, use the SaaS terms — e.g. "What's this company's ARR?". If the user gives a figure without saying whether it's MRR or ARR, ask before creating the company.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `domain` (`string`, required): The company's domain, e.g. 'acme.com'. Used to deduplicate — creation fails if a company with this domain already exists.
- `name` (`string`, required): The company's name.
- `spend` (`number`, optional): The company's recurring revenue, in dollars — its MRR or ARR per `spendType`. Must be paired with `spendType`; provide both or neither.
- `spendType` (`string`, optional): Whether `spend` is monthly recurring revenue (`mrr`) or annual recurring revenue (`arr`). Must be paired with `spend`; provide both or neither. ARR is converted to a monthly amount (divided by 12) before being stored. One of: `mrr`, `arr`.

Example input: `{"domain":"acme.com","name":"<name>"}`

### `cannymcp_create_group`

Create Group · Write

Creates a new group used to organize ideas.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): The name of the group to create.
- `description` (`string`, optional): An optional description of the group.
- `parent` (`string`, optional): An optional parent group ID. When set, the new group will be created as a sub-group of this parent. To discover valid parent IDs, call the `list_groups` tool. Sub-groups can be nested at most 3 levels deep; passing a parent that is already at the maximum depth will be rejected.

Example input: `{"name":"<name>"}`

### `cannymcp_create_idea`

Create Idea · Write

Creates a new idea. Use this tool to collect feedback from the user. Pass `insight` with a `companyID` and/or `userIDs` to attribute the idea to the customer who asked for it: that records an insight on the new idea, returned as `insight`. By default, user-related identifiers in the returned idea are omitted. Pass `include: ["users"]` to include user-related identifiers.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `title` (`string`, required): The title of the idea to create. This should be a concise summary of the idea.
- `description` (`string`, optional): An optional longer description of the idea. This can include context, use cases, or any additional details that help clarify the idea.
- `group` (`string`, optional): An optional (but strongly recommended) group ID to associate the idea with. Must refer to a group in the same company. To discover valid IDs, first call the `list_groups` tool. When creating a sub-idea (i.e. when `parent` is set), this can be omitted. The sub-idea will inherit the parent idea's group. If provided alongside `parent`, it must match the parent's group.
- `include` (`array`, optional): Optional response fields to include. By default, user-related identifiers are omitted from the returned idea. Pass `["users"]` to include them.
- `insight` (`object`, optional): Optional: attributes the new idea to the customer who asked for it by recording an insight on it, returned as `insight`. Only takes effect when `companyID` or `userIDs` is set; omit it when no customer asked for the idea.
- `parent` (`string`, optional): An optional parent idea ID. When set, the new idea will be created as a sub-idea of this parent. The sub-idea inherits the parent's group automatically, so you should leave `group` unset. To discover valid parent IDs, call the `list_ideas` tool. Sub-ideas can be nested at most 3 levels deep; passing a parent that is already at the maximum depth will be rejected.

Example input: `{"title":"<title>"}`

### `cannymcp_create_insight`

Create Insight · Write

Creates a new insight on an idea, capturing feedback from a customer (an end user, a company, or both). At least one of `companyID` or `userIDs` must be provided. When both are provided and the user is not already associated with the company, an association will be created. By default, user-related identifiers in the returned insight are omitted. Pass `include: ["users"]` to include them.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `ideaID` (`string`, required): The ID of the idea this insight is linked to. To discover valid IDs, call the `list_ideas` tool.
- `value` (`string`, required): The content of the insight. This should capture the customer feedback in their own words.
- `companyID` (`string`, optional): Optional ID of the company the insight is attributed to. To discover valid IDs, call the `list_companies` tool.
- `include` (`array`, optional): Optional response fields to include. By default, user-related identifiers are omitted from the returned insight. Pass `["users"]` to include them.
- `priority` (`string`, optional): Optional priority indicating how important this feedback is to the customer. One of: `nice-to-have`, `important`, `must-have`, `no-priority`.
- `url` (`string`, optional): Optional source URL pointing back to where this feedback came from.
- `userIDs` (`array`, optional): Optional list of user IDs the insight is attributed to. To discover valid IDs, call the `list_users` tool.

Example input: `{"ideaID":"<ideaID>","value":"<value>"}`

### `cannymcp_create_portal_comment`

Create Portal Comment · Write

Creates a portal comment for a specific idea, authored by the connected user. The idea must be published to the portal. Portal comments live on the portal and are distinct from idea comments (`list_comments`, `create_comment`). Pass `parentID` to reply to an existing root-level comment. By default, user-related identifiers in the returned comment are omitted. Pass `include: ["users"]` to include them.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `ideaID` (`string`, required): The ID of the idea whose portal post the comment should be added to.
- `value` (`string`, required): The text content of the comment. Must not be empty.
- `include` (`array`, optional): Optional response fields to include. By default, user-related identifiers are omitted from the returned comment. Pass `["users"]` to include them.
- `internal` (`boolean`, optional): Whether this comment is only available for internal usage. Default is false. Default: `false`.
- `parentID` (`string`, optional): Optional ID of a root-level comment to reply to. The parent comment must be on the same idea and must not itself be a reply. Discover valid IDs via the `list_portal_comments` tool.
- `shouldNotifyVoters` (`boolean`, optional): Whether to notify the post's voters about this comment. Defaults to false. Default: `false`.

Example input: `{"ideaID":"<ideaID>","value":"<value>"}`

### `cannymcp_create_segment`

Create Segment · Write

Creates a new user segment used for user segmentation. The segment is defined by a name and a list of attribute filters. Use the list_segment_fields and list_segment_operations tools first to discover valid field IDs and operators.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `attributes` (`array`, required): The attributes defining segment membership. A user must match all of them, and at least one attribute is required.
- `name` (`string`, required): The name of the segment to create. This should be a concise, human-readable label.

Example input: `{"attributes":[],"name":"<name>"}`

### `cannymcp_create_user`

Create User · Write

Creates a new end-user in the company and returns its ID and admin URL. Providing an `email` is strongly recommended: it helps deduplicate against existing users (if one already has that email, it is returned instead of creating a duplicate).

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): The new user's name.
- `email` (`string`, optional): The new user's email address.

Example input: `{"name":"<name>"}`

### `cannymcp_create_view`

Create View · Write

Creates a new View.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): The name of the view to create.
- `groupID` (`string`, optional): An optional group ID. When set, the new view will be scoped to this group. To discover valid group IDs, call the `list_groups` tool. Pass null (or omit) to create a global view that is not assigned to any group.

Example input: `{"name":"<name>"}`

### `cannymcp_follow_idea`

Follow Idea · Write

Follows or unfollows an idea. Followers are notified when the idea changes status or gets a new insight. Applies to the connected user unless `userIDs` names other admins. Use the `list_ideas` tool to discover valid idea IDs.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `follow` (`boolean`, required): Pass true to follow the idea, or false to unfollow it.
- `ideaID` (`string`, required): The ID of the idea to follow or unfollow.
- `userIDs` (`array`, optional): Optional IDs of the admins who should follow or unfollow the idea. Each must be an admin. Discover valid IDs via `list_admins` with `include: ["ids"]`. Omit to apply to the connected user.

Example input: `{"follow":true,"ideaID":"<ideaID>"}`

### `cannymcp_link_opportunity`

Link Opportunity · Write

Links a Salesforce opportunity or HubSpot deal to an idea. Provide exactly one of `salesforceOpportunityID` or `hubspotDealID`. To also capture customer feedback, call the `create_insight` tool separately.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `ideaID` (`string`, required): The ID of the idea to link the opportunity to. To discover valid IDs, call the `list_ideas` tool.
- `hubspotDealID` (`string`, optional): The HubSpot ID of the deal to link.
- `salesforceOpportunityID` (`string`, optional): The Salesforce ID of the opportunity to link.

Example input: `{"ideaID":"<ideaID>"}`

### `cannymcp_send_to_autopilot`

Send to Autopilot · Write

Sends a piece of unstructured feedback (e.g. a transcript, support ticket, or note) through Canny's Autopilot, which uses AI to extract feature requests, create ideas for new ones, and link duplicates to existing ideas. At least one of `userID` or `companyID` must be provided to attribute the feedback. Returns the ideas that were created or matched, along with any reasons extraction was skipped.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `text` (`string`, required): The raw feedback text to process. Can be a transcript, support ticket, customer note, or any other unstructured text containing feature requests.
- `companyID` (`string`, optional): The ID of the company the feedback should be attributed to. Discover valid IDs via `list_companies`. When supplied alongside `userID`, the user is added as a member of that company.
- `sourceUrl` (`string`, optional): An optional URL pointing to the original source of the feedback (e.g. a ticket or call recording).
- `userID` (`string`, optional): The ID of the user the feedback should be attributed to. Discover valid IDs via `list_users`.

Example input: `{"text":"<text>"}`

### `cannymcp_delete_changelog_entry`

Delete Changelog Entry · Destructive

Deletes a changelog entry.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `entryID` (`string`, required): The ID of the changelog entry to delete.

Example input: `{"entryID":"<entryID>"}`

### `cannymcp_delete_group`

Delete Group · Destructive

Deletes a group, its sub-groups, and views scoped to those groups. Ideas in those groups are kept and ungrouped by default; pass `moveIdeasToGroupID` to move them to another group instead. Set `preserveIdeas` to false to delete the contained ideas too. Use `list_groups` to find valid group IDs.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `group` (`string`, required): The ID of the group to delete.
- `moveIdeasToGroupID` (`string`, optional): The ID of an existing group to move preserved ideas into. Only valid when `preserveIdeas` is not false. Must not be the group being deleted or one of its sub-groups. If omitted, preserved ideas are ungrouped.
- `preserveIdeas` (`boolean`, optional): Whether to keep the ideas in this group and its sub-groups instead of deleting them. Defaults to true. When false, those ideas (and their comments, votes, and insights) are deleted. The group, sub-groups, and their views are always deleted. Default: `true`.

Example input: `{"group":"<group>"}`

### `cannymcp_delete_idea`

Delete Idea · Destructive

Deletes an idea. The idea, along with all of its descendants, insights, and related data will be deleted. Use the `list_ideas` tool to discover valid idea IDs.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `ideaID` (`string`, required): The ID of the idea to delete. The idea will be marked as deleted.

Example input: `{"ideaID":"<ideaID>"}`

### `cannymcp_delete_insight`

Delete Insight · Destructive

Deletes an insight.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `insightID` (`string`, required): The ID of the insight to delete. To discover valid IDs, call the `list_insights` tool.

Example input: `{"insightID":"<insightID>"}`

### `cannymcp_delete_portal_comment`

Delete Portal Comment · Destructive

Deletes a portal comment and its replies. Discover valid IDs via the `list_portal_comments` tool. These are portal comments, distinct from the idea comments managed by the `list_comments` and `create_comment` tools.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `portalCommentID` (`string`, required): The ID of the portal comment to delete. Discover valid IDs via the `list_portal_comments` tool.

Example input: `{"portalCommentID":"<portalCommentID>"}`

### `cannymcp_delete_view`

Delete View · Destructive

Deletes a view. Default views and the last remaining view in a group cannot be deleted.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `viewID` (`string`, required): The ID of the view to delete. Use the `list_views` tool to discover valid view IDs.

Example input: `{"viewID":"<viewID>"}`

### `cannymcp_merge_ideas`

Merge Ideas · Destructive

Merges two ideas together. The source idea (fromIdeaID) will be merged into the target idea (intoIdeaID). All descendants, insights, and related data from the source idea will be moved to the target idea, and the source idea will be marked as deleted. Use the `list_ideas` tool to discover valid idea IDs.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `fromIdeaID` (`string`, required): The ID of the source idea to merge from. This idea will be merged into the target idea and marked as deleted.
- `intoIdeaID` (`string`, required): The ID of the target idea to merge into. This idea will receive all descendants, insights, and related data from the source idea.

Example input: `{"fromIdeaID":"<fromIdeaID>","intoIdeaID":"<intoIdeaID>"}`

### `cannymcp_move_idea`

Move Idea · Destructive

Moves an idea to a different group and/or reparents it under another idea. At least one of `groupID` or `parentID` must be provided. A sub-idea must belong to the same group as its parent.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `ideaID` (`string`, required): The ID of the idea to move. To discover valid IDs, call the `list_ideas` tool.
- `groupID` (`string`, optional): The ID of the group to move the idea into, or `null` to remove it from any group. Omit to leave the idea's current group unchanged. To discover valid IDs, call the `list_groups` tool. When the idea has a parent, omit this to inherit the parent's group; a non-matching value is rejected.
- `parentID` (`string`, optional): The ID of the idea to reparent this idea under, making it a sub-idea, or `null` to move it to the top level. Omit to leave the idea's current parent unchanged. To discover valid parent IDs, call the `list_ideas` tool.

Example input: `{"ideaID":"<ideaID>"}`

### `cannymcp_move_insight`

Move Insight · Destructive

Moves an insight to a different idea. Insights linked to a vote, or to a comment someone wrote on the portal, cannot be moved.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `ideaID` (`string`, required): The ID of the idea to move the insight to. To discover valid IDs, call the `list_ideas` tool.
- `insightID` (`string`, required): The ID of the insight to move. To discover valid IDs, call the `list_insights` tool.

Example input: `{"ideaID":"<ideaID>","insightID":"<insightID>"}`

### `cannymcp_remove_user_from_company`

Remove User From Company · Destructive

Removes a user's membership from the given company.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `companyID` (`string`, required): The ID of the company to remove the user from. To discover valid IDs, call the `list_companies` tool.
- `userID` (`string`, required): The ID of the user to remove. To discover valid IDs, call the `list_users` tool with `include: ["ids"]`.

Example input: `{"companyID":"<companyID>","userID":"<userID>"}`

### `cannymcp_unlink_opportunity`

Unlink Opportunity · Destructive

Unlinks a Salesforce opportunity or HubSpot deal from an idea. Provide exactly one of `salesforceOpportunityID` or `hubspotDealID`.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `ideaID` (`string`, required): The ID of the idea to unlink the opportunity from. To discover valid IDs, call the `list_ideas` tool.
- `hubspotDealID` (`string`, optional): The HubSpot ID of the deal to unlink.
- `salesforceOpportunityID` (`string`, optional): The Salesforce ID of the opportunity to unlink.

Example input: `{"ideaID":"<ideaID>"}`

### `cannymcp_update_changelog_entry`

Update Changelog Entry · Destructive

Updates the content of an existing changelog entry. Only the fields you provide are changed; omitted fields stay the same. Use `update_changelog_entry_status` to change the entry status.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `entryID` (`string`, required): The ID of the changelog entry to update. Discover valid IDs via `list_changelog_entries`.
- `details` (`string`, optional): New details for the entry.
- `ideaIDs` (`array`, optional): Replaces the linked ideas on the entry with this list of idea IDs. Each idea must already be published to the portal. Pass an empty array to clear all linked ideas. Discover valid IDs via `list_ideas`.
- `labelIDs` (`array`, optional): Replaces the labels on the entry with this list of label IDs. Pass an empty array to clear all labels. Discover valid IDs via `list_changelog_labels`.
- `notifySubscribers` (`boolean`, optional): Whether to notify subscribers by email when the entry is published.
- `title` (`string`, optional): New title for the entry.
- `types` (`array`, optional): Replaces the types on the entry with this list. Pass an empty array to clear all types.

Example input: `{"entryID":"<entryID>"}`

### `cannymcp_update_changelog_entry_status`

Update Changelog Entry Status · Destructive

Transitions a changelog entry between draft, scheduled, and published states. Use `update_changelog_entry` to edit the content of an entry.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `entryID` (`string`, required): The ID of the changelog entry whose status to update. Discover valid IDs via `list_changelog_entries`.
- `entryStatus` (`string`, required): The target status. `published` publishes the entry (from draft or scheduled). `scheduled` schedules a draft for a future date, or reschedules an already-scheduled entry to a new date (requires `scheduledFor`). `draft` unpublishes a published entry or unschedules a scheduled entry. One of: `draft`, `scheduled`, `published`.
- `publishedOn` (`string`, optional): Optional when `entryStatus` is `published`. ISO 8601 date in the past to backdate the publish time. Defaults to now.
- `scheduledFor` (`string`, optional): Required when `entryStatus` is `scheduled`. ISO 8601 date in the future indicating when the entry should be auto-published.

Example input: `{"entryID":"<entryID>","entryStatus":"draft"}`

### `cannymcp_update_company`

Update Company · Destructive

Updates an existing company, looked up by its ID. Only the fields you supply are changed; omit a field to leave it untouched. Recurring revenue is updated via `spend` and `spendType` (`mrr` for monthly recurring revenue, `arr` for annual recurring revenue), which are all-or-nothing: provide both or neither. When asking a user for revenue, use the SaaS terms — e.g. "What's this company's ARR?". If the user gives a figure without saying whether it's MRR or ARR, ask before updating the company. If you have company syncing integrations in place (e.g. Hubspot, Salesforce, SSO Tokens, Canny Identify), fields updated here may later be overwritten.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `companyID` (`string`, required): The company's unique identifier. Discover valid IDs via the `list_companies` tool.
- `created` (`string`, optional): The date the company was created in your system, as an ISO 8601 date string (e.g. 2024-01-31T00:00:00.000Z).
- `customFields` (`object`, optional): Custom fields associated with the company, merged into any existing fields. Each field name (key) must be between 1 and 29 characters long; string values must be under 200 characters.
- `name` (`string`, optional): The company's name.
- `spend` (`number`, optional): The company's recurring revenue, in dollars — its MRR or ARR per `spendType`. Must be paired with `spendType`; provide both or neither.
- `spendType` (`string`, optional): Whether `spend` is monthly recurring revenue (`mrr`) or annual recurring revenue (`arr`). Must be paired with `spend`; provide both or neither. ARR is converted to a monthly amount (divided by 12) before being stored. One of: `mrr`, `arr`.

Example input: `{"companyID":"<companyID>"}`

### `cannymcp_update_group`

Update Group · Destructive

Updates a group's name and/or description. Omit fields to leave them untouched.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `group` (`string`, required): The ID of the group to update. Use `list_groups` tool to discover valid group IDs.
- `description` (`string`, optional): New description for the group.
- `name` (`string`, optional): New name for the group.

Example input: `{"group":"<group>"}`

### `cannymcp_update_idea`

Update Idea · Destructive

Updates an existing idea. Omit fields to leave them untouched.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `ideaID` (`string`, required): The ID of the idea to update. Discover valid IDs via `list_ideas`.
- `customFields` (`object`, optional): Map of custom-field IDs to new values. Custom field IDs are MongoDB ObjectIds — discover them via `list_idea_fields` (entries with source="custom"). Values must match the field type: strings for text/dropdown/date/url, numbers for number/rating/fibonacci, booleans for boolean, or arrays of strings for multiselect. Pass null as a value to clear that custom field.
- `description` (`string`, optional): New description for the idea. Pass null to clear the description.
- `include` (`array`, optional): Optional response fields to include. By default, user-related identifiers are omitted from the returned idea. Pass `["users"]` to include them.
- `owner` (`string`, optional): User ID of the new owner. The user must be an admin of this company. Discover valid IDs via `list_admins`. Pass null to unassign the owner.
- `status` (`string`, optional): Status ID to set on the idea. Discover valid IDs via `list_idea_statuses`. Cannot be cleared.
- `themes` (`array`, optional): Replaces the themes on the idea with this list of theme IDs. Discover valid IDs via `list_idea_themes`. Pass an empty array to clear all themes.
- `title` (`string`, optional): New title for the idea. Cannot be cleared (titles are required).

Example input: `{"ideaID":"<ideaID>"}`

### `cannymcp_update_insight`

Update Insight · Destructive

Updates an existing insight. Omit fields to leave them untouched. At least one of `companyID` or `userIDs` must remain set on the insight after the update. By default, user-related identifiers in the returned insight are omitted. Pass `include: ["users"]` to include them.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `insightID` (`string`, required): The ID of the insight to update. To discover valid IDs, call the `list_insights` tool.
- `companyID` (`string`, optional): New company ID the insight is attributed to. Pass `null` to clear it; note that if every attached user belongs to the same company, that company will be re-inferred and re-attached. To discover valid IDs, call the `list_companies` tool.
- `include` (`array`, optional): Optional response fields to include. By default, user-related identifiers are omitted from the returned insight. Pass `["users"]` to include them.
- `priority` (`string`, optional): New priority for the insight, or `null` to clear it. One of: `nice-to-have`, `important`, `must-have`, `no-priority`.
- `url` (`string`, optional): New source URL for the insight, or `null` to clear it.
- `userIDs` (`array`, optional): Replaces the users attributed to the insight with this list of user IDs. Pass an empty array to clear all users. To discover valid IDs, call the `list_users` tool.
- `value` (`string`, optional): New content for the insight. Cannot be cleared once the insight has content.

Example input: `{"insightID":"<insightID>"}`

### `cannymcp_update_portal_category`

Update Portal Category · Destructive

Updates the category of the provided idea. The idea must be published to the portal, and the category must belong to the idea's board.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `categoryID` (`string`, required): The ID of the category to set on the idea. Must belong to the idea's board. Pass `null` to clear the category. Discover valid IDs via `list_board_categories`.
- `ideaID` (`string`, required): The ID of the idea whose category to update. Discover valid IDs via `list_ideas`.

Example input: `{"categoryID":"<categoryID>","ideaID":"<ideaID>"}`

### `cannymcp_update_portal_comment`

Update Portal Comment · Destructive

Updates the text of an existing portal comment. Internal portal comments can only be updated by the user who authored them. Discover valid IDs via the `list_portal_comments` tool. By default, user-related identifiers in the returned comment are omitted. Pass `include: ["users"]` to include them. These are portal comments, distinct from the idea comments managed by the `list_comments` and `create_comment` tools.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `portalCommentID` (`string`, required): The ID of the portal comment to update. Discover valid IDs via the `list_portal_comments` tool.
- `value` (`string`, required): The new text content of the comment. Must not be empty.
- `include` (`array`, optional): Optional response fields to include. By default, user-related identifiers are omitted from the returned comment. Pass `["users"]` to include them.

Example input: `{"portalCommentID":"<portalCommentID>","value":"<value>"}`

### `cannymcp_update_portal_status`

Update Portal Status · Destructive

Updates the portal status (the public-facing status shown on the portal/roadmap) of the provided idea. The idea must be published to the portal.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `ideaID` (`string`, required): The ID of the idea whose portal status to update. Discover valid IDs via `list_ideas`.
- `commentValue` (`string`, optional): An optional comment to include with the status change. When `shouldNotifyVoters` is true, this is included in the email notification sent to voters.
- `portalStatusID` (`string`, optional): The ID of the portal status to set on the idea. Provide exactly one of `portalStatusID` or `portalStatusName`. Discover valid IDs via `list_portal_statuses`.
- `portalStatusName` (`string`, optional): The name of the portal status to set on the idea. Provide exactly one of `portalStatusID` or `portalStatusName`. Discover valid names via `list_portal_statuses`.
- `shouldNotifyVoters` (`boolean`, optional): Whether to notify voters of the idea about the status change. Defaults to false.

Example input: `{"ideaID":"<ideaID>"}`

### `cannymcp_update_view`

Update View · Destructive

Updates an existing view. Only the fields you provide are changed; omit a field to leave it untouched.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `viewID` (`string`, required): The ID of the view to update. Use `list_views` to discover valid view IDs.
- `fields` (`array`, optional): Replacement list of field to display as columns. Must include `title` as the first entry. To discover valid field IDs, call `list_idea_fields`.
- `filters` (`array`, optional): Replacement filter list. Use `list_idea_fields` and `list_idea_filtering_operations` to discover valid fields, conditions, and values.
- `filtersOperator` (`string`, optional): How to combine filters: `all` (AND) or `any` (OR). A view scoped to a segment cannot use `any`. One of: `all`, `any`.
- `groupBy` (`string`, optional): Field to group ideas by. Pass null to ungroup. One of: `hierarchy`, `owner`, `status`, `board`.
- `includeSubIdeas` (`boolean`, optional): Whether the view includes sub-ideas in addition to top-level ideas.
- `name` (`string`, optional): New name for the view. Default views cannot be renamed.
- `segmentID` (`string`, optional): The ID of a segment to scope this view’s segmentable metrics to (the default Insight, User, and Company Count and ARR factors, plus any score field that consumes one). Use the `list_segments` tool to discover IDs; only segments whose `objectType` is `company` can be applied, and not to a view whose `filtersOperator` is `any`. Pass null to unset the segment.
- `sort` (`object`, optional): Sort order for ideas.

Example input: `{"viewID":"<viewID>"}`

## Related

Other Customer Support connectors ([all 38](/agentkit/connectors/?category=customer-support)):

- [ServiceNow](/agentkit/connectors/servicenow/): Scalekit connector, OAuth, 112 tools
- [Zendesk](/agentkit/connectors/zendeskoauth/): Scalekit connector, OAuth, 137 tools
- [Jira Service Management](/agentkit/connectors/jiraservicemanagement/): Scalekit connector, OAuth, 72 tools


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |
