Evermuse

What Evermuse MCP server does

The Evermuse MCP server gives AI agents access to customer and product knowledge stored in Evermuse. It is designed for product work that benefits from source-backed evidence, including customer research, feature specifications, development plans, PR reviews, roadmap work, competitor analysis, and feedback analysis.

The plugin combines MCP access with a collection of Claude Code skills and Cursor commands. These workflows instruct the agent to identify the relevant product, search for evidence using varied queries, apply the requested product or research method, cite customer-derived claims, and offer to save the resulting deliverable back to Evermuse.

How it works

The remote MCP endpoint is https://api.evermuse.com/api/mcp. Product-scoped operations require a product_id; there is no persistent session used to switch products. A project can optionally narrow work to a research effort such as Discovery, Support, or Sales.

Workflow tools can perform the initial grounding step and return the relevant methodology. Direct evidence work can use searches and item or source retrieval. The grounding process distinguishes customer voice (evidence), market information (context), and company strategy (guidance). Outputs are expected to include verbatim quotes and source references where customer evidence supports a claim. The agent can then persist a deliverable or related information through Evermuse write tools.

The Evermuse MCP server is bundled with the repository's Claude Code and Cursor plugins. Claude Code skills can activate from a plain-language request, while Cursor users invoke commands explicitly with slash commands or attach skills as context.

Setup and configuration

For Claude Code, add the repository as a plugin marketplace and install evermuse@evermuse. A local repository path can be used instead during development. Cursor users can install the plugin from the Cursor Marketplace or add the MCP server through the provided installation link.

Authentication is configured in the client. Claude Code and Cursor support OAuth; Claude Code starts authorization from /mcp, while Cursor uses Settings → MCP. An API key can be supplied through an Authorization header in either client's MCP settings. After authentication, run /evermuse:setup to select a Product and verify grounding.

Tools and capabilities

The published tool set contains 27 tools in these groups:

• Guidance: find_skills, read_skills
• Product context: product, summary, and project lookup tools
• Workflows: research, PRD, brief, feature-spec, persona, story, competitor, and conversation-summary tools
• Evidence: search, view_item
• Sources: find_sources, read_source
• Competitors and opportunities: listing, capability, and opportunity tools
• Shaping notes: read, create, and update tools
• Writes: add_source, add_signals, and update_signals

Claude Code exposes commands with the /evermuse: prefix, including setup, research, spec, development planning, PR review, and save workflows. Cursor provides equivalent short commands such as /research, /spec, and /dev-plan, plus additional commands for discovery, strategy, and launch planning.

Limitations and notes

A Product is required for every Evermuse call. Projects are optional. Cursor does not automatically activate skills, so its commands or attached skills must be invoked explicitly. The repository states that the skills/ directory is generated from the Evermuse monorepo and should not be edited directly; changes should be made upstream and synchronized.