Cuti-E MCP Server

Local setup required. This server has to be cloned and prepared on your machine before you register it in Claude Code.
1

Set the server up locally

Run this once to clone and prepare the server before adding it to Claude Code.

Run in terminal
cd ~/.claude/mcp-servers/cutie-mcp
npm install
2

Register it in Claude Code

After the local setup is done, run this command to point Claude Code at the built server.

Run in terminal
claude mcp add -e "CUTIE_API_KEY=${CUTIE_API_KEY}" cutie-mcp -- node "<FULL_PATH_TO_CUTIE_MCP>/dist/index.js"

Replace <FULL_PATH_TO_CUTIE_MCP>/dist/index.js with the actual folder you prepared in step 1.

Required:CUTIE_API_KEY+ 1 optional
README.md

MCP server for the Cuti-E admin API.

cutie-mcp

MCP server for the Cuti-E admin API. Manage conversations, reply to feedback, and monitor the platform from Claude Code or any MCP-compatible client.

Features

  • List and filter conversations (by status, priority, app, category, search)
  • View conversation details with full message history
  • Send replies and internal notes
  • Update conversation status, priority, and assignment
  • List apps and view app configuration
  • Dashboard analytics (conversation stats, response times, breakdowns, trends)
  • Team member listing
  • Customer/team info
  • Active user stats (DAU/WAU/MAU) per app or across all apps

Installation

cd ~/.claude/mcp-servers/cutie-mcp
npm install

Configuration

Environment Variables

Variable Required Description
CUTIE_API_KEY Yes Admin API key (ck_live_...)
CUTIE_API_URL No API base URL (default: https://api.cuti-e.com)

Generate an API Key

# Using session auth (from admin dashboard login)
curl -X POST https://api.cuti-e.com/v1/admin/api-keys \
  -H "Authorization: Bearer <session_token>" \
  -H "Content-Type: application/json" \
  -d '{"name": "Claude MCP"}'

The response includes the full api_key (only shown once). Store it securely.

MCP Configuration

Add to your .mcp.json:

{
  "mcpServers": {
    "cutie-mcp": {
      "type": "stdio",
      "command": "node",
      "args": ["/Users/post/.claude/mcp-servers/cutie-mcp/index.js"],
      "env": {
        "CUTIE_API_KEY": "ck_live_..."
      }
    }
  }
}

Tools

Conversations

Tool Parameters Description
list_conversations status, priority, app_id, search, category, assigned_to, limit, offset, sort List conversations with optional filters. Returns status, priority, unread counts, and pagination.
get_conversation conversation_id* Get a single conversation with full message history and tags.
send_reply conversation_id, message, is_internal_note Send a visible reply or internal admin note.
update_conversation conversation_id*, status, priority, assigned_admin_id, title, category Update one or more fields on a conversation.
delete_conversation conversation_id* Close/delete a conversation.

list_conversations filter values:

  • status: open · in_progress · waiting_user · waiting_admin · resolved · closed
  • priority: low · normal · high · urgent
  • category: bug · feature · question · feedback · other
  • sort: last_message (default) · created · updated

Apps

Tool Parameters Description
list_apps List all registered apps with usage stats.
get_app app_id* Get app details, configuration, and notification settings.

Analytics

Tool Parameters Description
get_dashboard period Conversation stats, response times, category/status/priority breakdowns, daily trends, and team activity. period: 7d · 30d (default) · 90d · all
get_active_users app_id*, period DAU/WAU/MAU for a specific app. period: day · week · month (default: all three)
get_active_users_all_apps period Active user counts aggregated across all apps.
get_sentiment_insights period, app_id AI-classified sentiment breakdown (positive/neutral/negative) by app and category. period: 7d · 30d · 90d · all

Feature Requests

Tool Parameters Description
get_feature_requests status, app_id, search, limit AI-extracted feature requests ranked by vote count. status: new · acknowledged · planned · completed · declined
update_feature_request request_id*, status, title Update the status or title of a feature request.
merge_feature_requests target_id, source_id Merge a duplicate into a target — combines votes and linked conversations, deletes source.

Team & Account

Tool Parameters Description
list_team List all team members with their roles.
get_customer Get team/customer info including tier, mascot settings, and brand color.

* Required parameter

Security

  • API keys are bearer tokens with full admin access to the team's data
  • Keys use SHA-256 hashing (never stored in plain text)
  • Keys can be revoked instantly via DELETE /v1/admin/api-keys/:keyId
  • Optional expiry via expires_in_days parameter at creation
  • Never commit API keys to git -- use environment variables

Tools (16)

list_conversationsList conversations with optional filters.
get_conversationGet a single conversation with full message history and tags.
send_replySend a visible reply or internal admin note.
update_conversationUpdate one or more fields on a conversation.
delete_conversationClose/delete a conversation.
list_appsList all registered apps with usage stats.
get_appGet app details, configuration, and notification settings.
get_dashboardConversation stats, response times, category/status/priority breakdowns, daily trends, and team activity.
get_active_usersDAU/WAU/MAU for a specific app.
get_active_users_all_appsActive user counts aggregated across all apps.
get_sentiment_insightsAI-classified sentiment breakdown by app and category.
get_feature_requestsAI-extracted feature requests ranked by vote count.
update_feature_requestUpdate the status or title of a feature request.
merge_feature_requestsMerge a duplicate into a target.
list_teamList all team members with their roles.
get_customerGet team/customer info including tier, mascot settings, and brand color.

Environment Variables

CUTIE_API_KEYrequiredAdmin API key (ck_live_...)
CUTIE_API_URLAPI base URL

Configuration

claude_desktop_config.json
{"mcpServers": {"cutie-mcp": {"type": "stdio", "command": "node", "args": ["/Users/post/.claude/mcp-servers/cutie-mcp/index.js"], "env": {"CUTIE_API_KEY": "ck_live_..."}}}}

Try it

List all open conversations with high priority.
Show me the dashboard analytics for the last 30 days.
Get the active user stats for my main application.
Find all feature requests with the status 'new' and summarize them.
Send a reply to conversation ID 123 saying 'We are looking into this issue'.

Frequently Asked Questions

What are the key features of Cuti-E?

Filter and manage customer conversations with full message history. Access platform analytics including response times and daily trends. Track active user statistics (DAU/WAU/MAU) across applications. Manage and merge AI-extracted feature requests. Retrieve team member roles and customer account configuration.

What can I use Cuti-E for?

Customer support teams managing multiple app feedback channels. Product managers tracking feature request popularity and status. Platform administrators monitoring daily active user growth. Operations teams analyzing sentiment trends to improve product quality.

How do I install Cuti-E?

Install Cuti-E by running: cd ~/.claude/mcp-servers/cutie-mcp && npm install

What MCP clients work with Cuti-E?

Cuti-E works with any MCP-compatible client including Claude Desktop, Claude Code, Cursor, and other editors with MCP support.

Turn this server into reusable context

Keep Cuti-E docs, env vars, and workflow notes in Conare so your agent carries them across sessions.

Need the old visual installer? Open Conare IDE.
Open Conare