Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Description from the maker (original English)
Search your customer interviews, calls, feedback, competitor intel and roadmap from any AI agent.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://api.evermuse.com/api/mcpRun this in your terminal
claude mcp add --transport http evermuse https://api.evermuse.com/api/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"evermuse": {
"url": "https://api.evermuse.com/api/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"evermuse": {
"type": "http",
"url": "https://api.evermuse.com/api/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://api.evermuse.com/api/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The publisher (evermuse.com) is not the repo owner (Usermuse); someone else may have listed it
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 0 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.1) reached the registry 31 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Context7, Codebase Memory, Exa
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
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.
# 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
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.
The plugin bundles the Evermuse MCP server (https://api.evermuse.com/api/mcp). Before the skills can ground anything, connect it:
/mcp in an interactive session and authorize evermuse.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.)
/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
Every skill follows Ground → Work → Cite → Save:
evidence = customer voice, context = market, guidance = company strategy) plus verbatim quotes.[^n] footnote.add_source.The full doctrine lives in the using-evermuse skill, which every other skill defers to.
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.
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.
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.
using-evermuse (the doctrine + MCP mechanics every skill uses)write-feature-spec, development-plan, gap-analysis, review-pr, customer-researchbrainstorm-ideas, deep-dive, assumptions, prioritize-features, analyze-feature-requests, opportunity-solution-tree, interview-script, summarize-conversationproduct-strategy, product-vision, value-proposition, business-model, pricing-strategy, strategy-frameworks, strategy-red-teamcreate-prd, user-stories, brainstorm-okrs, outcome-roadmap, release-notes, test-scenarios, shipping-artifacts, daily-briefuser-personas, segmentation, customer-journey-map, market-sizing, `cOnly the beginning is shown; read the rest in the repo