GTD Brain
Getting Things Done (GTD) board for AI agents: capture to Inbox, next actions by context, projects, waiting-for, someday/maybe.
What it can do
- Capture: GTD capture: add a card straight to the Inbox. The go-to tool for anything the user mentions they need to do, remember, or follow up on — capture first, clarify later; no column lookup needed
- List Next Actions: List the cards in the Next Actions column, in board order. This answers 'what should I do now / what can I work on'; optionally filter by GTD context (where the user is or what they
- List Projects: List the cards in the Projects column, in board order. A project is any outcome needing more than one step; use this to check each has a next action. Use this instead of list_columns +
What data it sees
Do you need an account
No: the server works without sign-in
Getting Things Done (GTD) board for AI agents: capture to Inbox, next actions by context, projects, waiting-for, someday/maybe. Remote Streamable HTTP server with OAuth 2.1 login (passwordless email code). 16 tools + 4 prompts. Setup guide: https://gtdbrain.com/connect?source=smithery
How to connect
How to connect GTD Brain to Claude
The server address to paste into Claude settings:
https://gtd-brain--admin-xigh.run.tools
- Open Claude (claude.ai or the desktop app).
- Go to Settings → Connectors.
- Click Add custom connector.
- Paste the server address copied below into Remote MCP server URL and click Add.
- In a chat, click + → Connectors and switch the new connector on.
Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.
Authorization
After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.
How to connect GTD Brain to ChatGPT
The server address to paste into ChatGPT settings:
https://gtd-brain--admin-xigh.run.tools
- Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
- Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
- Open Settings → Connectors and click Create.
- Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
- Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
- In a new chat open + → Apps/Connectors and enable the connector.
OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.
Authorization
On first use ChatGPT opens the service's sign-in window. Sign in and approve access.
How to connect GTD Brain to Cursor
The server address to paste into Cursor settings:
https://gtd-brain--admin-xigh.run.tools
Fastest: click Open in Cursor below and confirm the prompt.
Manually:
- In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
- Paste the JSON copied below into
~/.cursor/mcp.json(per project:.cursor/mcp.jsonin the repo root). - Save the file. The server appears in the MCP list; authorize it there if asked.
Authorization
If the service needs sign-in, an authorize button appears next to the server in the MCP list.
Server tool list (16)
Raw names from tools/list. Only developers need these.
| capture | GTD capture: add a card straight to the Inbox. The go-to tool for anything the user mentions they need to do, remember, or follow up on — capture first, clarify later; no column lookup needed. Returns the created card. |
| list_next_actions | List the cards in the Next Actions column, in board order. This answers 'what should I do now / what can I work on'; optionally filter by GTD context (where the user is or what they have). Use this instead of list_columns + list_cards when the user asks for their next actions. |
| list_projects | List the cards in the Projects column, in board order. A project is any outcome needing more than one step; use this to check each has a next action. Use this instead of list_columns + list_cards when the user asks for their projects. |
| list_waiting_for | List the cards in the Waiting For column, in board order (each card carries who it's delegated to and since when). Use it for 'who am I waiting on' and follow-up nudges, instead of list_columns + list_cards. |
| list_columns | List the user's GTD board columns (Inbox, Next Actions, Projects, Waiting For, Someday/Maybe, and any custom columns) with their ids, labels, kind, order, and the ordered card ids in each. Needed for column ids when working with columns the fast-access tools don't cover. |
| list_cards | List the user's GTD Brain cards. Archived cards are excluded unless includeArchived is true. Optionally filter by column, kind, or context. |
| search_cards | Search the user's GTD Brain cards by a case-insensitive substring over title and notes. Archived cards excluded unless includeArchived is true. |
| get_card | Get the full details of one GTD Brain card by its id. |
| create_card | Create a new GTD Brain card and add it to a column. A 'card' goes in normal/flexible columns, an 'action' only in Next Actions, a 'project' only in Projects. Returns the created card. |
| update_card | Edit a GTD Brain card's fields (any of title, notes, context, who, since). Does NOT move the card between columns — use move_card for that. Returns the updated card. |
| move_card | Move a GTD Brain card to any column (or reorder it within its column). The card's kind is re-derived from the destination column (next→action, projects→project, normal→note, flexible keeps it). Returns the moved card. |
| archive_card | Archive a GTD Brain card (soft-remove). The card is kept but hidden from the board and can be restored later. There is no delete — this is the only way to remove a card. Returns the archived card. |
| list_contexts | List the user's GTD contexts (id, label, color, order). Context ids are the values create_card, update_card, and the context filters accept. |
| create_context | Create a new GTD context (e.g. '@boat'). The id is derived from the label and must not clash with an existing context. Color is optional (hex like #4f9466); one is auto-picked if omitted. Returns the created context. |
| update_context | Rename or recolor a GTD context. The context id never changes, so cards keep their assignment. Returns the updated context. |
| delete_context | Delete a GTD context. Every card carrying it (archived included) gets its context cleared. Returns the deleted id and how many cards were cleared. |