Dayhand MCP server
Commit Nov 15, 2026Lets an AI agent add, plan, and finish tasks within a synchronized day plan and task list.
Also known as maiarowsky/dayhand
- Stars
- 2
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 15, 2026
- License
- Apache-2.0
What is Dayhand MCP?
Dayhand lets an AI agent add, plan, and finish tasks within a synchronized day plan and task list.
Summary generated from the project's README
About Dayhand MCP server
Managing a synchronized task list and daily schedule alongside AI agents is what Dayhand enables for solo business owners. It provides a unified environment where you and your automated assistants can add, plan, and complete tasks. The system tracks every modification, clearly identifying whether a change was made by you or a specific agent.
Users can interact with their plan through a terminal-based interface using the dayhand ui command, a command line interface, or dedicated desktop applications for Linux and macOS. An Android app is also available for mobile access. To keep everything in sync, you run a server locally on macOS or Linux, or deploy it to a Convex account if you are using Windows. AI agents connect to this central plan via MCP or the command line using unique API keys, allowing them to propose or execute work within your established schedule.
What you can do with it
- 1Delegate task creation to agentsYou can instruct an AI agent to add a specific task with a due date and reminder directly into your schedule.
- 2Manage tasks via terminal UIUse keyboard shortcuts to navigate between different views like the board, the week, or the agent management screen.
Written from the project's README. Every use case is checked against a quote from it.
Configuration
AGENT_KEYDAYHAND_API_KEYDAYHAND_URLTASK_ID
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablemaiarowsky/dayhand is public and reachablegithub.com/maiarowsky/dayhand ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-09github.com/maiarowsky/dayhand ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubI'm building Dayhand for myself and for other people who run a business on their own. It is a task list and a day plan for you and for the AI agents that work for you.
You plan in the terminal, full screen with dayhand ui or one command at a time, in the desktop
apps for Linux and macOS, or on an Android phone that keeps the plan offline with a calendar and
reminders. A server you run yourself, started with one command, keeps them in sync and lets your
agent add, plan and finish tasks over MCP or the dayhand command line. Every change shows who
made it: you or one of your agents.
$ DAYHAND_API_KEY=$AGENT_KEY dayhand add "Draft the VAT reply" --due "today 16:00" --remind 30
Added:
#3 [ ] today 16:00 Draft the VAT reply
$ dayhand
Today, Sat 24 Oct 2026 (Europe/London)
OVERDUE (1)
#1 [ ] yesterday Send the invoice to Anna
TODAY
#2 [ ] 14:00 Call the accountant
#3 [ ] 16:00 Draft the VAT reply
Terminal UI
dayhand ui opens the plan full screen in the terminal, on Linux and macOS alike. Below, Today with
sample data:
It has five views: Today, the board (to do, in progress, done), the week, the trash and Agents.
Enter opens a task with its history, which names who made each change (app, cli or
agent: <name>), who claimed the work, its acceptance criteria, plan, proof and dependencies. The
coloured line above Today sums up plan health, with the same counts as dayhand health.
| Key | Does |
|---|---|
j k, h l |
Next and previous task; board column or week day |
Tab, 1 to 5 |
Next view; Today, Board, Week, Trash, Agents |
a |
Add a task with a date phrase: Call the accountant fri 2pm |
Space or x, s, n |
Done; start or stop; make it the task you are working on now |
e, m, d |
Edit; move to another day; to the trash (asks first) |
/, y |
Filter; copy the task as plain text, ready to paste into a chat with an agent |
p, A, X |
In Agents: pause or resume changes; accept or reject a proposal |
?, q |
Every key; quit |
The keys follow vim and lazygit, and the mouse selects and scrolls (hold Shift while dragging to
select text, or start dayhand ui --no-mouse). Coming soon: M turns mouse reporting off so you
can select text with the mouse, and on again. It uses the terminal's 16 colours, so it follows your
theme, and its screens speak the terminal's language when it is one of the eight the apps speak
(--lang pl or DAYHAND_LANG=pl to choose); everything scripts and agents read stays English. It
has no reminders: the desktop and phone apps do. On Omarchy it becomes an app of its own
(docs/omarchy.md). Every key: dayhand help ui and
docs/terminal.md.
dayhand ui comes with the command line (Install) and opens the plan of the server it
is signed in to (Quick start).
Desktop apps
Dayhand for Linux (Qt 6) has Today with task details, a trash with restore, reminder settings, a quick add window for a keyboard binding and a tray icon. Reminders and the morning summary come as desktop notifications.
Dayhand for macOS keeps Today, projects and lists in a sidebar. Each one opens as a list, a board or a week plan. It has quick add from the menu bar or a global shortcut, reminders and the morning summary, the trash, each task's change history and read-only agent work.
Both work offline and speak English, Polish, German, Spanish, French, Brazilian Portuguese, Japanese and Simplified Chinese. Both are built from source for now: Build the desktop apps.
Dayhand for macOS, Today as a list with a task open, then the same day as a week plan (sample data):
On the phone
Dayhand for Android (8.0 or newer) starts without any server. Under On this phone only choose Start with an empty plan, or Try with sample data (one tap removes it). Today, the board and the projects, with sample data:
Without a server you still get Today with quick add (a date phrase at the end sets the day:
Call the accountant fri 2pm), the week and day calendar, the board, the Projects tab, task
details with repeats, checklists and reminders, the morning summary and a backup file (Backup
under Data in Settings). Making and changing projects needs a server
(projects). The plan then lives only on the phone. Android backups are off for
Dayhand, so keep a backup file. To sync the phone with the command line, the desktop apps and your
agents: Connect the phone.
Install
| System | Command line and dayhand ui |
App | Server on this computer |
|---|---|---|---|
| Linux | npm or Homebrew | Dayhand for Linux, built from source | yes, x64 or arm64 |
| macOS | npm or Homebrew | Dayhand for macOS, built from source | yes, Apple silicon or Intel |
| Windows | npm, not tested on Windows | none | no: use a free Convex account |
| Android | none | signed APK | not needed: the app works without one |
dayhand, the command line (short name dh), and with it dayhand ui need
Node.js 22.12 or newer:
npm i -g dayhand
or, on Linux and macOS with Homebrew, which brings Node.js along:
brew install maiarowsky/tap/dayhand
npx dayhand --help tries it without installing, and npm rm -g dayhand or brew uninstall dayhand
removes it. Updates, shell completion and manual pages: docs/install.md.
Linux
- Command line and
dayhand ui: npm or Homebrew, as above. On Debian and Ubuntu, debhelper has adhcommand of its own; typedayhandthere. - Server:
dayhand server startruns it on this computer, with no account (Quick start). - App: Dayhand for Linux is built from source. Arch Linux and Omarchy have a package in this repository (not on the AUR); other distributions build it with CMake, a path the project does not test: Dayhand for Linux.
macOS
- Command line and
dayhand ui: npm or Homebrew, as above. - Server:
dayhand server startruns it on this computer, with no account (Quick start). - App: Dayhand for macOS runs on macOS 13 or later and is built from source with Xcode 26 or later. It is not signed for other Macs yet: Dayhand for macOS. Coming soon: a signed, notarized download.
Windows
-
Command line and
dayhand ui:npm i -g dayhandinstalls them; there is no Homebrew here. The code has Windows paths (the key in Windows Credential Manager,ycopying withclip, Notepad as the default editor), but the project's tests do not run on Windows, so the commands anddayhand uiare untested there. -
Server: the local server does not run on Windows. Run it on your own free Convex account: setup opens the browser to sign in to Convex, deploys and signs
dayhandin (Your own server):dayhand server deployThe shell examples in this README use a POSIX shell, for example Git Bash.
-
App: there is no Windows desktop app.
Android
- App: Android 8.0 or newer. Download the
signed APK from GitHub Releases
and allow your browser or file manager to install apps when Android asks; the release includes
SHA256SUMSand the signing certificate fingerprint. Google Play is coming soon. - Build it yourself with JDK 17 or newer and the Android SDK: docs/install.md and android/README.md.
- Server: not needed to start (On the phone); to sync, see Connect the phone.
The iPhone and iPad app is in development and has nothing to install yet.
Quick start
Start your own server on this computer (macOS or Linux). On Windows, use the
Convex account setup instead.
The dayhand package carries the server (the backend/ folder), so there is no repository to clone
and nothing to build. No account is needed for the local server: the first run copies the packaged
backend once to a folder for your user data, downloads the Convex local backend once, deploys Dayhand
to it, signs dayhand in and prints a pairing QR code for the phone.
dayhand server start
A clone of the repository still works, and it is used instead when you run dayhand from it
(Your own server).
For the local server, leave it running and select it explicitly in a second terminal:
export DAYHAND_URL=http://127.0.0.1:3211
dayhand add "Call the accountant" --due "today 14:00"
dayhand
dayhand done 1
dayhand ui
dayhand alone is Today: the task you are working on now, overdue, today and done today. Dates
are English phrases in your time zone (fri 2pm, in 3 days, 2026-11-02), all listed by
dayhand help dates. dayhand ui opens the same plan full screen, and q quits it
(Terminal UI). Stop the server with Ctrl+C; dayhand server start again keeps the
data.
Your agent
The examples below use jq to read JSON responses. Give each agent its own key. Its changes are
signed agent: <name> in the history and the activity log, and you can revoke the key at any time
(dayhand key revoke):
AGENT_KEY=$(dayhand key create claude --scope write --json | jq -r .key)
DAYHAND_API_KEY=$AGENT_KEY dayhand add "Draft the VAT reply" --due "today 16:00" --remind 30
dayhand log --by agent
Tasks can carry acceptance criteria and a plan. An agent claims a task so other agents leave it alone, and a task with criteria is done only when they are met and the agent says what it did:
TASK_ID=$(dayhand add "Send the Q4 invoices" --due "today 17:00" --accept "One PDF per client" --plan "Export, then check the totals" --json | jq -er .id)
DAYHAND_API_KEY=$AGENT_KEY dayhand claim "$TASK_ID" --minutes 30
DAYHAND_API_KEY=$AGENT_KEY dayhand criteria "$TASK_ID" --met all
DAYHAND_API_KEY=$AGENT_KEY dayhand done "$TASK_ID" --summary "3 PDFs sent" --check totals=pass
For agents, --json prints exactly what the MCP tools return (schemas), exit
codes say what to do next, and dayhand prime prints Today, the agent's claims, the approvals it
waits for and its next steps with a short guide, ready for a session-start hook. Over MCP the
same is agent_brief, and three guides walk an agent through one task, from writing it down to
closing it with proof (dayhand://workflow/intake, dayhand://workflow/execution and
dayhand://workflow/finalization). More:
docs/agent-work.md (activity cursors, dependencies, claims) and
docs/cli.md (every command).
A plan kept in Backlog.md task files comes in with
dayhand backlog import backlog --dry-run (then without --dry-run) and goes out with
dayhand backlog export backlog-out: criteria, plan, dependencies and status carry over, and a folder
imported again brings only what is new (docs/backlog-md.md).
You stay in charge of your agents:
- Before a risky step an agent asks (
dayhand ask, the MCP toolrequest_approval). You pick an option on the phone or withdayhand approvals decide. - One switch pauses every agent (
dayhand agents pause). - A policy per agent key allows, asks for or denies each tool (
dayhand policy set). - Work that an agent or an alert proposes waits in an inbox until you accept, merge or reject it
(
dayhand proposals). dayhand health, also a card above Today on the phone, shows what needs a look.
Dayhand records your decisions. It cannot stop what an agent does outside Dayhand.
MCP
The server speaks MCP at /mcp; its available operations are
listed in docs/mcp.md. For Claude Code, with the agent key from above:
claude mcp add --transport http dayhand "$DAYHAND_URL/mcp" --header "Authorization: Bearer $AGENT_KEY"
Any other MCP client works the same way: the address and an Authorization: Bearer header.
docs/mcp.md lists the tools, resources and prompts. The Claude apps connect as a
custom connector with OAuth instead, and you approve each connection on your phone
(docs/oauth.md); that needs a public HTTPS server (below).
There is also a ready Agent Skill that teaches an agent the dayhand commands. It lives in the
repository, and the commands from here on that name repository folders (docs/, macos/, cli/)
run in a clone (if you already have one, skip the git clone line and cd into it):
git clone https://github.com/maiarowsky/dayhand.git
cd dayhand
mkdir -p ~/.claude/skills && cp -R docs/skills/dayhand ~/.claude/skills/
Herdr
If your agents run in Herdr panes, the plugin in herdr/ gives an agent pane
a task from Today and writes the agent's state into that task: in progress, waiting for you, or
finished and ready for you to check. It never marks the task done. Setup:
herdr/README.md.
Build the desktop apps
Both apps are built in a clone of this repository, like the one made for the Agent Skill above.
Dayhand for Linux
On Arch Linux or Omarchy, Dayhand for Linux is built as a package from this repository (it is not on the AUR):
(cd packaging/arch && makepkg -si)
On other distributions it builds with CMake against Qt 6
(docs/install.md); only Arch Linux builds are tested in the
project. Bind dayhand-qt --quick-add to a key in Hyprland and add the Omarchy theme template to
follow your theme's colours: docs/linux.md. More: linux/README.md.
Dayhand for macOS
It needs Xcode 26 or later to build and runs on macOS 13 or later. It is not signed for other Macs yet:
(cd macos && scripts/build-app.sh)
open macos/dist/Dayhand.app
Connect it with a code from dayhand pair, or choose Not now to keep the plan on this Mac.
The morning summary time and default reminders are in Settings. When you complete a repeating task, its next
occurrence shows at once, also on a paired Mac with no network. More:
macos/README.md and docs/macos.md.
Connect the phone
To sync the phone, the CLI and your agents, connect it to your own server. In Settings, under Server, choose Connect to my server and scan the code from
dayhand pair
Release builds of the app connect only over HTTPS, so a server on your computer needs
tailscale serve in front of it (docs/deploy.md).
Tasks you added on the phone before are sent to the server.
Your own server
Dayhand has no shared server to sign up for, and the app has no built-in server address. You run yours in one of two ways:
- On this computer: follow Quick start. Data and keys stay in a private folder.
- On your own free Convex account, also from Windows:
dayhand server deploylogs in to Convex in the browser, deploys, signsdayhandin and prints the server address and a pairing code. This gives a public HTTPS address, which the Claude apps and a phone away from home need. Follow the server update guide to update; keys and data are kept.
See every step first, without changing anything:
dayhand server deploy --dry-run
Costs (nothing on Convex's Free plan), backups, updates, Tailscale and setup by hand: docs/deploy.md. The Convex local backend binary is source-available under FSL-1.1-Apache-2.0; it is downloaded from Convex's GitHub releases at a pinned version and its checksum is verified.
The name
Dayhand was called Helm until backend 0.9.0 and CLI 0.10.0; the old hlm command and HELM_*
names still work with a warning (docs/rename.md). An unrelated to-do app called
DayHand exists for iPhone, iPad and Mac (amouraux/DayHand,
in public TestFlight beta in October 2026). If it reaches the App Store first, this project's
Apple apps would be listed as "Dayhand Planner"; the CLI, npm, Homebrew and Android are not
affected.
Development
backend/ Convex backend: data model, domain operations, MCP endpoint, REST API, webhooks
cli/ dayhand, the command line for people and agents
android/ Android app (Kotlin, Compose)
macos/ Dayhand for macOS (Swift, SwiftUI)
linux/ Dayhand for Linux (Qt 6, QML); see docs/linux.md
herdr/ the Herdr plugin: Dayhand tasks for agent panes
docs/ architecture, MCP, REST API, webhooks, OAuth, calendar feed, pairing, deployment
site/ dayhand.dev: the landing page and the docs from docs/, an Astro site built into site/dist; check it with scripts/check-site.sh --build
To run dayhand from this checkout instead of the npm package, build it and link it onto your
PATH; npm unlink -g dayhand removes the link:
(cd cli && npm ci --ignore-scripts && npm run build && npm link)
The tests start their own throwaway backend:
(cd backend && npm ci --ignore-scripts && npm test)
(cd cli && npm test)
Every command in the sh blocks of this README runs against a local backend with sample data in
scripts/verify-readme.sh. Contributions are accepted under the
Developer Certificate of Origin.
Help
Start with dayhand help and the documentation: quick start,
FAQ and troubleshooting, docs/cli.md and docs/deploy.md.
Dayhand is a personal project. There is no hosted service yet (a hosted backend is planned, with a
waitlist on dayhand.dev) and no support promise. Issues are
for bugs you can reproduce and for feature ideas. Security problems go privately, never in an
issue (SECURITY.md).
License
Dayhand MCP questions
How can an AI agent interact with Dayhand?
Agents can add, plan, and finish tasks over MCP or the dayhand command line using a dedicated API key.
Can I run the Dayhand server myself?
Yes, you can run a server yourself on macOS or Linux with a single command, or use a Convex account on Windows.
How do I distinguish between my changes and an agent's changes?
Every change shows who made it, identifying whether it was made by you, the CLI, or a specific agent.