Evermuse

Name: Evermuse
Author: Usermuse

作者：Usermuse版本 1.0.1i★ –i在云端运行

注册名称com.evermuse/evermuse

安装

概览

作者提供的说明（英文原文）

Search your customer interviews, calls, feedback, competitor intel and roadmap from any AI agent.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 0 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在云端运行
传输方式: Streamable HTTP
分类: 搜索与 AI 记忆

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 0 项
在作者的服务器上运行：你向它提出的内容会经过他们的服务器。
注册中心没有列出需要填写的密钥。

你需要

在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

适用于网页版、桌面版和手机版 Claude：

打开 Settings → Connectors
点击 Add custom connector
粘贴下面的地址，然后点击 Add
如果要求登录，请登录作者的服务

https://api.evermuse.com/api/mcp

在终端中运行这条命令

claude mcp add --transport http evermuse https://api.evermuse.com/api/mcp

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "evermuse": {
      "url": "https://api.evermuse.com/api/mcp"
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "evermuse": {
      "type": "http",
      "url": "https://api.evermuse.com/api/mcp"
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

ChatGPT 只能连接互联网上的服务器：

打开网页版 ChatGPT → Settings → Connectors (Apps)
点击 Create 或 Add（部分套餐需要先在 Advanced 中开启 Developer mode）
粘贴下面的地址，起个名字，然后保存
如果要求登录，请登录作者的服务

https://api.evermuse.com/api/mcp

菜单名称可能因套餐和版本不同而略有差异。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

我们还没有读取这个服务器的工具列表；我们会轮流检查各个端点。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

! 注意
作者与仓库一致
发布者（evermuse.com）不是仓库所有者（Usermuse）；可能是其他人代为上架的
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
… 尚未检查
端点有响应
尚未检查；我们会轮流检查各个端点
… 尚未检查
使用 OAuth 登录
尚未检查；我们会轮流检查各个端点
… 尚未检查
工具描述中没有隐藏指令
尚未检查；我们会在检查端点时读取工具列表

与“搜索与 AI 记忆”中的其他服务器比较i

星标数多于此分类中其他 7231 个服务器的 0%
发布到注册中心的时间比此分类中其他 7231 个服务器的 54% 更新
基础检查结果等于或优于此分类中其他 7231 个服务器的 37%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Evermuse 安全吗？

它在 1 项适用的基础检查中通过了 0 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在作者的云端运行。通过互联网连接，无需安装，但你发送的内容会经过作者的服务器。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（1.0.1）于31天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接，所以接受远程 MCP 服务器的应用也可以使用，例如开启开发者模式的 ChatGPT。

有什么可以替代它？

同一分类中有：Context7, Codebase Memory, Exa

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Context7

作者：upstash

Up-to-date docs for AI agents

电脑或云端★ 64,224MIT3天前更新

安装

Codebase Memory

作者：DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

在你的电脑上运行★ 48,148MIT20天前更新

安装

Exa

作者：exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

在云端运行★ 5,213MIT44天前更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Evermuse for Claude Code and Cursor

Make your AI agent speak with the voice of your customers.

Evermuse is a plugin for Claude Code and Cursor that turns everyday product work — specs, dev plans, research, roadmaps, gap analyses, PR reviews — into deliverables grounded in real customer evidence. Instead of plausible-sounding generic answers, you get verbatim quotes, real needs, and actual pain points, each with a source link back to the conversation it came from. And the important things you produce get saved back into Evermuse, so your knowledge base compounds.

It combines proven PM/research methods (adapted from pm-skills) and spec-driven-development discipline (adapted from spec-kit) with the Evermuse MCP, which searches your recorded calls, interviews, and feedback.

What changes after you install it

Ask *"what do customers think about our onboarding?"* and instead of a guess you get:

Short answer: Onboarding friction centers on manual data entry — 7 mentions across 5 accounts, mostly frustrated.

### Theme 1 — Re-keying data by hand (7 mentions / 5 accounts)

> "We lose half a day every week re-keying this into the spreadsheet." — Dana K., Acme onboarding call, 12 May 2025 · View in Evermuse [^1]

Every spec gets a Customer Evidence section. Every dev plan opens with the customer quotes that justify it. Every PR review checks the diff against what customers literally asked for. That's the difference.

Install

Claude Code

# Add this repo as a plugin marketplace, then install the plugin

claude plugin marketplace add Usermuse/em-plugin claude plugin install evermuse@evermuse

Or point at a local checkout during development:

claude plugin marketplace add /path/to/em-plugin

claude plugin install evermuse@evermuse

Cursor

Install from the Cursor Marketplace, or add just the MCP server with a one-click deeplink:

Add Evermuse to Cursor

The Cursor plugin ships the skills and the MCP server.

How invocation differs between the two clients. In Claude Code, skills auto-activate — you describe the task in plain language and the right skill fires. Cursor works differently: skills are invoked explicitly, by typing /skill-name in chat or @skill-name to attach one as context. So in Cursor the skill name *is* the command:

Claude Code	Cursor
`/evermuse:spec`	`/write-feature-spec`
`/evermuse:research`	`/customer-research`
"write a spec for bulk CSV export" (auto-activates)	`/write-feature-spec` (explicit)

Because Cursor won't auto-fire a skill, the short aliases matter more there, not less — so Cursor gets its own command layer in cursor-commands/:

/spec        /dev-plan     /research     /setup      /save

/discover /brainstorm /pricing /strategy /plan-launch …28 in total

Each carries Cursor's name / description frontmatter. The Claude versions in commands/ use a different frontmatter shape plus $ARGUMENTS, which Cursor does not support, so the two directories are kept separate and each client reads its own.

Six Claude commands are deliberately not duplicated — business-model, gap-analysis, release-notes, review-pr, test-scenarios and value-proposition share a name with a skill that already does the same job, so in Cursor you invoke those as /gap-analysis etc. directly and a duplicate command would only make the / list ambiguous.

Authenticate the MCP

The plugin bundles the Evermuse MCP server (https://api.evermuse.com/api/mcp). Before the skills can ground anything, connect it:

Claude Code — OAuth (recommended): run /mcp in an interactive session and authorize evermuse.
Cursor — OAuth: open Settings → MCP and authorize evermuse. Cursor registers itself dynamically (DCR), so there's no client ID to configure.
API key (either client): add an Authorization header for the evermuse server in your MCP settings.

Then run `/evermuse:setup` to pick your Product and confirm grounding works. (A Product is required for every Evermuse call; a Project like Discovery/Support/Sales is optional and only needed when you're focused on one research effort.)

Quickstart

/evermuse:setup                      # connect + pick your product

/evermuse:research what do customers think about pricing? /evermuse:spec bulk CSV export for the reporting page /evermuse:dev-plan specs/bulk-csv-export/spec.md /evermuse:review-pr 482

The doctrine (how grounding works)

Every skill follows Ground → Work → Cite → Save:

Ground — verify the right Product, then run 2–4 differently-worded searches (declaring a *nature*: evidence = customer voice, context = market, guidance = company strategy) plus verbatim quotes.
Work — apply the skill's method, shaped by what the evidence says.
Cite — every customer-derived claim carries a source badge and a [^n] footnote.
Save — offer to persist the deliverable back into Evermuse via add_source.

The full doctrine lives in the using-evermuse skill, which every other skill defers to.

The MCP tools

The submitted default cloud OAuth configuration exposes these 27 tools:

Group	Tools
Read-only: guidance	`find_skills` · `read_skills`
Read-only: product context	`get_products` · `get_product_summary` · `get_projects`
Read-only: workflow (start here)	`customer_research` · `create_prd` · `write_brief` · `write_feature_spec` · `user_personas` · `user_stories` · `competitor_analysis` · `summarize_conversation`
Read-only: evidence and sources	`search` · `view_item` · `find_sources` · `read_source`
Read-only: internal assets	`list_competitors` · `get_competitor_capabilities` · `get_opportunities` · `get_shaping_notes` · `read_shaping_note`
Write: additive	`add_source` · `add_signals` · `create_shaping_note`
Write: overwrites existing data (destructive)	`update_signals` · `update_shaping_note`

Workflow tools are read-only despite their imperative names: create_prd creates nothing — you write the document, and it is stored only if you then call a write tool.

Not every workspace gets exactly this list. Workspaces with shaping writes disabled don't get create_shaping_note / update_shaping_note, local-storage workspaces get only the guidance tools from the cloud endpoint, and other feature flags can add tools. tools/list is the authority for what a given workspace is served.

A workflow tool runs the job's first grounding step and returns the methodology, so start from one when it matches the task rather than reaching straight for search. Every product-scoped call takes product_id as a parameter — there is no session to switch.

Tool annotations

Every tool sets all four MCP tool annotations explicitly to true or false, plus a title.

Tool(s)	readOnlyHint	destructiveHint	idempotentHint	openWorldHint	Why
The 22 read-only tools: `find_skills` · `read_skills` · `get_products` · `get_product_summary` · `get_projects` · `customer_research` · `create_prd` · `write_brief` · `write_feature_spec` · `user_personas` · `user_stories` · `competitor_analysis` · `summarize_conversation` · `search` · `view_item` · `find_sources` · `read_source` · `list_competitors` · `get_competitor_capabilities` · `get_opportunities` · `get_shaping_notes` · `read_shaping_note`	`true`	`false`	`true`	`false`	Retrieve guidance or authorized workspace data. They never create, overwrite, delete or publish the user's sources, signals or notes.
`add_source`	`false`	`false`	`false`	`true`	Adds a source to the caller's workspace and queues ingestion; the response confirms submission, not completion. Meeting imports can fetch a caller-supplied public HTTPS media URL (`media.url`), which is why it is open-world. Meeting and communication imports deduplicate on `external_source` + `external_id`, but note, document and spreadsheet modes don't, so a repeated call can create another source. It never overwrites an existing source.
`add_signals`	`false`	`false`	`true`	`false`	Adds up to 100 signals to an existing source. Replays are deduplicated on source, type and content, so repeating a call creates nothing new.
`create_shaping_note`	`false`	`false`	`false`	`false`	Creates a new shaping note and never modifies an existing one. Repeating the call creates a second note.
`update_signals`	`false`	`true`	`false`	`false`	Overwrites the passed fields on up to 100 existing signals (`null` clears an optional title or attribution). Signals have no version history. Repeating a title, content or type update advances the embedding revision and queues embedding work again, so a repeat has further effects.
`update_shaping_note`	`false`	`true`	`false`	`false`	Replaces each passed field outright, `content` and `tags` included. Every successful update, a repeat included, creates a new version, so it is not idempotent. Version history allows recovery, but the current fields are still overwritten.

Idempotency here means a repeated identical call has no further effect, not that the data can't change between calls. Every tool except add_source works only on Evermuse guidance or the caller's own workspace data (hosted storage and embedding services included); add_source can also download a media file from a URL the caller supplies. The third-party proxy tools (find_tool / call_tool) are not served to OAuth clients. No tool on this surface renders UI.

Commands

Cursor — 28 plain-Markdown commands in cursor-commands/. Same short names as below, without the evermuse: prefix (/spec, /dev-plan, /research). The six that duplicate a skill name are omitted; invoke those as /gap-analysis, /review-pr etc. directly.

Claude Code — the /evermuse:* commands in commands/, listed here:

Flagship: /evermuse:setup · spec · dev-plan · gap-analysis · review-pr · research · release-notes · save

Discovery & execution: discover · brainstorm · triage-requests · interview · write-prd · write-stories · plan-okrs · transform-roadmap · test-scenarios · pre-mortem · red-team-prd · meeting-notes · ship-check

Strategy, research & GTM: strategy · business-model · value-proposition · market-scan · pricing · research-users · competitive-analysis · analyze-feedback · plan-launch · growth-strategy · battlecard · market-product · north-star

Skills also auto-activate when you describe the task in plain language ("write a spec for…", "what are customers saying about…", "review this PR") — you don't have to remember command names.

Skills catalog

Foundation: using-evermuse (the doctrine + MCP mechanics every skill uses)
Flagships: write-feature-spec, development-plan, gap-analysis, review-pr, customer-research
Discovery: brainstorm-ideas, deep-dive, assumptions, prioritize-features, analyze-feature-requests, opportunity-solution-tree, interview-script, summarize-conversation
Strategy: product-strategy, product-vision, value-proposition, business-model, pricing-strategy, strategy-frameworks, strategy-red-team
Execution: create-prd, user-stories, brainstorm-okrs, outcome-roadmap, release-notes, test-scenarios, shipping-artifacts, daily-brief
Market research: user-personas, segmentation, customer-journey-map, market-sizing, `c

只显示了开头部分；其余内容请在仓库中阅读