Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words
Beginner mode On
ColoursSystemLightDark
LanguageไทยEnglish中文日本語한국어EspañolDeutsch
☰ MenuSettings
Beginner mode On
ColoursSystemLightDark
LanguageไทยEnglish中文日本語한국어EspañolDeutsch

minddy

by mangue-devversion 0.10.30i★ –iRuns in the cloud
Registry nameio.github.mangue-dev/minddy

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • The registry lists no key to fill in.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3
https://www.minddy.app/api/mcp

Run this in your terminal

claude mcp add --transport http minddy https://www.minddy.app/api/mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3
https://www.minddy.app/api/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account mangue-dev, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

  • More stars than 0% of the other 32476 servers in this category
  • Published to the registry more recently than 47% of the other 32476 servers in this category
  • Basic checks equal to or better than 100% of the other 32476 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is minddy safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.10.30) reached the registry last month.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, zanadir

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

zanadir

by MustacheCase

Find what a repository's CI is missing, and which security checks cannot fail the build.

Runs on your computerUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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.

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

Ask PopNx