Evermuse

com.evermuse由 evermuse.com 发布官方发布者v1.0.1更新于 Oct 24, 2026

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

已验证Streamable HTTP可网页运行效率与工作流知识与记忆

概览

AI 生成的概览

Evermuse 将 AI 助手连接到客户研究知识库，使其能检索访谈、通话和反馈，并用可溯源的客户证据支撑产品工作。

可以做什么
检索并阅读客户证据：执行证据搜索，打开单条记录、来源和对话，并附回原始通话或反馈的引用。获取产品上下文：列出产品、产品摘要和项目，读取竞品列表、竞品能力与机会。运行产品工作流：客户研究、PRD、简报、功能规格、用户画像、用户故事、竞品分析和对话摘要，均返回方法论与证据支撑。处理塑造笔记：读取、创建和更新笔记。写回 Evermuse：添加来源，添加或更新信号。读取内置的指导技能。
适用场景
适合希望规格、开发计划、PR 评审、路线图和研究结论基于真实客户原话而非泛泛模型输出的产品经理和团队，且每条结论都能链接到来源对话。当客户访谈、通话和反馈已存放在 Evermuse 中时最为适用。
运行要求
通过 streamable HTTP 访问的远程 MCP 端点，无需本地安装包。需要 Evermuse 账户，使用 OAuth 授权（推荐）或在 Authorization 请求头中提供 API 密钥。每次调用都必须选定一个产品（Product），项目（Project）可选。README 还介绍了捆绑技能和命令的 Claude Code 与 Cursor 插件。
安装前请注意
需要 OAuth 授权或 Authorization 请求头中的 API 密钥，应将该凭据视为敏感信息。多个工具会写入知识库（add_source、add_signals、update_signals、create_shaping_note、update_shaping_note），助手操作可能改动已存数据。客户对话和引语会发送给 AI 客户端并出现在输出中，请留意共享的内容。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Evermuse，将其添加到工作区。
  2. 连接 所需的 凭据。它们会被私密存储，绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/com.evermuse%2Fevermuse/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。

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

README

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

bash
# Add this repo as a plugin marketplace, then install the pluginclaude plugin marketplace add Usermuse/em-pluginclaude plugin install evermuse@evermuse

Or point at a local checkout during development:

bash
claude plugin marketplace add /path/to/em-pluginclaude 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 CodeCursor
/evermuse:spec <feature>/write-feature-spec
/evermuse:research <question>/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:

  1. 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.
  2. Work — apply the skill's method, shaped by what the evidence says.
  3. Cite — every customer-derived claim carries a source badge and a [^n] footnote.
  4. 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

OAuth clients — Claude Code and Cursor included — are served these 27 tools:

GroupTools
Guidancefind_skills · read_skills
Product contextget_products · get_product_summary · get_projects
Workflow (start here when the job matches)customer_research · create_prd · write_brief · write_feature_spec · user_personas · user_stories · competitor_analysis · summarize_conversation
Evidencesearch · view_item
Sourcesfind_sources · read_source
Competitors & opportunitieslist_competitors · get_competitor_capabilities · get_opportunities
Shaping notesget_shaping_notes · read_shaping_note · create_shaping_note · update_shaping_note
Writesadd_source · add_signals · update_signals

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.

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, competitor-analysis, sentiment-analysis
  • GTM & growth: gtm-strategy, beachhead-segment, ideal-customer-profile, competitive-battlecard, positioning-and-messaging, north-star-metric
  • Onboarding & meta: setup-evermuse, initial-report, list-capabilities, schedule-new-ingestion-tasks

skills/ is generated from the Evermuse monorepo (yarn sync:em-plugin). Do not edit it here — open an issue instead, and the change is made upstream and synced down.

Tips

  • The plugin works best when your project's CLAUDE.md mentions the product name — it helps the agent pick the right Evermuse Product automatically. (Optional.)
  • If Evermuse isn't connected, skills still run but produce ⚠ ungrounded output and tell you to authorize the MCP — they never fake evidence.
  • Secondary Evermuse assets (the AI-generated roadmap, shaping notes, competitor list, research questions) are used sparingly and always labeled — customer conversations are the source of truth.

Contributing

  • skills/ is generated. Request changes upstream in the Evermuse monorepo; a sync PR brings them here. Commands, manifests, the README and the logo are hand-written and edited here.
  • logomark.svg must keep this path. The setup-evermuse skill loads it from https://cdn.jsdelivr.net/gh/Usermuse/em-plugin@main/logomark.svg, so moving or renaming it breaks the setup header for every user.
  • Bump the version before merging a sync PR. Cursor re-reviews every update, so each release needs version raised in .claude-plugin/plugin.json, .cursor-plugin/plugin.json and .claude-plugin/marketplace.json.

Credits

Built on phuryn/pm-skills (MIT) and github/spec-kit (MIT). See ATTRIBUTION.md. Licensed MIT — see LICENSE.

来源：README.md，提交 ec5c36e

工具

0
该服务器需要登录，因此 SourceWeft 无法在没有账号的情况下读取其工具，也未收录。已连接账号所能看到的内容可能因账号及其权限而异。

版本历史

2
  1. v1.0.1最新Oct 5, 2026
  2. v1.0.0Sep 16, 2026

评分

已满足适用检查项的 85%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分