minddy

io.github.mangue-devPublished by GitHub account mangue-devv0.10.30Updated Oct 26, 2026

Minimal issue tracker: projects, objectives and trackable plans, written by agents over MCP.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

Minddy's hosted MCP endpoint lets an AI assistant work in a team issue tracker: projects, issues, objectives, wiki pages and feedback.

What you can do
  • Create, triage and update issues in projects, including cycles and objectives
  • Write and edit nested project wiki pages such as specs, decisions and runbooks
  • Work with saved views and the public feedback board, linking posts to issues
  • Run scheduled routines and Numo conversations that update the workspace directly
When to use it
Useful for small product teams that already run Minddy and want a coding or assistant agent to read and change the same backlog the team uses, instead of copying issues into prompts by hand.
Requirements
A remote MCP endpoint at the Minddy host, reached over streamable HTTP with OAuth sign-in; no local runtime or environment variables are declared. Self-hosting the app itself instead needs Node.js 24.x, pnpm 10 and a Supabase project.
Before you install
The assistant can create and change issues, pages and feedback posts in a shared team workspace, so writes are visible to colleagues. Access is granted through OAuth to your Minddy account; review which workspace and permissions you authorize. Self-hosted setups require Supabase keys such as SUPABASE_SERVICE_ROLE_KEY, which must never be committed.

Installation

In SourceWeft

  1. Open minddy in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.mangue-dev%2Fminddy/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "minddy": {
      "type": "http",
      "url": "https://www.minddy.app/api/mcp"
    }
  }
}

README

[minddy app icon]

minddy

Issue tracking, product knowledge, and Numo in one open-source workspace.

minddy 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.

[A minddy project board with issues grouped by status]

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.

[A minddy board with the new issue dialog open]

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.

[The minddy page editor showing a release process document]

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.

[A public minddy feedback board with requests, statuses, and vote counts]

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.

bash
corepack enablecorepack prepare [email protected] --activatepnpm install --frozen-lockfilecp .env.example .envpnpm 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

bash
pnpm dev          # run the web app locallypnpm lint         # lintpnpm typecheck    # type-checkpnpm test         # run the test suitepnpm build        # production buildpnpm 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 deploy is 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 from main to production, 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 its production/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.

Source: README.md at commit d6dce93

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.10.30LatestSep 22, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts