One command, one approval in your browser, and your agent reads and updates your issues.
Included in every plan, the free one too. There is no key to create.
The address to connect to
https://www.minddy.app/api/mcp
Authentication
You approve in your browser, once
Pick yours and paste the line. It asks for your approval the first time.
- Claude Code
claude mcp add --scope user --transport http minddy https://www.minddy.app/api/mcpRun it in a terminal.
- Claude Desktop
https://www.minddy.app/api/mcpPaste it as a custom connector.
- Codex
codex mcp add minddy --url https://www.minddy.app/api/mcp && codex mcp login minddyRun it in a terminal.
- CursorInstall in Cursor
Opens the app and adds minddy.
- Gemini CLI
gemini mcp add --scope user --transport http minddy https://www.minddy.app/api/mcpRun it in a terminal.
- VS Code
code --add-mcp '{"name":"minddy","type":"http","url":"https://www.minddy.app/api/mcp"}'Run it in a terminal.
- Windsurf
{ "mcpServers": { "minddy": { "serverUrl": "https://www.minddy.app/api/mcp" } } }Paste it into the agent configuration file.
Or let your assistant do it
Copy this and paste it to the agent you already have open. It handles the rest.
Add the minddy MCP server to my setup. It is a remote MCP server at https://www.minddy.app/api/mcp, over HTTP with OAuth, and there is no API key to create. Read https://www.minddy.app/llms.txt for the exact steps, register it for the agent you are running in, then tell me how to approve access.
Nothing to store, nothing to leak, nothing to rotate.
The agent acts as you
It sees the projects you see, and nothing else. Every change is attributed.
One approval, in the browser
It asks the first time you use it. You choose the account.
Revoked from your settings
Connected apps are listed in your account. Removing one cuts access immediately.
It works the way you do, in the same tool, on the same issues.
- Read an issue with its full context.
- Write its plan onto the issue, then tick it off.
- Change status, priority, assignee, objective.
- Create issues and objectives, and link them together.
- Report back in a comment.
- Review the pull request opened on the issue.
- And the notebook, your cycle, your user feedback too.
Not a feature list: the three sentences that come back every day.
- 1
Let the agent write the implementation plan
It reads the issue, looks through your repository, and writes the plan onto the ticket.
Ask this
Read MIN-42 in minddy and write its implementation plan. - 2
Let the agent tick the tasks off as it goes
Each finished task turns to done on the issue. You follow along without asking.
Ask this
Work through the plan on MIN-42 and keep its tasks up to date. - 3
Turn a conversation into issues
Describe what you decided; the agent files it with priority, effort and objective.
Ask this
Create issues in minddy for everything we just decided.