Evermuse MCP server
2026년 11월 6일 커밋AI 에이전트가 고객 인터뷰, 통화 내용, 피드백 및 로드맵을 검색하여 제품 결과물을 실제 고객 근거에 기반하도록 지원합니다.
다른 이름 Usermuse/em-plugin, em-plugin
- 스타
- 0
- Tools
- 5
- 다운로드, 30일
- —
- 최신 버전
- 1.0.1
- 마지막 커밋
- 2026년 11월 6일
- 라이선스
- MIT
Evermuse MCP란?
Evermuse은(는) MCP server입니다. AI 에이전트가 고객 인터뷰, 통화 내용, 피드백 및 로드맵을 검색하여 제품 결과물을 실제 고객 근거에 기반하도록 지원합니다. 5개 도구를 제공합니다. 예: add_source, add_signals, create_shaping_note.
프로젝트 README에서 생성된 요약
Evermuse MCP server 정보
제품 관리자와 개발자는 Claude Code 또는 Cursor 내에서 Evermuse를 사용하여 기술적 결과물을 실제 고객 근거에 기반하여 작성할 수 있습니다. 이 MCP server는 AI 에이전트를 녹화된 통화, 인터뷰 및 피드백과 연결하여, 일반적인 가정이 아닌 실제 인용구와 구체적인 페인 포인트를 활용할 수 있게 합니다. 기존 지식 베이스를 검색하여 기능 명세서 작성, 개발 계획 수립, PR 리뷰 등의 작업에 필요한 컨텍스트를 제공합니다.
서버를 사용하려면 클라이언트에서 OAuth로 인증하거나 MCP 설정에서 API key를 제공하면 됩니다. 연결이 완료되면 /evermuse:setup 명령어를 사용하여 특정 제품을 선택합니다. 시스템은 연구 근거 확보, 작업 수행, 각주를 통한 출처 인용, 최종 결과물을 Evermuse 워크스페이스에 저장하는 엄격한 워크플로우를 따릅니다. 이를 통해 customer_research, write_feature_spec, review_pr와 같은 도구를 사용하여 모든 명세서나 로드맵이 실제 사용자 요구사항과 연결되도록 보장합니다.
활용 사례
- 1연구 기반의 기능 명세서 작성실제 고객 요구사항을 사용하여 에이전트에게 새로운 기능에 대한 기술 명세서 작성을 요청합니다.
- 2특정 주제에 대한 고객 감정 분석온보딩이나 가격 책정과 같은 제품의 특정 부분에 대해 사용자들이 무엇을 말하고 있는지 에이전트에게 질의합니다.
- 3사용자 요구사항에 따른 Pull Request 검증에이전트를 사용하여 코드 변경 사항이 원래의 고객 요청과 일치하는지 확인합니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
Evermuse MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 Evermuse MCP 설치
$ claude mcp add --transport http em-plugin https://api.evermuse.com/api/mcpCursor에 Evermuse MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"em-plugin": {
"url": "https://api.evermuse.com/api/mcp"
}
}
}VS Code에 Evermuse MCP 설치
.vscode/mcp.json
{
"servers": {
"em-plugin": {
"type": "http",
"url": "https://api.evermuse.com/api/mcp"
}
}
}VS Code CLI에 Evermuse MCP 설치
$ code --add-mcp '{"name":"em-plugin","type":"http","url":"https://api.evermuse.com/api/mcp"}'Codex에 Evermuse MCP 설치
$ codex mcp add em-plugin --url https://api.evermuse.com/api/mcpCodex config.toml에 Evermuse MCP 설치
~/.codex/config.toml
[mcp_servers.em-plugin] url = "https://api.evermuse.com/api/mcp"
Gemini CLI에 Evermuse MCP 설치
$ gemini mcp add -s user --transport http em-plugin https://api.evermuse.com/api/mcpGemini settings.json에 Evermuse MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"em-plugin": {
"url": "https://api.evermuse.com/api/mcp",
"type": "http"
}
}
}Evermuse MCP 도구 5
README에서 감지됨add_sourceadd_signalscreate_shaping_noteupdate_signalsupdate_shaping_note
| add_source | — | |
| add_signals | — | |
| create_shaping_note | — | |
| update_signals | — | |
| update_shaping_note | — |
자동 검사
2026년 11월 14일에 실행됨전체 보고서 →아직 인증되지 않았습니다. 서버는 80점 이상의 점수, 심각한 결함 없음, 그리고 검사에 충분한 데이터를 갖추어야 합니다. 검사 방식 · 점수를 높이기 위해 수정할 항목
- 소스 저장소 연결 및 접근 가능usermuse/em-plugin is public and reachablegithub.com/usermuse/em-plugin ↗통과
- 패키지가 이 저장소를 소스로 명시검사되지 않음
- 빌드 출처(Sigstore 증명)검사되지 않음
- 오픈 소스 라이선스 (OSI)MITspdx.org/licenses/MIT.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-11-06github.com/usermuse/em-plugin ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음검사되지 않음
- 패키지 및 해당 종속성에 중요한 보안 권고 없음검사되지 않음
- 모델에 대한 숨겨진 지침 없음5 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨No tool named like delete, drop or exec통과
- 원격 엔드포인트가 MCP 핸드셰이크에 응답HTTPS endpoint answered 401 (sign-in required)통과
README
GitHub에서 보기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:
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 <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
/mcpin 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
Authorizationheader for theevermuseserver 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,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.mdmentions 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.- The setup header inlines
logomark.svg. Thesetup-evermuseskill embeds the SVG markup directly rather than loading it from a URL, so if the logomark changes, update the inline copy in that skill too. - Bump the version before merging a sync PR. Cursor re-reviews every update, so each release
needs
versionraised in.claude-plugin/plugin.json,.cursor-plugin/plugin.json,.codex-plugin/plugin.jsonand.claude-plugin/marketplace.json.
Credits
Built on phuryn/pm-skills (MIT) and github/spec-kit (MIT). See ATTRIBUTION.md. Licensed MIT — see LICENSE.
Evermuse MCP 질문
Evermuse MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add --transport http em-plugin https://api.evermuse.com/api/mcp를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
Evermuse MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
Evermuse MCP는 어떤 도구를 제공하나요?
5개 도구를 제공합니다. 예: add_source, add_signals, create_shaping_note, update_signals, update_shaping_note.
Evermuse MCP 인증은 어떻게 하나요?
Claude Code 또는 Cursor에서는 OAuth(권장)를 사용할 수 있으며, MCP 설정에 Authorization 헤더를 추가하여 API key를 제공할 수도 있습니다.
Evermuse는 Claude Code 및 Cursor와 호환되나요?
네, Evermuse는 Claude Code 및 Cursor 전용으로 설계된 플러그인이며, 각 환경에 맞는 호출 방식을 제공합니다.
AI가 생성한 결과물을 Evermuse에 다시 저장할 수 있나요?
네, add_source 도구를 사용하여 결과물을 Evermuse 지식 베이스에 다시 저장할 수 있습니다.