feat(tools): expand Canny API surface with 6 new tools and fix jira field mapping#5
Merged
Merged
Conversation
…ield mapping
Introduce tag lifecycle management (create, add-to-post, remove-from-post),
status change auditing, and changelog entry support as first-class MCP tools.
This brings total coverage from 24 to 30 tools across 7 toolsets.
New tools:
- canny_create_tag: tag creation on boards (discovery toolset)
- canny_add_post_tag / canny_remove_post_tag: post-tag association (posts toolset)
- canny_list_status_changes: status change audit trail (discovery toolset)
- canny_create_changelog_entry / canny_list_changelog_entries: changelog CRUD (new changelog toolset)
Infrastructure changes:
- Add CannyStatusChange, CannyChangelogEntry types and corresponding client methods
- Extend ToolsetName union with 'changelog' for granular toolset filtering
- Add 6 client methods with retry logic via existing request() pipeline
Bug fix:
- Correct CannyPost.jira type from CannyJiraIssue[] to { linkedIssues: CannyJiraIssue[] }
to match actual Canny API response shape, resolving "post.jira.map is not a function"
crash in ResponseTransformer.compactPost and jiraLinkStatus resource
Test and documentation updates reflect new tool counts (30 total, 12 read-only, 18 write).
AwolDes
reviewed
May 11, 2026
| const response = await this.request<{ | ||
| entries: CannyChangelogEntry[]; | ||
| hasMore: boolean; | ||
| }>('changelog_entries/list', params); |
There was a problem hiding this comment.
Hey @Ompragash I'm using your MCP to link up Canny and wanted to let you know that this API is out of date and it should be https://canny.io/api/v1/entries/list (https://developers.canny.io/api-reference#entries)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Introduce tag lifecycle management (create, add-to-post, remove-from-post), status change auditing, and changelog entry support as first-class MCP tools. This brings total coverage from 24 to 30 tools across 7 toolsets.
New tools:
Infrastructure changes:
Bug fix:
Test and documentation updates reflect new tool counts (30 total, 12 read-only, 18 write).