discoveree-desktop
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@discoveree-desktoprun this week's roadmap review and suggest priorities for Jira"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Discoveree Desktop
A local, agent-maintained context layer for your product, served over MCP to any AI tool.
Discoveree keeps a structured, always-fresh picture of your product world — strategy, competitors, customers and feedback, and your product's own feature inventory — maintained by agents and served over the Model Context Protocol to whatever AI tools you already use: Claude, Cursor, ChatGPT, or your own agents.
Status: pre-alpha. The desktop edition is under active development and not yet ready for use. The build plan lives in docs/build-brief.md.
Why
AI tools are only as good as the context they're given. Prose documents rewritten by prompts silently accumulate duplicates and drift. Discoveree holds product context as a typed, validated schema — stable IDs, provenance, confidence, freshness accounting — kept current by deterministic pipelines (hash-diff changelog monitoring, help-centre crawling, review mining), and serves it to every tool and teammate from one source of truth.
Your data stays local. Competitive and roadmap data never leaves your machine.
Bring your own LLM keys. One key from any major provider is enough.
Any AI tool connects. Local MCP over stdio and localhost HTTP.
Judgment, not just storage. A weekly, evidence-cited review of whether your roadmap is building the most valuable things — with suggestions you can accept into Jira or Linear.
Related MCP server: PM-Skills MCP
Structure
client/ React SPA (shared by desktop and team deployments)
server/ Express server — embedded in the desktop app, deployable shared for teams
shared/ Schema and types (Drizzle + Zod)
docs/ Build brief and design docsOne codebase, two deployments: the desktop app embeds the server with a local database; the team tier deploys the same server shared. Local/team is a deployment target, not a fork.
Licence
Functional Source License, Version 1.1, ALv2 Future License (FSL-1.1-ALv2): source-available — you can read, run, and modify the code for any non-competing purpose, and each version becomes Apache 2.0 licensed two years after release.
This server cannot be deployed
Maintenance
Related MCP Connectors
Your product team's shared strategic memory — an MCP server your AI tools reason over.
Your versioned memory across every AI tool — context maps, personal memory, and tasks over MCP.
One shared context your team's AI tools read & write over MCP. No re-explaining. Free.
shared AI-context layer for teams — persistent memory your agents search and update over MCP
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAI-native productivity backend that gives your AI assistant persistent memory, pattern awareness, and computed intelligence about your work. 14 MCP tools for task management, daily planning, weekly review, and personal context.MIT
- AlicenseAqualityBmaintenanceMCP server exposing 40 best-practice product management skills plus workflows and lifecycle tools, instantly accessible to any AI via Model Context Protocol.1929 npm20Apache 2.0
- AlicenseAqualityAmaintenanceOne context engine for every AI. Persistent context from GitHub, Notion, and your decisions, delivered to Claude, ChatGPT, Cursor, VS Code, Gemini, and any MCP-compatible client.93AGPL 3.0
- FlicenseNot gradedqualityBmaintenanceA single source of truth for a product's state, roadmap, and deferred work, read and written equally by you and your AI agent via web dashboard and MCP.-