Evermuse MCP sunucusu
Commit 6 Kas 2026Yapay zeka ajanlarının müşteri görüşmeleri, aramalar, geri bildirimler ve yol haritaları içinde arama yapmasını sağlayarak ürün çıktılarını gerçek müşteri kanıtlarına dayandırmanıza olanak tanır.
Ayrıca bilinen adı Usermuse/em-plugin, em-plugin
- Yıldızlar
- 0
- Araçlar
- 5
- İndirmeler, 30 gün
- —
- En son sürüm
- 1.0.1
- Son commit
- 6 Kas 2026
- Lisans
- MIT
Evermuse MCP nedir?
Evermuse bir MCP sunucusudur. Yapay zeka ajanlarının müşteri görüşmeleri, aramalar, geri bildirimler ve yol haritaları içinde arama yapmasını sağlayarak ürün çıktılarını gerçek müşteri kanıtlarına dayandırmanıza olanak tanır. 5 araç sunar; örneğin add_source, add_signals, create_shaping_note.
Özet, projenin README dosyasından oluşturuldu
Evermuse MCP sunucusu hakkında
Ürün yöneticileri ve geliştiriciler, Claude Code veya Cursor içerisinde Evermuse kullanarak teknik çıktılarını gerçek müşteri kanıtlarına dayandırabilirler. Sunucu, yapay zeka ajanınızı kaydedilmiş aramalar, görüşmeler ve geri bildirimlerle birbirine bağlayarak, genel varsayımların yerine doğrudan alıntılar ve spesifik sorun noktaları kullanılmasını sağlar. Mevcut bilgi tabanınızda arama yaparak özellik spesifikasyonları yazma, geliştirme planları oluşturma veya PR incelemeleri yapma gibi görevler için bağlam sağlar.
Sunucuyu kullanmak için istemci üzerinden OAuth ile kimlik doğrulayabilir veya MCP ayarlarınızda bir API key sağlayabilirsiniz. Bağlantı kurulduktan sonra, belirli ürününüzü seçmek için /evermuse:setup komutunu kullanabilirsiniz. Sistem; araştırmayı temellendirme, işi gerçekleştirme, kaynakları dipnotlarla belirtme ve nihai sonucu Evermuse çalışma alanınıza kaydetme teklifinde bulunma şeklinde katı bir iş akışını takip eder. Bu sayede her bir spesifikasyon veya yol haritası; customer_research, write_feature_spec ve review_pr gibi araçlar aracılığıyla gerçek kullanıcı ihtiyaçlarına bağlı kalır.
Neler yapabilirsiniz
- 1Özellik spesifikasyonlarını araştırmaya dayandırmaAjanın, gerçek müşteri gereksinimlerini kullanarak yeni bir özellik için teknik spesifikasyon yazmasını isteyin.
- 2Belirli konularda müşteri duyarlılığını analiz etmeKullanıcıların ürününüzün onboarding veya fiyatlandırma gibi belirli bir bölümü hakkında neler söylediğini öğrenmek için ajana sorgu gönderin.
- 3Pull request'leri kullanıcı ihtiyaçlarına göre doğrulamaBir kod değişikliğinin orijinal müşteri talepleriyle uyumlu olup olmadığını kontrol etmek için ajanı kullanın.
Projenin README dosyasından alınmıştır. Her kullanım durumu, oradaki bir alıntı ile kontrol edilir.
Evermuse MCP nasıl yüklenir
Biçimler 10 Kas 2026 tarihinde doğrulandıCursor'a ekleGoose'a ekleEvermuse MCP'yi Claude Code içine yükleyin
$ claude mcp add --transport http em-plugin https://api.evermuse.com/api/mcpEvermuse MCP'yi Cursor içine yükleyin
~/.cursor/mcp.json
{
"mcpServers": {
"em-plugin": {
"url": "https://api.evermuse.com/api/mcp"
}
}
}Evermuse MCP'yi VS Code içine yükleyin
.vscode/mcp.json
{
"servers": {
"em-plugin": {
"type": "http",
"url": "https://api.evermuse.com/api/mcp"
}
}
}Evermuse MCP'yi VS Code CLI içine yükleyin
$ code --add-mcp '{"name":"em-plugin","type":"http","url":"https://api.evermuse.com/api/mcp"}'Evermuse MCP'yi Codex içine yükleyin
$ codex mcp add em-plugin --url https://api.evermuse.com/api/mcpEvermuse MCP'yi Codex config.toml içine yükleyin
~/.codex/config.toml
[mcp_servers.em-plugin] url = "https://api.evermuse.com/api/mcp"
Evermuse MCP'yi Gemini CLI içine yükleyin
$ gemini mcp add -s user --transport http em-plugin https://api.evermuse.com/api/mcpEvermuse MCP'yi Gemini settings.json içine yükleyin
~/.gemini/settings.json
{
"mcpServers": {
"em-plugin": {
"url": "https://api.evermuse.com/api/mcp",
"type": "http"
}
}
}Evermuse MCP araçları 5
README dosyasından algılandıadd_sourceadd_signalscreate_shaping_noteupdate_signalsupdate_shaping_note
| add_source | — | |
| add_signals | — | |
| create_shaping_note | — | |
| update_signals | — | |
| update_shaping_note | — |
Otomatik kontroller
Çalıştırıldı 14 Kas 2026Tam rapor →Henüz doğrulanmadı. Bir sunucunun 80 puana, ciddi bir bulgu olmamasına ve kontrol edebilmemiz için yeterli veriye ihtiyacı vardır. Kontroller nasıl çalışır · Daha fazla puan için nelerin düzeltileceği
- Kaynak deposu bağlantılı ve erişilebilirusermuse/em-plugin is public and reachablegithub.com/usermuse/em-plugin ↗Geçti
- Paket, bu depoyu kaynağı olarak gösteriyorKontrol edilmedi
- Derleme kökeni (Sigstore onayı)Kontrol edilmedi
- Açık kaynak lisansı (OSI)MITspdx.org/licenses/MIT.html ↗Geçti
- Son bir yıl içinde commit veya sürüm mevcutLast commit or release 2026-11-06github.com/usermuse/em-plugin ↗Geçti
- OpenSSF ScorecardKontrol edilmedi
- Paket adı popüler bir pakete yakın değilKontrol edilmedi
- Pakette veya bağımlılıklarında kritik uyarı yokKontrol edilmedi
- Modele yönelik gizli talimat yok5 tool descriptions and the README read; no override phrases, credential paths or hidden charactersGeçti
- Yıkıcı araçlar etiketlenmişNo tool named like delete, drop or execGeçti
- Uzak uç nokta MCP el sıkışmasına yanıt veriyorHTTPS endpoint answered 401 (sign-in required)Geçti
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 soruları
Evermuse MCP'yi Claude Code'a nasıl eklerim?
Terminalinizde claude mcp add --transport http em-plugin https://api.evermuse.com/api/mcp komutunu çalıştırın. Her projede kullanılabilir olması için --scope user ekleyin.
Evermuse MCP'yi Cursor'a nasıl eklerim?
~/.cursor/mcp.json dosyasını açın ve yukarıdaki yükleme bölümünde gösterilen Cursor yapılandırmasını kullanarak sunucuyu mcpServers altına ekleyin.
Evermuse MCP hangi araçları sunar?
5 araç sunar; bunlar arasında add_source, add_signals, create_shaping_note, update_signals, update_shaping_note yer alır.
Evermuse MCP kimlik doğrulamasını nasıl yapabilirim?
Claude Code veya Cursor için OAuth (önerilen) kullanabilir ya da MCP ayarlarınıza bir Authorization header ekleyerek bir API key sağlayabilirsiniz.
Evermuse, Claude Code ve Cursor ile çalışıyor mu?
Evet, Evermuse özellikle Claude Code ve Cursor için tasarlanmış bir eklentidir ve her biri için farklı çağırma yöntemleri sunar.
Yapay zeka tarafından oluşturulan çıktıları tekrar Evermuse içine kaydedebilir miyim?
Evet, sistem add_source aracını kullanarak çıktıları Evermuse bilgi tabanınıza geri kaydetmenize olanak tanır.