Kenotex MCP server
{
"mcpServers": {
"kenxcomp-kenotex": {
"command": "npx",
"args": [
"-y",
"kenotex-mcp@latest"
],
"env": {
"KENOTEX_TOKEN": "<kenotex_token>"
}
}
}
}{
"mcpServers": {
"kenxcomp-kenotex": {
"command": "npx",
"args": [
"-y",
"kenotex-mcp@latest"
],
"env": {
"KENOTEX_TOKEN": "<kenotex_token>"
}
}
}
}{
"mcpServers": {
"kenxcomp-kenotex": {
"command": "npx",
"args": [
"-y",
"kenotex-mcp@latest"
],
"env": {
"KENOTEX_TOKEN": "<kenotex_token>"
}
}
}
}{
"servers": {
"kenxcomp-kenotex": {
"command": "npx",
"args": [
"-y",
"kenotex-mcp@latest"
],
"env": {
"KENOTEX_TOKEN": "${input:kenotex_token}"
}
}
},
"inputs": [
{
"id": "kenotex_token",
"type": "promptString",
"description": "Kenotex token",
"password": true
}
]
}{
"mcpServers": {
"kenxcomp-kenotex": {
"command": "npx",
"args": [
"-y",
"kenotex-mcp@latest"
],
"env": {
"KENOTEX_TOKEN": "<kenotex_token>"
}
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsoninstall npx -y kenotex-mcpversion 1.3.1
What it does
MCP server that connects Claude and other coding agents to Kenotex, a native planner for macOS and iPhone. Agents can create, read, and manage todos with categories and recurrence, calendar events, and daily habit check-ins, with all data stored in a local SQLite database on your Mac and synced to iPhone via iCloud.
- An agent creates a todo with a specific category and recurrence pattern, or updates an existing todo's status based on user requests.
- An agent schedules calendar events or retrieves upcoming events to help with scheduling decisions.
- An agent manages daily habits like medication or water intake by creating habits and marking them complete for specific dates or times.
Tools this server exposes
| Tool | Does |
|---|---|
| create_todo | Create a new todo item with a category ID, optional recurrence pattern, and other details. |
| list_todos | Retrieve all todos from the database. |
| get_todo | Fetch a specific todo by ID. |
| update_todo | Modify an existing todo's properties. |
| complete_todo | Mark a todo as complete. |
| delete_todo | Delete a todo from the database. |
| create_event | Create a new calendar event, optionally with recurrence. |
| list_events | Retrieve all calendar events. |
| get_event | Fetch a specific event by ID, including support for recurring event occurrences. |
| update_event | Modify an existing calendar event. |
| delete_event | Delete an event from the calendar. |
| create_habit | Create a daily check-in habit tracker with up to 6 dose times per day. |
| list_habits | Retrieve all habits. |
| get_habit | Fetch a specific habit by ID. |
| update_habit | Modify a habit's properties or set an end date to stop tracking without deleting history. |
| set_habit_check | Mark a habit as checked or unchecked for a specific date, optionally for a specific dose slot. |
| list_habit_checks | Retrieve check-in history for a habit. |
| delete_habit | Permanently delete a habit and its entire check-in history. |
| list_categories | Retrieve all todo categories. |
| create_category | Create a new todo category. |
| add_reminder | Add a reminder to a todo or event. |
| remove_reminder | Remove a reminder from a todo or event. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.