GTD Brain
com.gtdbrainPublished by gtdbrain.comOfficial publisherv1.0.9Updated Oct 24, 2026
Getting Things Done (GTD) board: capture to Inbox, next actions by context, projects, waiting-for.
Overview
A remote GTD board server that lets an assistant capture items to an Inbox and work with next actions by context, projects, and waiting-for lists.
- What you can do
- GTD Brain exposes a Getting Things Done board to an assistant over a remote streamable HTTP endpoint. Based on the registry description, it supports capturing items into an Inbox, organizing next actions by context, tracking projects, and managing waiting-for items. No individual tools are listed in the manifest, so the exact operations are not documented here.
- When to use it
- Use it when you follow the Getting Things Done method and want an assistant to help capture tasks quickly, review next actions by context, or keep projects and waiting-for items in view. It is less relevant if you do not already use a GTD-style workflow.
- Requirements
- A remote MCP client that supports streamable HTTP, connected to the GTD Brain endpoint. OAuth authentication is required, so you need a GTD Brain account and must complete the OAuth sign-in flow. No environment variables or headers are declared.
Installation
In SourceWeft
- Open GTD Brain in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- 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/com.gtdbrain%2Fgtd-brain/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.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"gtd-brain": {
"type": "http",
"url": "https://mcp.gtdbrain.com/api/gtdbrain/v1/mcp"
}
}
}Tools
0Version history
5- v1.0.9LatestOct 4, 2026
- v1.0.6Sep 29, 2026
- v1.0.5Sep 27, 2026
- v1.0.4Sep 16, 2026
- v1.0.3Sep 16, 2026
Score
67% 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
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.