Docs

MCP server

Your coding agent can see what customers asked for, and ship it.

Install#

Create a key under Install & connect → API keys, then:

Claude Code

claude mcp add shipnoted \
  -e SHIPNOTED_API_KEY=snk_your_key \
  -e SHIPNOTED_URL=https://shipnoted.com \
  -e SHIPNOTED_PROJECT=your-slug \
  -- npx -y shipnoted-mcp

Cursor, Windsurf, Claude Desktop (JSON)

{
  "mcpServers": {
    "shipnoted": {
      "command": "npx",
      "args": ["-y", "shipnoted-mcp"],
      "env": { "SHIPNOTED_API_KEY": "snk_your_key", "SHIPNOTED_URL": "https://shipnoted.com", "SHIPNOTED_PROJECT": "your-slug" }
    }
  }
}

It speaks the Model Context Protocol over stdio, has no dependencies, and runs on your machine; the key never goes anywhere but to Shipnoted.

Tools#

project_infoWhich project this is, with counts. A good first call.read only

top_feedbackThe most-voted requests, to decide what to build.read only

search_feedbackSearch by words or by customer group (segment).read only

segmentsThe customer groups that voted, with votes and revenue.read only

get_requestOne request: text, votes, revenue, linked issues, comments.read only

themesRequests grouped by meaning, ranked by revenue.read only

loop_statusShipped, median days to ship, people told, pull requests waiting.read only

list_releasesRecent releases and their status.read only

draft_releaseWrite a draft from a list of changes. Never published.changes data

set_feedback_statusMove a request on the roadmap.changes data

file_requestFile a request from a support conversation, safely retried.changes data

publish_releaseCreate and publish a release.visible to customers

publish_draftPublish an existing draft. Voters are emailed.visible to customers

update_releaseEdit a release; changes to a published one go live.visible to customers

comment_on_requestReply publicly, or leave an internal note.visible to customers

Things to ask#

“What are my three most requested features, and how much revenue is behind each?”
“What did the beta customers ask for?” (it uses the segments)
“Draft release notes for what I merged this week, then show me before publishing.”
“SN-42 shipped in the last release: move it and tell the people who asked.”

Safety#

Tools are marked so a client can ask before running them: read-only ones have readOnlyHint, and the ones that change what customers see or get emailed have destructiveHint. Give the agent a key with only the scopes it needs. For an agent that should only look, make a Read only key and the write tools will simply be refused.