minddy MCP server
Commit Nov 15, 2026Lets coding agents manage backlogs, triage issues, and access project knowledge through a unified workspace.
Also known as mangue-dev/minddy
- Stars
- 1
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.10.30
- Last commit
- Nov 15, 2026
- License
- AGPL-3.0
What is minddy MCP?
minddy lets coding agents manage backlogs, triage issues, and access project knowledge through a unified workspace.
Summary generated from the project's README
About minddy MCP server
minddy provides an open-source workspace designed for small product teams to manage issue tracking, product knowledge, and customer feedback. It functions as a unified hub where projects, objectives, and collaborative pages live alongside a public feedback board. Developers can run the application locally using Node.js and pnpm with a Supabase project, or opt for the hosted Minddy Cloud service. The system also supports self-hosting on private infrastructure without requiring a managed provider.
The platform includes an MCP server that uses an OAuth 2.1 endpoint to allow external coding agents to interact with the same backlog used by the human team. Through Numo conversations, agents can triage issues, fill cycles, and write pages by accessing project context. This integration ensures that AI agents and team members work from a single source of truth, whether they are reviewing specifications in the nested project wiki or managing tasks through the issue tracker.
What you can do with it
- 1Automated issue managementAn AI agent can create and organize new tasks within your project backlog.
- 2Centralized project documentationDevelopers can maintain specifications and runbooks in a structured wiki for both humans and agents.
- 3Customer feedback integrationTeams can connect user requests directly to their development workflow.
- 4Agentic workspace synchronizationCoding agents can access the same project data and context as the rest of the team.
Written from the project's README. Every use case is checked against a quote from it.
How to install minddy MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall minddy MCP in Claude Code
$ claude mcp add --transport http minddy https://www.minddy.app/api/mcpInstall minddy MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"minddy": {
"url": "https://www.minddy.app/api/mcp"
}
}
}Install minddy MCP in VS Code
.vscode/mcp.json
{
"servers": {
"minddy": {
"type": "http",
"url": "https://www.minddy.app/api/mcp"
}
}
}Install minddy MCP in VS Code CLI
$ code --add-mcp '{"name":"minddy","type":"http","url":"https://www.minddy.app/api/mcp"}'Install minddy MCP in Codex
$ codex mcp add minddy --url https://www.minddy.app/api/mcpInstall minddy MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.minddy] url = "https://www.minddy.app/api/mcp"
Install minddy MCP in Gemini CLI
$ gemini mcp add -s user --transport http minddy https://www.minddy.app/api/mcpInstall minddy MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"minddy": {
"url": "https://www.minddy.app/api/mcp",
"type": "http"
}
}
}Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablemangue-dev/minddy is public and reachablegithub.com/mangue-dev/minddy ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)AGPL-3.0spdx.org/licenses/AGPL-3.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-14github.com/mangue-dev/minddy ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeHTTPS endpoint answered 401 (sign-in required)Pass
README
View on GitHubminddy is an open-source issue tracker for small product teams. It keeps the daily work in one place: projects, issues, objectives, saved views, collaborative pages, a public feedback board, and an MCP server that lets coding agents work with the same backlog as the team.
The application is built with Next.js, React, Tailwind CSS, and Supabase. It also includes optional macOS, Linux, and Microsoft Store Windows desktop shells and integrations for GitHub, GitLab, Stripe, and OpenRouter.
Product tour
Track work with Numo
Start one Numo conversation from its page or the contextual floating button. Numo answers with project context and updates Minddy directly: it creates and triages issues, fills cycles, writes pages, and runs scheduled routines. Coding stays with your own agent: copy an issue as a prompt, then review the linked pull request in Minddy.
Keep durable knowledge beside the backlog
Write specifications, decisions, runbooks, and meeting notes in a nested project wiki. Pages support rich Markdown, issue mentions, attachments, history, and read-only sharing, so both people and connected agents can work from the same source of truth.
Connect customer feedback to delivery
Publish a feedback board where users can submit requests and vote. The team can triage posts, reply publicly, merge duplicates, and link feedback to issues so its public status follows the work through delivery.
Run locally
Requirements: Node.js 24.22.1 or a later 24.x and pnpm 10 (the versions used by CI), plus a Supabase project for an interactive application.
corepack enable
corepack prepare pnpm@10.28.0 --activate
pnpm install --frozen-lockfile
cp .env.example .env
pnpm dev
.env.example documents every optional integration and the Supabase dashboard
settings. At minimum, set MINDDY_PUBLIC_SUPABASE_URL,
MINDDY_PUBLIC_SUPABASE_ANON_KEY, and SUPABASE_SERVICE_ROLE_KEY for a local
application that can access its data. Never commit .env or production
credentials.
The development command builds the page-markdown bundle before starting Next.js. See CONTRIBUTING.md before running code from an untrusted pull request: dependency installation, tests, and development commands execute repository code.
Minddy Cloud is the hosted and operated option from Minddy. Self-hosted is
the same public core on infrastructure you control: no Minddy account, Stripe,
PostHog, or managed provider is required. The edition guide
explains the choice, data flows, responsibilities, and costs in one place.
To install your own instance, start with the
step-by-step self-hosting installer
for this computer or a shared server. On your own computer, the desktop app's
Self-host minddy › Install on this computer runs the whole local
installation for you. Use
docs/self-hosting.md as the technical reference for
topology, configuration, and reproducible Supabase bootstrap. On a fresh local clone, use
pnpm bootstrap:supabase before pnpm dev instead of manually applying SQL in
the Supabase dashboard. After installation, follow the
self-hosted operations runbook for upgrades,
coordinated Postgres and Storage backups, disaster recovery, and rollback.
Release acceptance is recorded with the isolated
clean-room self-hosting scenario.
The official multi-architecture OCI image, its tag policy, and verification
commands are documented in docs/container-image.md.
Common commands
pnpm dev # run the web app locally
pnpm lint # lint
pnpm typecheck # type-check
pnpm test # run the test suite
pnpm build # production build
pnpm desktop:dev # run the optional desktop shell
Architecture and deployment
Development follows a trunk-based branch contract: short-lived work branches
merge by pull request into main, the integration branch and preview candidate.
After CI and explicit production approval, automation fast-forwards
production to the selected main SHA. There is no long-lived develop or
release branch, and no human writes directly to production.
- Web app: Next.js App Router, React, Tailwind CSS, and Minddy's own UI
components (
components/ui/, Radix-based). - Data and auth: Supabase Postgres, Auth, Storage, and Realtime.
- Numo and agent integration: Unified Numo conversations, scheduled routines, and an OAuth 2.1 MCP endpoint for external agents.
- Deployment:
pnpm deployis the interactive maintainer entry point. It detects whether to release the public core, deploy the Minddy Cloud web app, and publish desktop applications for macOS, Linux, and Windows, with automatic, all, custom, and Windows-only modes. The Windows-only mode reuses an existing core release and avoids starting macOS or Linux runners. The assistant waits for CI, requests an approved fast-forward frommaintoproduction, verifies the Vercel Production deployment, and only tags that deployed SHA. Builds and production secrets never come from the maintainer's machine. Self-hosters should adapt itsproduction/Vercel conventions to their own hosting.
Public releases are distinct from deployments. Their SemVer/tag policy, artifacts, checksums, migrations, CI provenance, desktop distribution, and rollback procedure are documented in docs/releases.md. Linux installation, GPG verification, XDG paths, and update behavior are documented in docs/linux-desktop.md. The registration of the MCP server in the public registry after each release is documented in docs/mcp-registry-publication.md.
The CI workflow is the source of truth for checks. It runs the public-repository check, lint, typecheck, desktop bundle build, tests, and dependency audit. See CONTRIBUTING.md for contribution and review guidance, and SECURITY.md for the security model and vulnerability reporting.
Community and governance
- Propose bugs and improvements through the repository's structured issue forms, and read CONTRIBUTING.md before opening a pull request.
- Ask usage and self-hosting questions in GitHub Discussions. The boundaries between best-effort community help and commercial support are documented in SUPPORT.md.
- Project roles, decisions, reviews, protected branches, and dependency policy are defined in GOVERNANCE.md.
- Participation is subject to the Code of Conduct. Report vulnerabilities privately as described in SECURITY.md.
License
minddy is released under the GNU AGPL v3.0 only. If you operate a modified version for users over a network, you must offer those users the corresponding source code. See the licensing policy, including the limits on use of the minddy name and logos.
minddy MCP questions
How do I add minddy MCP to Claude Code?
Run claude mcp add --transport http minddy https://www.minddy.app/api/mcp in your terminal. Add --scope user to make it available in every project.
How do I add minddy MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
Can I host minddy on my own infrastructure?
Yes, you can self-host the public core on your own infrastructure without needing a Minddy account or managed providers.
Does minddy support customer feedback?
Yes, it includes a public feedback board where users can submit requests and vote, which can then be linked to issues.