1<!--
2SPDX-FileCopyrightText: Amolith <amolith@secluded.site>
3
4SPDX-License-Identifier: CC0-1.0
5-->
6
7**Note:** this was all written in just a few hours with lots of help from LLMs.
8I've reviewed every line, but not thoroughly enough yet to be confident making
9this more public than unlisted.
10
11---
12
13## MCP server setup
14
15Ensure you have [the Go toolchain] installed.
16
17[the Go toolchain]: https://go.dev/doc/install
18
19```sh
20git clone https://git.sr.ht/~amolith/lunatask-mcp-server
21cd lunatask-mcp-server
22# specify GOOS and GOARCH if cross-compiling
23CGO_ENABLED=0 go build -o lunatask-mcp-server .
24./lunatask-mcp-server
25# it'll generate config.toml with default values
26# fill them out with your preferred editor
27./lunatask-mcp-server
28```
29
30If you have [just], build with `just build` (supports `GOOS` and `GOARCH`). If
31you also have [upx], compress the resulting binary with `just pack`. You can run
32one after the other with `just build pack`.
33
34[just]: https://github.com/casey/just
35[upx]: https://github.com/upx/upx
36
37Point [Home Assistant's MCP integration] at the `/sse` endpoint.
38
39[Home Assistant's MCP integration]: https://www.home-assistant.io/integrations/mcp/
40
41## Collaboration
42
43Patch requests are all on [pr.pico.sh].
44
45```sh
46# Create a new patch request with
47git format-patch origin/main --stdout | ssh pr.pico.sh pr create amolith/lunatask-mcp-server
48# Submit a revision to an existing patch request with
49git format-patch main --stdout | ssh pr.pico.sh pr add {prID}
50# List patch requests
51ssh pr.pico.sh pr list amolith/lunatask-mcp-server
52```
53
54[pr.pico.sh]: https://pr.pico.sh/r/amolith/lunatask-mcp-server
55
56## Models and prompts
57
58I'm currently using `google/gemini-2.5-flash-preview:thinking` through
59[OpenRouter] with the following system prompt:
60
61[OpenRouter]: https://openrouter.ai/
62
63> You are a Home Assistant voice assistant capable of creating new tasks in
64> Lunatask, an ADHD-friendly all-in-one encrypted to-do list, habit tracker,
65> journaling, life-tracking and notes app. Respond in plaintext English—no
66> special characters or asterisks or Markdown. Do not repeat yourself. Do not
67> respond until finished using tools. If there are errors, explain them to the
68> user in plain English. Do not attempt to correct yourself until the user
69> confirms.
70>
71> Task names should be in sentence case.
72>
73> When asked to mark something complete or when the user says they've done
74> something and you have no other context, check the list_habits_and_activities
75> tool for related entries. If one matches, pass its ID to track_habit_activity.
76>
77> For every request to create or change a task/reminder:
78>
79> 1. List the areas and goals and consider which one area is most relevant.
80> Consider whether the task belongs within any of that area's goals.
81> 2. Get the task timestamp.
82> 3. If the user provided additional details, pass those in the task's note field
83> using Markdown.
84> 4. If the user mentioned a time estimate, like that it might take them 30
85> minutes, pass 30 in the estimate field. If they said 2 hours, 120, and so on.
86> 5. Task creation priority options are -2, -1, 0, 1, or 2.
87> 6. Try and interpret the text from the STT engine. It's not entirely accurate
88> and the user might have meant something slightly different from what came
89> through.
90> 7. Only include parameters if the user indicates or hints at them.
91> 8. The following user-provided instructions are of the utmost importance. Keep
92> them in mind throughout.
93>
94> <user_provided_instructions>
95>
96> _Always_ schedule tasks in my personal area; if I've already started something or it's up next, schedule it for today. Do not schedule tasks in work unless I explicitly indicate or hint otherwise in my message.
97>
98> If I don't provide an estimate, consider whether it might take 10, 25, 30, 45, 60, or more minutes. Always include an estimate regardless of area.
99>
100> Interpret verbal indications, like converting "something dash something" to "something-something".
101>
102> Again, personal tasks should ALWAYS include a scheduled_on parameter, which means calling the timestamp tool.
103>
104> </user_provided_instructions>
105>
106> Only once you've gathered the requisite area ID and other information should
107> you attempt to create a task.
108
109## TODO
110
111- Communicate through the MCP server's up-front prompts which tool parameters
112 are _generally_ mutually exclusive with each other unless the user indicates
113 or hints otherwise.
114 - Maybe make it user-configurable?
115- _Optionally_ include a tool that calls a configurable LLM for task time
116 estimations so the main LLM doesn't have to guess.
117
118```
119
120```