@harkly/mcp

Harkly as tools for Claude Code, Claude Desktop, Cursor and anything else that speaks MCP: feedback posts, the support inbox, help articles, the changelog, customers and reports. Reads are on by default; writes are opt-in.

Claude Code

claude mcp add harkly --env HARKLY_API_KEY=hk_live_… -- npx -y @harkly/mcp

or in .mcp.json:

{
  "mcpServers": {
    "harkly": {
      "command": "npx",
      "args": ["-y", "@harkly/mcp"],
      "env": { "HARKLY_API_KEY": "hk_live_…" }
    }
  }
}

Get a key under Settings → API keys; give it the permissions the tools need (feedback:read, inbox:read, help:read, changelog:read, customers:read, org:read; the *:write ones for the write tools). Self-hosted: add HARKLY_API_URL.

Tools

| tool | what | |---|---| | list_boards | boards and the status pipeline | | list_posts | posts by board, status, search, sort | | get_post | one post with its comments | | list_conversations, get_conversation | the support inbox and one thread's messages | | search_help | help articles | | list_changelog | changelog entries and drafts | | find_customers | people by name or email, with attributes | | report | a module's numbers for the last N days |

With HARKLY_WRITE=1: create_post, set_post_status, comment_on_post, reply_to_conversation, draft_changelog. The API key's permissions still apply, and the server tells the model to confirm before writing.

Same CalVer as @harkly/js, @harkly/react and @harkly/cli.