Dooit

so.dooitPublished by dooit.soOfficial publisherv1.0.0Updated Oct 24, 2026

Read and run a user's task board: tasks, schedules, projects, and weekly/monthly/yearly goals.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

Remote Dooit MCP server that lets an assistant read a personal task board and create, reschedule, complete, archive or delete tasks, projects and goals.

What you can do
  • Read the board and agenda, including today's date in the user's timezone and the ids writes need
  • List and inspect tasks, then create, update, mark done, archive or delete them
  • Create and update projects
  • List, create and update weekly, monthly and yearly goals
When to use it
Useful when you want an assistant to work inside a Dooit task manager: reviewing the agenda, planning the week, or making and rescheduling tasks and goals on your behalf without leaving the chat.
Requirements
A hosted remote endpoint at app.dooit.so over streamable HTTP; no package or API key. A Dooit account is required, and sign-in uses OAuth 2.1 with dynamic client registration. Writes need an active subscription and are rate limited.
Before you install
The assistant can change your data: it creates, updates, completes, archives and deletes tasks, and creates or updates projects and goals. Deletions and archives may be hard to undo. Write access depends on a paid subscription, and writes are rate limited.

Installation

In SourceWeft

  1. Open Dooit in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/so.dooit%2Fmcp/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "dooit": {
      "type": "http",
      "url": "https://app.dooit.so/mcp"
    }
  }
}

README

Dooit MCP server

This repo is metadata and docs, not source. Dooit's MCP server is hosted — it runs as part of the Dooit app, and its code lives in the product repo. This repo exists because the ecosystem assumes one: server.json wants a repository, aggregators key their claim flow off it, and directory entries are owner/repo shaped.

Dooit is a lightweight, keyboard-first personal task manager. The MCP server lets an agent read your board, agenda, projects and weekly/monthly/yearly goals, then create, reschedule, complete, archive and delete tasks on your behalf — in your own timezone, with your own permissions.

Connect

claude mcp add --transport http dooit https://app.dooit.so/mcp

Claude Desktop, claude.ai, ChatGPT, Cursor and other clients take the same URL as a custom connector. Auth is OAuth 2.1 with dynamic client registration — there is no API key.

You need a Dooit account. Reads work on any account; writes require an active subscription and are rate limited.

Docs

Tools

Context: get_board, get_agenda Tasks: list_tasks, get_task, create_task, update_task, set_task_done, archive_task, delete_task Projects: create_project, update_project Goals: list_goals, create_goal, update_goal

Call get_board first — it returns today's date in the user's timezone plus the status and project ids every write needs.

License

MIT

Source: README.md at commit 9f73477

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

85% 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
  • License10 pts