Connect a client
Claude Code, Claude Desktop, claude.ai, ChatGPT, Cursor, VS Code, or any client from a JSON
config.
What it exposes
186 tools
Every public operation but seven: tasks, projects, areas, planning, calendar, coach, sharing,
agents and account.
5 resources
Views to pin in a conversation: today’s context, open tasks, the day’s plan, projects, one task.
4 prompts
Ready-made workflows: plan my day, brain dump, start my round, triage.
MCP or REST
Both come from the same list of operations, so a tool and its REST route take the same input and return the same output. What differs is who calls them.
That last line matters. When a client connects, the server sends instructions that the client puts
in the model’s context:
when is not deadline, a task is in a project or an area, the server
works in UTC, and the method (start with get_context, find identifiers with search rather than
asking, batch similar changes, propose a plan before committing it).
An example
You: What should I work on today? Then plan my day.The assistant chains, without asking you for an identifier:
get_context: your counters, and your top tasks with the reasons behind each score;suggest_day_plan: a proposal split into rounds, written nowhere;- it shows you three to five tasks and waits for your answer;
plan_today: saves the plan you agreed to, shown at the top of Today in the app.
Good to know
- Every tool acts with your account’s full authority. Neither a token nor an OAuth connection narrows what a client can do. Grant access only to clients you trust, and prefer clients that ask before running a tool marked destructive.
- Stateless. No session: each request carries its credential.
- Product only. This server and these pages cover the Doers product. The Doers website’s content management resource is operational infrastructure: it is not public, not documented here and not listed in the public MCP Registry.
- Your day. Tools that take a
dayexpect it in your time zone; without it, the server uses its UTC day.