discoveree-desktop
Provides a local, agent-maintained product context layer over MCP, serving structured strategy, competitor, customer feedback, and feature inventory data to any AI tool such as Claude, Cursor, or ChatGPT, with local data storage, bring-your-own-LLM support, and weekly evidence-based roadmap reviews that can sync suggestions to Jira or Linear.
README
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.
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 docs
One 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.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.