Skip to main content
Glama
mailerlite

Canny MCP Server

by mailerlite

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CANNY_API_KEYYesYour Canny.io API key
CANNY_TIMEOUTNoRequest timeout in ms30000
CANNY_BASE_URLNoAPI base URLhttps://canny.io/api/v1
CANNY_MAX_RETRIESNoMax retry attempts3
CANNY_RATE_LIMIT_RPMNoRequests per minute limit60
CANNY_RATE_LIMIT_BURSTNoBurst limit10

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_boardsA

List all Canny boards accessible with the current API key

get_postsB

Get posts from a specific Canny board with optional filtering

get_postB

Get detailed information about a specific Canny post

search_postsB

Search for posts across Canny boards

create_postB

Create a new post in a Canny board

update_postB

Update an existing Canny post

get_categoriesA

Get all categories from a specific Canny board

get_commentsB

Get comments from a specific Canny post

get_usersC

Get users/authors from your Canny instance

get_tagsA

Get all tags from Canny boards (optionally filtered by board)

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 10 tools

Disambiguation4/5

Each tool targets a distinct resource or action, with clear separation between listing posts, getting a single post, and searching posts. The only minor ambiguity is between get_posts and search_posts, but their descriptions clarify the difference.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (get, search, create, update), making the API predictable and easy to navigate. There are no mixed conventions or vague verbs.

Tool Count5/5

Ten tools is well within the ideal range for a domain-specific server, covering boards, posts, comments, users, and tags without being overwhelming. Each tool is clearly scoped to a specific operation.

Completeness3/5

The tool set covers core read operations and post creation/update, but lacks delete functionality for posts and any comment write operations. Given Canny's feedback focus, missing vote or comment creation capabilities are notable gaps.

Maintenance

ActivityMaintained
ResponsivenessNo issues