Claude (MCP)

Klero exposes a Model Context Protocol (MCP) server, letting Claude Desktop and other MCP-compatible AI clients read and write your feedback, roadmap, changelog, and surveys directly from a conversation.

Prerequisites

• A Klero project
• A Project API key — go to Settings → API Keys and create one

Connecting Claude Desktop

Add Klero to your Claude Desktop configuration file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "klero": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://YOUR-PROJECT.klero.ai/mcp",
        "--header",
        "Authorization: Bearer YOUR_API_KEY"
      ]
    }
  }
}

Replace YOUR-PROJECT with your project slug and YOUR_API_KEY with the key you created.

Restart Claude Desktop. You should see Klero appear in the tools panel.

Available Tools

Feedback

Tool	Description
list_feedback_boards	List all feedback boards in your project
list_feedback_items	Search and filter feedback items
get_feedback_item	Get full details and comments for an item
create_feedback_item	Create a new feedback item
update_feedback_item	Update status, title, or description
list_comments	List comments on a feedback item
create_comment	Post a comment on a feedback item

Roadmap

Tool	Description
list_roadmaps	List public roadmaps

Changelog

Tool	Description
list_changelogs	List changelog entries
create_changelog	Draft a new changelog entry
update_changelog	Edit a draft entry
publish_changelog	Publish a changelog entry

Surveys

Tool	Description
list_surveys	List surveys
get_survey	Get survey details and questions
create_survey	Create a new survey
update_survey	Update a survey
get_survey_responses	Fetch survey responses
get_survey_analytics	Get aggregated survey analytics

Example Prompts

What are the top 10 most-voted feedback items this month?

Create a changelog entry summarising the feedback items we shipped this week.

Find all feedback items with status "in review" on the Feature Requests board.

Post a comment on feedback item <ulid> saying we're planning this for Q3.