goalslot-mcp
goalslot-mcp
GoalSlot용 MCP 서버입니다. AI 어시스턴트에게 목표, 작업, 주간 일정 템플릿, 시간 추적, 공유 타이머, 보고서, 메모, 저널을 자신의 GoalSlot 계정으로 다룰 수 있는 도구를 제공합니다.
stdio로 실행되므로 모든 MCP 호스트가 실행할 수 있습니다. 모델이 도구를 잘 사용하는 방법을 가르치는 네 가지 스킬이 포함되어 있습니다.
설치
먼저 goalslot CLI에 로그인해야 합니다. 이 서버는 CLI가 작성한 자격 증명을 읽기 때문입니다. 자체적으로 로그인 흐름을 실행하지 않습니다.
npm install -g goalslot-cli
goalslot login그런 다음 Claude Code에 MCP 서버를 추가합니다:
claude mcp add goalslot -- npx -y goalslot-mcpClaude Desktop 또는 JSON 구성을 사용하는 모든 호스트의 경우:
{
"mcpServers": {
"goalslot": {
"command": "npx",
"args": ["-y", "goalslot-mcp"]
}
}
}작동하는지 확인합니다:
npx -y goalslot-mcp --list-tools이 패키지는 아직 npm에 게시되지 않았습니다. 게시될 때까지 소스에서 설치하세요: 저장소를 클론하고
npm install && npm run build를 실행한 다음 호스트를node /path/to/goalslot-mcp/dist/cli.js로 지정하세요.
Related MCP server: Chisel Planner
인증 작동 방식
이 서버에는 로그인 흐름이 없습니다. stdio가 프로토콜 채널이므로 서버는 어떤 것도 프롬프트할 수 없으며, 모델에게 토큰을 처리하도록 요청하는 것은 더 나쁩니다. 이미 머신에 존재하는 자격 증명을 읽습니다.
해결 순서:
환경 변수
GOALSLOT_ACCESS_TOKEN(설정되어 있고 비어 있지 않은 경우).$GOALSLOT_CONFIG_DIR/credentials.json.Windows의
%APPDATA%\goalslot\credentials.json.$XDG_CONFIG_HOME/goalslot/credentials.json, 그 외에는~/.config/goalslot/credentials.json.
이 파일은 goalslot login이 작성하며 CLI와 공유됩니다. 형태는 다음과 같습니다:
{
"version": 1,
"apiBaseUrl": "https://api.goalslot.io/api",
"apiUrl": "https://api.goalslot.io/api",
"accessToken": "<jwt>",
"refreshToken": "gsl_rt_...",
"accessTokenExpiresAt": "2026-08-25T12:00:00.000Z",
"refreshTokenExpiresAt": "2026-11-23T00:00:00.000Z",
"tokenId": "<uuid>",
"scopes": ["full"],
"user": { "id": "...", "email": "..." },
"defaultTimezone": "Asia/Karachi",
"weekStartsOn": 1
}apiBaseUrl과 apiUrl은 모두 읽고 동일한 값으로 작성되므로 CLI와 이 서버가 서로 덮어쓰지 않습니다. 알 수 없는 키는 다시 쓰기 후에도 유지됩니다.
CLI 토큰은 typ: "cli" 및 cid 클레임(해지 가능한 토큰 행을 나타냄)을 포함하는 일반 Bearer JWT이며, 모든 일반 API 경로가 이를 허용합니다. 액세스 토큰은 1시간 동안 유효합니다. 401이 발생하면 이 서버는 POST /api/auth/cli/token/refresh에 대해 리프레시 토큰을 회전시키고, 새 쌍을 사용하기 전에 디스크에 원자적으로 기록한 다음 원래 요청을 한 번 재생합니다. 회전은 단일 실행(single-flight)입니다: 리프레시 토큰은 일회용이며, 회전된 토큰을 재생하면 전체 자격 증명이 해지되므로 동시에 두 번의 리프레시가 발생하면 영구 로그아웃이 됩니다.
어떤 수준의 로그에도 토큰, 헤더 또는 Authorization 줄이 기록되지 않습니다.
자격 증명이 없거나 만료된 경우, 모든 도구는 구조화된 NOT_AUTHENTICATED 또는 SESSION_EXPIRED를 반환하여 모델에게 goalslot login을 실행하도록 안내합니다. 토큰을 붙여넣도록 요청하지 않습니다.
헤드리스 및 CI
GOALSLOT_ACCESS_TOKEN은 파일을 완전히 대체합니다. 리프레시가 작동하도록 하려면 GOALSLOT_REFRESH_TOKEN과 함께 사용하세요. 리프레시 토큰이 없으면 리프레시가 비활성화되고 1시간 액세스 토큰이 만료되면 세션이 종료됩니다. 장기 실행 작업의 경우 GOALSLOT_CONFIG_DIR을 설정하고 서버가 파일을 관리하도록 하세요.
도구
읽기 도구 9개와 쓰기 도구 9개. 읽기 도구는 자유롭게 호출해도 안전하며 readOnlyHint로 주석 처리되어 있습니다. 모든 쓰기 도구의 설명은 WRITES.로 시작하며, 여기에 노출된 어떤 것도 사용자 데이터를 삭제하지 않습니다.
읽기
도구 | 기능 |
| 인수 없는 오리엔테이션 호출. 사용자, 플랜 한도 및 현재 사용량, 카테고리 값 문자열, 라벨, 시간대, 오늘 날짜, 현재 주, 실행 중인 타이머. 모든 스킬이 먼저 호출합니다. |
| 목표, 목표 시간, 기록 시간, 진행률, 마감일 및 라벨이 포함된 목표. 선택적 상태, 카테고리 및 라벨 필터. |
| 하나의 목표를 전체적으로, 선택적으로 사용자가 작성한 반성(reflections) 포함. |
| 상태, 목표, 일정 블록 또는 요일로 필터링된 작업. 큰 백로그가 컨텍스트를 넘치지 않도록 제한됨. |
| 주간 일정 템플릿. 요일별로 그룹화되고 시작 시간별로 정렬되며, 요일별 계획된 분 포함. |
| 기간 또는 사전 설정에 대한 개별 시간 항목, 합계 포함. 선택적 목표 필터 및 텍스트 검색. |
| 하나의 |
| 제목 또는 본문 부분 문자열로 메모를 찾거나 ID로 하나를 가져옵니다. 트리 경로를 반환하고 HTML 본문을 마크다운으로 변환합니다. |
| 날짜별로 병합된 저널 항목 및 일일 체크인: 기분, 에너지, 집중, 잘된 점, 방해된 점. |
쓰기
도구 | 기능 |
| 목표를 생성합니다. |
| 상태를 포함한 목표를 업데이트합니다. 의도적으로 |
| 작업을 생성하며, 선택적으로 목표 및 일정 블록에 연결할 수 있습니다. |
|
|
| 이미 소요된 시간을 기록합니다. |
| 공유 서버 타이머를 시작합니다. 조용히 인수하지 않고 |
| 타이머를 시간 항목으로 중지하거나 폐기합니다. |
| 주간 템플릿에서 하나의 블록을 생성, 업데이트 또는 삭제합니다. |
| 한 날짜에 대한 저널 항목과 일일 체크인을 업서트(upsert)합니다. 마크다운 입력, TipTap HTML 출력. |
의도적으로 도구로 만들지 않은 것
목표, 작업 및 시간 항목 삭제; 전체 일정 지우기; 공개 또는 다른 사람과 공유; AI 코치 채팅 엔드포인트; 청구 및 계정 설정; 템플릿 가져오기. 연쇄 효과가 있는 삭제 및 개인 데이터를 게시하는 모든 것은 에이전트가 루프에서 호출할 수 있는 곳이 아니라 사람이 직접 입력하는 곳에 속합니다. GoalSlot 앱 또는 CLI를 사용하세요.
도구가 적용하는 규칙
기간은 정수 분이며, 항상
durationMinutes로 명명되고 절대duration으로 명명되지 않습니다. 읽기에서도durationHours를 표시용 부동 소수점으로 반환합니다. 목표의targetHours는 유일한 예외입니다.날짜는
YYYY-MM-DD형식이며 시간이 포함되면 경계에서 거부됩니다. "오늘"은 UTC ISO 조각이 아닌 사용자 시간대에서 계산됩니다.일정은 반복되는 주간 템플릿이며 날짜가 있는 이벤트가 아닙니다. 관련 도구 설명마다 명시되어 있습니다.
dayOfWeek는 일요일 우선(0 = 일요일)이며, 주간 보고서가 사용하는 월요일 우선 순서와 다릅니다. 둘 다 인라인으로 표시되고 모든 응답에는dayName이 포함됩니다.주간 버킷은 API의 저장된
dayOfWeek열(API 서버 시간대에서 파생되어 하루 차이가 날 수 있음)이 아닌 항목 날짜에서 다시 계산됩니다.
오류
실패는 isError: true와 함께 하나의 JSON 객체로 반환됩니다:
{
"error": {
"code": "PLAN_LIMIT",
"message": "You've reached your FREE plan limit for goals.",
"httpStatus": 403,
"retryable": false,
"remedy": "The account is at its goal limit. Ask the user to pause a goal with update_goal (status PAUSED), delete one from the CLI, or upgrade. Do not retry.",
"details": { "plan": "FREE", "limitType": "goals" }
}
}remedy는 모델을 위한 명령형으로 작성됩니다. 코드: NOT_AUTHENTICATED, SESSION_EXPIRED, PLAN_LIMIT, FORBIDDEN, SCHEDULE_CONFLICT, INVALID_INPUT, NOT_FOUND, RATE_LIMITED, UPSTREAM_ERROR, WRITE_BUDGET_EXCEEDED, READ_ONLY_MODE, TIMER_ALREADY_RUNNING, NO_TIMER_RUNNING.
스킬
skills/에 네 가지 스킬이 포함되어 있습니다. 도구 설명이 담을 수 없는 판단을 제공합니다: 호출 순서, 쓰기 전에 확인할 사항, 말하지 말아야 할 것.
스킬 | 사용 시점 |
| 주간 계획, 목표에 시간 블록 지정, 일정 재조정. |
| 추적되지 않은 시간 따라잡기, 항목 수정, 타이머 구동. |
| 주말, "내 주는 어땠나", 반성 작성. |
| "X에 대해 순조로운가", 목표 축소와 마감일 연기 사이 결정. |
Claude Code에 설치하려면 디렉터리를 스킬 폴더로 복사하세요:
# macOS and Linux
cp -r "$(npm root -g)/goalslot-mcp/skills/"* ~/.claude/skills/
# Windows PowerShell
Copy-Item "$(npm root -g)\goalslot-mcp\skills\*" "$env:USERPROFILE\.claude\skills\" -Recurse클론에서 복사하는 경우 저장소의 skills/*를 복사하세요. 프로젝트 범위도 작동합니다: 저장소 내 .claude/skills/에 넣으세요.
구성
변수 | 효과 |
|
|
| 자격 증명 파일을 완전히 대체합니다. CI 탈출구. |
| 위와 함께 사용할 리프레시 토큰. 회전은 메모리에만 보관됩니다. |
| API 기본 URL. 기본값은 |
| 로그인 시 설정된 시간대를 재정의하는 IANA 시간대. |
| 모든 쓰기 도구가 |
| 프로세스당 허용되는 쓰기 호출 수. 기본값은 25. 무한 루프는 플랜 한도(무료 계정만 백스톱)가 아닌 여기서 중지됩니다. |
HTTP 전송
선택 사항이며 플래그 뒤에 있습니다:
npx -y goalslot-mcp --http --port 7801동일한 도구 레지스트리를 http://127.0.0.1:7801/mcp에서 스트리밍 가능한 HTTP 전송으로 무상태로 제공합니다.
이것은 단일 사용자 및 로컬 전용입니다. 모든 요청은 이 머신의 GoalSlot 자격 증명으로 처리됩니다. 호출자별 인증, OAuth 및 토큰 보관이 없으므로 포트에 도달할 수 있는 사람은 누구나 계정을 읽고 쓸 수 있습니다. 루프백에 바인딩되며 그 상태를 유지해야 합니다. goal-slot-api#55에서 추적되는 호스팅된 다중 테넌트 MCP 서버가 아닙니다. 그 서버는 실제 OAuth 흐름과 사용자별 토큰 저장이 필요하며, 이는 별도의 작업입니다.
stdio가 지원되는 경로입니다.
개발
npm install
npm run typecheck
npm test
npm run build
node dist/cli.js --list-toolsTypeScript strict, ESM, Node 20 이상. 테스트는 스텁된 fetch를 사용하는 vitest이며, 스위트의 어떤 것도 실제 API에 접촉하지 않습니다. CI는 Ubuntu와 Windows에서 Node 20 및 22에 대해 typecheck, 테스트 및 빌드를 실행합니다.
라이선스
MIT
Available Tools
18 toolsgoalslot_create_goalCreate a goalA
WRITES. Creates a new goal on the user's account. category must be a value string from get_context.categories[].value, not a display name. targetHours is the one field measured in HOURS; everything else in this server is minutes. Creating a goal counts against the plan limit reported by get_context. If the account is at its limit this returns PLAN_LIMIT, so check the limit before calling rather than after. Confirm the title, category and target with the user before calling. Do not invent goals from an offhand remark.
Inputs: title (required), category (required), targetHours (required), color, +3 more.
goalslot_create_taskCreate a taskA
WRITES. Creates a task, optionally attached to a goal and to a weekly schedule block. estimatedMinutes is in MINUTES. Creating a task does not log any time; completing it with update_task does. Prefer attaching a goalId when the task clearly serves one, because that is what makes reports and goal progress meaningful later.
Inputs: title (required), notes, goalId, status, +5 more.
goalslot_get_contextGet GoalSlot account contextARead-only
READ ONLY. Call this first, before any other GoalSlot tool, in every session. It returns the facts the other tools require and that you must not guess: the signed-in user, the plan limits and how much of each is already used, the category VALUE strings that create_goal and manage_schedule_block require, the labels, the timezone, today's date in that timezone, the current Monday-first week window, and any timer already running. Do not assume today's date from your own sense of time, and do not invent a category value. Both come from here. Cheap and side-effect free. Call it again after a long conversation rather than relying on a stale copy.
Inputs: no named parameters.
goalslot_get_goalGet one goalARead-only
READ ONLY. Full detail for a single goal, optionally with the user's own written reflections on it. Use this when the conversation is about one specific goal. For "how are all my goals doing", call list_goals instead, which is one request rather than many.
Inputs: goalId (required), includeReflections.
goalslot_get_journalGet journal entries and check-insARead-only
READ ONLY. Returns the user's written journal and their daily check-ins over a window, merged by date. A journal entry is free-written prose plus optional mood and energy. A check-in is the structured version: mood, energy and focus each 1 to 5, plus short "what worked" and "what blocked me" notes. This is what answers "how did my week feel", as opposed to get_report which answers "where did my hours go". Read both when the user asks how a week went. Journal bodies are stored as HTML and converted to markdown here. Quote the user's own words rather than paraphrasing them.
Inputs: date, preset, endDate, include, +1 more.
goalslot_get_reportGet a time reportARead-only
READ ONLY. The single reporting tool. Pick a view; the tool routes to the right report and normalizes the answer. Views: "day_total" is minutes per day, the best default for "how did my week go". "summary" with groupBy goal or category is the per-goal rollup. "detailed" lists every entry grouped by day. "day_by_task" is per day broken down by task. "schedule" compares hours PLANNED in the weekly template against hours actually LOGGED, which is the only way to tell "I never allocated time" apart from "I allocated it and did not honour it". "goals_progress" and "dashboard" are account-wide snapshots that ignore the date range. "weekly" and "monthly" are convenience windows. The response always echoes the resolved date range. Quote that range to the user rather than saying "this week", and never state a number that did not come back from a tool. All durations are minutes. Percentages are already computed; do not recompute them.
Inputs: view (required), preset, endDate, goalIds, +6 more.
goalslot_get_scheduleGet the weekly scheduleARead-only
READ ONLY. Returns the user's weekly schedule template, grouped by day and sorted by start time. The GoalSlot schedule is a REPEATING WEEKLY TEMPLATE, not a calendar of dated events. A block on Tuesday 09:00-12:00 happens every Tuesday. There is no way to schedule something for one specific date. Times are wall-clock HH:mm with no date and no timezone. dayOfWeek is Sunday-first: 0 = Sunday through 6 = Saturday. Call this before proposing any new block, so you can see which windows are already taken.
Inputs: dayOfWeek.
goalslot_list_goalsList goalsARead-only
READ ONLY. Lists the user's goals with target hours, hours already logged, progress and deadline. This is the tool that answers "what am I working on" and "am I behind". loggedHours is accumulated by time entries, so it moves whenever log_time is called with a goalId. Returns ids you must reuse verbatim when calling create_task, log_time or manage_schedule_block.
Inputs: status, labelIds, categories, includeStats.
goalslot_list_tasksList tasksARead-only
READ ONLY. Lists tasks, optionally filtered by status, goal, schedule block or day of week. Statuses are BACKLOG, TODO, DOING, DONE. Results are capped by limit (default 50) so a large backlog cannot flood the conversation; the response says whether it was truncated. dayOfWeek here is Sunday-first (0 = Sunday), which is not the Monday-first ordering that weekly reports use.
Inputs: limit, goalId, status, statuses, +2 more.
goalslot_list_time_entriesList time entriesARead-only
READ ONLY. Returns the individual time entries the user logged over a window, with a total. This is the raw record of what was tracked. For aggregates, comparisons and per-goal rollups use get_report instead, which is one call rather than summing these yourself. Every duration is returned as durationMinutes (whole minutes, authoritative) and durationHours (a float for display only, never send it back). The response always echoes the resolved date range, so check it matches what the user meant before quoting numbers.
Inputs: limit, goalId, preset, search, +2 more.
goalslot_log_timeLog a time entryA
WRITES. Records time the user already spent. This is the workhorse tool for catching up on untracked work. durationMinutes is in whole MINUTES: an hour and a half is 90. date is a calendar date in the user's timezone, taken from get_context.today, never guessed. When goalId is set this ALSO increases that goal's logged hours. That is usually what the user wants, but it means a wrong goalId quietly corrupts goal progress, so confirm the goal before logging. Never invent a duration. If the user did not say how long something took, ask. Restate the minutes back in hours when you confirm, so a units mistake is visible. Entries count against the per-day task limit on free plans. Use dryRun true to show a batch to the user before committing it.
Inputs: date (required), taskName (required), durationMinutes (required), notes, +5 more.
goalslot_manage_schedule_blockCreate, update or delete a schedule blockA
WRITES. Creates, updates or deletes one block in the weekly schedule template. The GoalSlot schedule is a REPEATING WEEKLY TEMPLATE, not a calendar of dated events. A block on Tuesday 09:00-12:00 happens every Tuesday. There is no way to schedule something for one specific date. Adding a block therefore changes every future week, not one date. Say that back to the user before you commit a plan. Overlapping an existing block is rejected with SCHEDULE_CONFLICT. On a conflict, re-read that day with get_schedule and shift your proposal. Never delete the incumbent block to make room without asking. Use dryRun true to validate a whole proposed week and show it to the user before writing anything. Blocks count against the plan limit in get_context, so stop one short of it rather than erroring into it. action "delete" removes a single block. There is no way to clear the whole schedule from this server, deliberately.
Inputs: action (required), color, title, dryRun, +8 more.
goalslot_search_notesSearch notesARead-only
READ ONLY. Finds notes by a substring of their title or body, or fetches one note by id. Notes are a tree, so every result carries its full path such as "Work / Meetings / Standup". Bodies are stored as HTML and are converted to markdown here, then truncated to maxChars, so long notes come back readable rather than as a wall of tags. With no query this lists the user's notes without their bodies, which is the cheap way to see what exists before pulling one. This server cannot create, edit, delete or share notes. Say so rather than looking for another tool.
Inputs: limit, query, noteId, maxChars, +1 more.
goalslot_start_timerStart the timerA
WRITES. Starts the shared GoalSlot timer for this account. The same timer the user sees in the web and mobile apps, not a private one. Only one timer can run at a time. If one is already running this returns TIMER_ALREADY_RUNNING with what it is tracking and how long it has been going. Do not pass takeOver to get past that on your own: takeOver DISCARDS the running session and its elapsed time is lost with no time entry written. Show the user what is running and let them choose to stop it or replace it. Attach goalId when the work belongs to a goal, so stopping the timer credits that goal.
Inputs: notes, goalId, taskId, takeOver, +2 more.
goalslot_stop_timerStop or discard the timerA
WRITES. Stops the running timer and converts it into a time entry, or discards it. Stopping is atomic and credits the linked goal, so the goal's logged hours go up by the elapsed minutes. Duration is floored at 1 minute and capped at 12 hours: a session left open overnight writes 12 hours, not the real elapsed time, and the response says so via "capped". discard true writes nothing at all and the elapsed time is lost. Only use it when the user says the timer was started by mistake. Attribution fields sent here override whatever the timer was started with.
Inputs: notes, goalId, taskId, discard, +2 more.
goalslot_update_goalUpdate a goalAIdempotent
WRITES. Updates fields on an existing goal, including its status. There is deliberately no way to set loggedHours here. Logged hours are accumulated from time entries; to change them, add or correct a time entry with log_time. There is no archived status. PAUSED is how the user shelves a goal without deleting it. Deleting a goal is not available as a tool at all; tell the user to run the CLI if they want one gone. Only send the fields that should change.
Inputs: goalId (required), color, title, status, +4 more.
goalslot_update_taskUpdate, complete or restore a taskAIdempotent
WRITES. One tool for the whole task lifecycle, selected by action. action "update" edits fields. action "complete" marks the task done AND creates a time entry for actualMinutes, which also increases the linked goal's logged hours; it counts against the per-day task limit. action "restore" reopens a completed task. actualMinutes is required for complete and is in whole MINUTES. Never guess it: ask the user how long the task actually took.
Inputs: action (required), taskId (required), date, notes, +9 more.
goalslot_write_journalWrite a journal entry or check-inAIdempotent
WRITES. Saves the user's journal entry and daily check-in for one date. Both are upserts keyed by date. IMPORTANT: mode "replace" (the default) REPLACES that day's whole journal body. Use mode "append" to add to what is already there. If the day may already have content and the user did not ask you to overwrite it, append. content is markdown and is converted to the HTML the GoalSlot editor stores. Write in the user's voice, using their words, not a summary of them. focus, worked and blocked are part of the check-in, and the check-in requires mood, energy and focus together. Supplying only some of the three is rejected rather than guessed at. Never invent a mood, an energy level or a reflection the user did not express.
Inputs: date (required), mode, mood, focus, +4 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 18 tools
Each tool targets a distinct resource and action (e.g., log_time vs. stop_timer, get_report vs. list_time_entries, get_schedule vs. manage_schedule_block). The overlapping cases are clearly differentiated by descriptions, such as manual logging vs. timer-driven logging, and raw entries vs. aggregated reports. No two tools appear to do the same thing.
All tools follow the 'goalslot_' prefix plus a consistent snake_case verb_noun pattern (e.g., get_goal, create_task, stop_timer). The verb choice is uniform across read (get/list/search) and write (create/update/start/stop/manage/log/write) operations. There are no stylistic deviations or mixed conventions.
18 tools cover a broad domain (goals, tasks, schedule, time tracking, reporting, journal, timer, notes). While this falls slightly above the typical 3–15 'well-scoped' range, the count is justified by the variety of features; each tool has a clear purpose and none are redundant. It feels comprehensive without being bloated.
The core workflows are covered: goal lifecycle (create/update, though delete is deliberately absent), task lifecycle (create/update/complete/restore, but no delete), schedule management (create/update/delete), time logging (manual and timer), reporting (multiple views), and journaling. However, there are no tools to delete or edit time entries, and goals/tasks cannot be fully removed, which are notable gaps for a productivity domain. The server explicitly documents these limitations, but they still create dead ends for agents.
Maintenance
Related MCP Connectors
Your planner in every AI chat: tasks, calendar, docs, habits, goals and memory, over MCP.
Official Akiflow MCP for tasks, calendars, scheduling, time slots, and meeting transcripts.
Connect any AI agent to 1,000+ apps and 27,000+ actions through one remote MCP server (OAuth).
Zero-setup MCP gateway securely connecting AI to your tools with authentication and workflows
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to interact with ExecuFunction's project management, knowledge base, code indexing, and calendar tools via MCP, allowing natural language management of tasks, notes, and code.MIT
- AlicenseNot gradedqualityDmaintenanceEnables authenticated MCP clients to manage projects, tasks, habits, and daily capacity through tool calls.8 npmISC
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to create, read, and manage tasks and projects in a personal todo system through MCP tools.1MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to connect to the OnTime personal workbench via MCP to manage tasks, projects, and goals through natural language, including creating sprint projects, logging progress, and querying workbench state in real time.1-