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 分