Canny MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CANNY_API_KEY | Yes | Your Canny.io API key | |
| CANNY_TIMEOUT | No | Request timeout in ms | 30000 |
| CANNY_BASE_URL | No | API base URL | https://canny.io/api/v1 |
| CANNY_MAX_RETRIES | No | Max retry attempts | 3 |
| CANNY_RATE_LIMIT_RPM | No | Requests per minute limit | 60 |
| CANNY_RATE_LIMIT_BURST | No | Burst limit | 10 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_boardsB | List all Canny boards accessible with the current API key |
| get_postsC | Get posts from a specific Canny board with optional filtering |
| get_postC | Get detailed information about a specific Canny post |
| search_postsC | Search for posts across Canny boards |
| create_postC | Create a new post in a Canny board |
| update_postC | Update an existing Canny post |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: create_post, get_post, update_post handle individual post lifecycle; get_boards lists boards; get_posts retrieves posts from a board; and search_posts searches across boards. No ambiguity exists between these operations.
All tools follow a consistent verb_noun pattern with snake_case naming (e.g., create_post, get_boards, update_post). The verbs are standard and predictable across the set.
With 6 tools, this server is well-scoped for managing Canny posts and boards. It covers core operations without being too sparse or bloated, fitting typical use cases efficiently.
The toolset provides solid CRUD coverage for posts (create, get, update, list, search) and board listing. A minor gap is the lack of delete_post or board management tools, but agents can still handle most workflows effectively.