Skip to main content

Documentation Index

Fetch the complete documentation index at: https://sleekplan.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

The Sleekplan MCP server exposes your entire workspace to any compatible AI client. Once connected, you can ask your AI assistant to find feedback, create changelog entries, tag items, look up users, run surveys, and more — all in natural language, without switching to the Sleekplan dashboard. The server is centrally hosted at https://mcp.sleekplan.com/mcp — nothing to install locally.

Before you connect

  • The MCP server uses OAuth 2.1 with dynamic client registration. On first connection, your AI client opens a browser window where you sign in to your Sleekplan account and select the workspace to authorize. Subsequent connections are authenticated automatically.
  • The server supports Streamable HTTP transport. Clients that only support the older SSE transport can use mcp-remote as a bridge (see the Others tab below).
  • Each connection is scoped to a single workspace. To connect multiple workspaces, add a separate MCP server entry for each one.

Setup

Open Claude settings, go to Connectors, and add Sleekplan. Alternatively, add the following to your claude_desktop_config.json:
{
  "mcpServers": {
    "sleekplan": {
      "url": "https://mcp.sleekplan.com/mcp"
    }
  }
}
Restart Claude Desktop after saving the file. On the next launch, Claude will prompt you to authorize your Sleekplan account.

Available tools

All tools and their parameters are automatically discovered by your AI client — you do not need to configure them manually. Ask your assistant in natural language and it will select the appropriate tool.
ResourceTools
Feedbacklist_feedback, create_feedback, get_feedback, update_feedback, delete_feedback, get_feedback_stats, get_similar_feedback, merge_feedback, tag_feedback
Commentslist_comments, create_comment, update_comment, delete_comment
Changeloglist_changelog, create_changelog, get_changelog, update_changelog, delete_changelog
Surveyslist_surveys, get_survey, create_survey, update_survey_name, update_survey_questions, get_survey_summary, get_survey_question_feed, list_survey_responses, get_survey_response
Voteslist_votes, get_voters
Userslist_users, get_user, get_user_segment
Topicslist_topics, list_sub_topics
Tagslist_tags, create_tag, delete_tag
Workspacelist_feedback_types, list_feedback_statuses, get_category_template, list_admins, list_segments

FAQ

Any MCP-compatible client works with the Sleekplan MCP server. This includes Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, and any other tool that supports the Model Context Protocol. Clients without native Streamable HTTP support can use mcp-remote as a bridge.
Each MCP connection is scoped to a single workspace, selected during the OAuth authorization flow. To connect more than one workspace, add a separate MCP server entry for each one in your client configuration, giving each a distinct name (for example, sleekplan-acme and sleekplan-beta).
The MCP server uses your Sleekplan account permissions. You can perform the same actions through the MCP server as you can through the Sleekplan admin dashboard — no more, no less.
Yes. Authentication uses OAuth 2.1 with PKCE. Your Sleekplan credentials are never shared with the AI client — the client only receives an access token scoped to the workspace you authorized. All communication between your client, the MCP server, and Sleekplan happens over HTTPS.
Clear your cached authentication tokens in the AI client and reconnect. This forces a fresh OAuth flow and resolves most connection issues. If the problem persists, contact support@sleekplan.com.