The MCP server puts your tasks inside AI clients that speak the Model Context Protocol: Claude, Claude Code, Cursor, VS Code, Codex. The client asks the server, the server checks your key, and only your own data comes back.
You need an API key first.
Server address
https://mcp.todowl.com/Claude Code
One command, run in a terminal:
claude mcp add --transport http todowl https://mcp.todowl.com/ \
--header "Authorization: Bearer todowl_YOUR_KEY"Cursor, Claude Desktop, VS Code
These clients read a JSON config file: .cursor/mcp.json in Cursor, claude_desktop_config.json in Claude Desktop, mcp.json in VS Code. Add the server there and restart the client.
{
"mcpServers": {
"todowl": {
"url": "https://mcp.todowl.com/",
"headers": { "Authorization": "Bearer todowl_YOUR_KEY" }
}
}
}ChatGPT
ChatGPT connects to MCP servers through Settings, Connectors, Create. Custom connectors need a paid plan, and ChatGPT expects the server to run an OAuth sign-in flow. ToDowl authenticates with the key in a header instead, so ChatGPT is the one client on this list that may refuse the connection today.
What the client can do
- Tasks: list, search, read one, create, create several at once, update, complete, move between projects and lists, send to Trash.
- Projects and lists: list, create, rename, change colour or icon, archive, delete.
- Calendar: list everything scheduled in a date range, create, update and delete events.
- Notes: list, read, create, update, delete.
- Habits: list, create, update, delete, read check-ins, check in.
- Trash: list, restore, delete for good.
Everything runs as you, under your account, and respects the same rules the app does.
That is 41 tools in all. The API reference lists every one of them with the parameters it takes, an example call and what comes back.
Good to know
Every request carries the key, because the server keeps no session between calls. A revoked key stops working right away, in the middle of a conversation if that is when you revoked it.