MCP App Store
by KeenEthics
Griply icon

Griply MCP Server for Claude and ChatGPT

By Griply

Overview

Griply is a goal-first planner. You set goals with a target and a deadline, group them under life areas, and link the projects, habits and tasks that move them forward. This connector brings that plan into Claude, so you can work in Griply from the chat you already have open. Ask Claude what's on your agenda today, how consistent you were with your habits this month, or whether you're on track for a goal. Claude reads your life areas and visions, your goals and their pace against the deadline, and your projects, habits, tasks and focus blocks, plus what you completed up to 12 months back. With "Read and change" access, Claude also records what you tell it. Say "Ran 8 km and skipped meditation today" and it logs both. Ask it to add a task for tomorrow at 9:00, move your gym habit to Monday, Wednesday and Friday, or find two hours this week for a project, and it updates Griply. Changes show up in the Griply apps right away. Larger changes come as a proposal first. Put your goals and habits in one message and Claude proposes a plan, shown as a tree of life areas, goals, projects, habits and first tasks. Nothing is saved until you confirm it. Where a target or deadline is missing, Claude suggests one and labels it as a suggestion. Anything Claude deletes goes to Griply's Trash, where you or Claude can restore it. The connector comes with 12 ready-made prompts, including plan_my_day, weekly_review, am_i_on_track, break_down_goal and set_up_from_braindump. You'll find them in Claude's prompt menu. You pick the access level when you connect: "Read only" or "Read and change". Disconnect at any time from the MCP server screen in Griply's settings. Claude doesn't read or change events in your Google or Outlook calendar. Requires Griply Premium, with a 7-day free trial for new users. The MCP server is in beta. Griply runs on iOS, Android, Mac, Windows and the web.

How to connect

  1. Claude: Open the Griply listing in the Claude connectors directory and choose Connect. Claude listing Griply exposes 28 tools here.
  2. ChatGPT: Open the Griply listing in the ChatGPT app directory and choose Connect. ChatGPT listing Griply exposes 29 tools here.

Tools

apply_plan

ChatGPT
Writes a plan of new structure in one go: new life areas, text added to existing life areas’ visions, goals with a metric and their subgoals, projects, habits, repeating tasks and one-off tasks, with the links between them and to existing life areas and goals. Call it once the user has seen the previewed plan and its warnings and confirmed it, without a second preview; a yes given before the preview is not that confirmation. preview_plan checks the same input without writing. At most 100 items. For one new task, habit or repeating task use create_tasks, for one goal create_goal, for one project create_project, for one life area create_life_area. A new life area is only for an area of life none of the user’s life areas covers; a value such as "freedom" is vision text on an existing one. A new life area gets no vision text here: the user adds that in the Griply app. A value or a picture of a good life is vision text; a result measurable with a number is a goal; work that is done when its tasks are done is a project; something that repeats on a schedule is a habit, or a repeating task when it should not be tracked as a habit; one action is a task. A goal or project can get task sections, such as phases, with its tasks in them. The write is atomic: when any item is wrong nothing is written, and the answer lists every error. Items of the plan point at each other by ref (parentRefs, goalRefs, goalRef, lifeAreaRefs, lifeAreaRef, sectionRef), existing ones by the ids get_hierarchy and get_goal give. Vision text is only ever added after the current vision. Every target, range, amount, deadline or date the user did not give is one you propose: label each as your suggestion when you show the plan. It cannot tag items, or change existing items beyond linking its new items to them and putting its tasks in their sections; tag its tasks and habits afterwards with update_tasks and update_habits. A habit moves only a habit-completion goal it serves, or the goals its On complete actions name (set in the Griply app). The answer gives the new ids per ref (life areas, goals, projects and their sections) and per index (habits, tasks). Write new names in the language the user writes in, not their account’s. Pick a goal’s metric.kind by what it measures. unit: a natural unit (money, km, pages) reached as a target or kept within a range (a weight, a budget). completedTasks: the tasks are the progress. subgoalProgress: distinct sub-outcomes, each its own goal. habitCompletion: the weekly completion rate of the habits linked to it (update_habits addGoalIds, or a plan habit’s goalIds / goalRefs). subTarget: a stretch of a parent goal’s number, such as the first 25k of 100k, logged on that parent. habits[].repeat takes kind days, weekdays, monthly, yearly or timesPer. These kinds and their bounds are everything the app’s repeat editor makes, and Griply stores no other rule: not two weekdays of the month such as the 2nd and 4th Tuesday, not several months a year, not hourly, not ending after a number of times. When the user asks for one that these cannot express, say so, offer the nearest options (two repeating tasks, one per weekday, is one of them) and create nothing until the user has chosen. When a request fits two, such as every 2nd Tuesday (every other week, or the second Tuesday of the month), ask which.

complete_tasks

ChatGPT
Use it when the user says they did a task ("the offer is sent"). Marks up to 25 tasks or focus blocks as done. For a repeating task or a habit it marks one day, today unless date says otherwise, and fills a habit up to that day’s target; use log_habit to log a different value. Completing a task linked to a goal moves a Completed tasks goal. Completing a habit day also runs the habit’s On complete actions, as the app does; goalsChanged names the goals they logged a value on, so never log that value again with log_progress. A focus block moves no goal: its completion records the time as spent. Doing it twice changes nothing.

create_focus_blocks

ChatGPT
Creates up to 25 focus blocks in one call. A focus block is time on the calendar for a goal or project, life area, tag or smart list, without choosing the task yet; time for one specific task is that task’s start time and duration (update_tasks), and a new appointment with other people is a calendar event, which Griply does not create; one already stored here is a task. Give each block the most specific target that fits (a project before its goal, a goal before its life area), a day, a start time and a duration; its name is the target’s, as in the app. Read get_planning first and place blocks in its free time. It does not show the user’s Google or Outlook appointments: ask about those when they matter, and never place a block on time the user says is reserved as an event, where tasks get a start time inside it instead. Focus blocks do not repeat: for every Tuesday, create one block per week for the next 4 weeks and tell the user that blocks do not repeat and which weeks you planned. A block shows on the Griply calendar and, when the user syncs tasks to a calendar, there too. Answers one result per block: its new id, its day, start, end and target, or what to fix.

create_goal

ChatGPT
Creates one goal: a result you can measure with a number by a date, linked to the goals it contributes to and its life areas. Work that is done when its tasks are done is a project: create it with create_project. A value or a picture of a good life is a vision, not a goal; something that repeats is a habit: create it with create_tasks and repeat. Call get_hierarchy first so an existing goal is not duplicated. A habit moves a goal only as a habit-completion goal it serves, or through On complete actions set in the Griply app. A stretch of a parent goal’s number, such as the first 25k of 100k, is a sub target under that goal (metric.kind subTarget), never a separate goal logged on its own. Without a target or range from the user, propose one labelled as your suggestion and let them confirm it before you write it.

create_life_area

ChatGPT
Use it when the user asks for a new life area: an area of their life, such as "Music" or "Volunteering", that none of their life areas covers. Before creating one, read the life areas get_hierarchy lists and use one that fits, also when it differs only in case, spelling or language. When one fits, name it and ask whether the user still wants a second one; create it only when they say so. A value or wish such as "freedom" or "balance" is vision text on the life area it belongs to, not a new life area. A label for tasks across life areas, such as "Errands", is a tag: create_tags. Archived life areas show only with get_hierarchy’s includeArchived; bring one back with update_item’s archived false rather than making a twin. Creates one life area with an optional color and the app’s placeholder icon, which the user can change in the Griply app; it comes last in their order of life areas. For a new life area with goals, habits or tasks in it, give it in apply_plan’s lifeAreas instead. Answers its id, to link goals, projects, habits and tasks to it. created false means an earlier call with the same clientRequestId made it: use its id and do not create it again.

create_project

ChatGPT
Creates one project: work that is done when its tasks are done, with nothing to measure. It may contribute to goals and sit in life areas, or stand on its own. A result you can measure with a number by a date is a goal: create it with create_goal. Call get_hierarchy first so an existing project is not duplicated. Add its tasks with create_tasks, or create the project and its tasks together with preview_plan and apply_plan.

create_sections

ChatGPT
Use it when the user wants a goal, project or life area split into parts: adds task sections, named groups such as phases, stages or headings, that its task list shows its tasks under. For a goal or project that does not exist yet, give its sections in apply_plan instead. Smart lists, tags and the inbox have no sections, and an archived item takes none. Before adding one, check the sections get_goal (goal or project) or get_hierarchy (life area) lists and use one that fits; a name may repeat when the user asks for it. Up to 25 per call; new sections come after the existing ones, and the item’s task list is then grouped by section instead of any other grouping, as in the app. Answers each section’s id, for sectionId on create_tasks and apply_plan or moveToSectionId on update_tasks. It cannot rename, reorder or delete a section: point the user to the Griply app for that. created false means an earlier call with the same clientRequestId made them: use their ids and do not create them again.

create_tags

ChatGPT
Creates up to 25 new tags. A tag labels tasks and habits across goals and life areas, such as a context ("Calls", "Errands"); goals, projects and life areas have no tags. Before creating one, check the tags get_hierarchy lists and use one that fits, also when it differs only in case, spelling or language. Create one only when the user asks for a tag that none of those matches. Answers each tag with its id, to link with tagIds on create_tasks, addTagIds on update_tasks and update_habits, or a focus block’s target. created false means an earlier call with the same clientRequestId made that tag: use its id and do not create it again.

create_tasks

ChatGPT
Creates up to 25 tasks, habits or repeating tasks in one call. A task is one action, optionally planned for a day and time, with reminders, a deadline, priority, tags, and links to the goals, projects and life areas it serves. A goal is a measurable result and a project is work that is done when its tasks are done: link the task to what it serves rather than leaving it in the inbox. With repeat it is a repeating task, or a habit with showInHabitList true; change those later with update_habits. With sectionId it goes into a task section of a goal, project or life area. With parentTaskId it creates a subtask, a named step of an existing task. Answers one result per item, with its new id and type or the reason it was not created; an error beside created true says what of it was not saved.

delete_items

ChatGPT
Moves up to 25 items to Griply's Trash, never permanently: restore_items brings them back. A task takes its subtasks along. A goal or project takes its sub-goals and projects that have no other parent, and the tasks and habits linked to nothing else, completed ones too; tasks also linked elsewhere stay. A life area or tag goes alone: its goals and tasks stay and show without it until it is restored. A repeating task or habit goes as a whole, not one day. A completed focus block cannot be deleted. Delete only what the user asked for, never to recreate something in another shape. The answer lists what went to the Trash with each item: tell the user, and offer restore_items. Doing it twice changes nothing.

get_completed

ChatGPT
Returns what the user got done on a range of days, at most 12 months back: completed tasks, completed focus blocks, values logged on goals, and the days habits and repeating tasks were done. Optionally only what belongs to a goal or project and everything under it, or to a life area and its goals. Newest day first. Per day: its completed tasks, its focus blocks (time reserved for a goal, life area, tag or smart list) and progress, where a goal stood after each value logged that day, in its unit. Habits and repeating tasks are listed once under recurring, with each day they were done and, when more than one, how many. Skipped and failed habit days are not listed. totals counts the whole range: give those numbers instead of adding up days, and still name the tasks. A page holds at most 200 items; total counts every item in the range, and when nextCursor is present, call again with it, and the same range, for the next page. Defaults to the last 7 days, today included.

get_goal

ChatGPT
Returns one goal or project in detail: its metric with its current and projected value, progress, dates, impact, the goals it contributes to, its life areas, its subgoals and projects, and its task sections. Progress moves through logged values, completed tasks, subgoals or its habits’ weekly completion rate, depending on the metric; a habit’s On complete actions can log values on it too. It carries the same signals as each goal in get_hierarchy: pace against the deadline (paceStatus, timeElapsedPercent, requiredRate), where the last 28 days’ pace lands it (projectedPercent, projectedDate), impactPath, activity (lastActivityAt, nextActionAt), the open work under it (openTaskCount, openTaskMinutes, unestimatedTaskCount), the time planned for it this week (plannedMinutesNext7d), how the habits under it went (linkedHabitRate across linkedHabitCount habits) and planIssues (noPath: nothing open under it; itemAfterDeadline: work under it after its deadline; nothingPlanned: deadline within 28 days, nothing planned); nextActionAt before today is overdue, and nextActionTask is the task to name as the next step. A goal measured by its tasks has metric.current done of metric.target tasks. A goal kept within a range has metric.range and metric.onTrack instead of a target, and progressPercent 100 when on track, 0 when not. A habit-completion goal’s metric.current is its habits’ rate (%) in the last complete week, against metric.target (%). A sub target measures a stretch of metric.mainGoal’s values, where its entries are stored. A project (type project) is always measured by its tasks, and one at 100% stays open until the user completes it. Use those as given.

get_habit_stats

ChatGPT
Returns each active habit’s statistics for one week, month, quarter or year, as the app’s habit statistics show them, and how it has been going lately: for habit patterns, and for which habits support a goal. Per habit: completed (what was logged; a count habit’s values add up) against target (what its schedule asked in the period; skipped days and the days still to come in a running period are in it, as in the app), rate (completed against target, can pass 100), skipped and failed days, and perfect: how many weeks, months or years (perfectUnit) met their target. A habit counted per week covers the whole weeks a month, quarter or year touches, as the app counts it: countedFrom and countedTo. Its signals: completionRate4w, that rate over the four full weeks before this week; trend, rising or falling when that rate moved more than 10 points from the four weeks before, else steady; weakestWeekday, over the last 12 full weeks the weekday it is missed most (a habit on set days; a skipped day is no miss) or done least (a habit done a number of times per period), absent without one clear day; lastCompletedAt and daysSinceLastCompleted, so a habit that stopped shows without counting days. goals and lifeAreas are what it serves. A habit moves only a habit-completion goal it serves, or the goals its On complete actions name (set in the Griply app). Use the numbers as given. Use it for every question about how habits went or which day one is skipped; get_trends gives work per week or month.

get_hierarchy

ChatGPT
Lists the user’s life areas, goals and projects, habits, tags and smart lists, with their ids and the signals to judge them by. Without lifeAreaId or goalId: every life area, the top-level goals, every open project and the completed ones no listed goal is above, every active habit, the tags, the smart lists (saved filters a focus block can reserve time for) and the account’s own numbers. With lifeAreaId: that life area with its whole vision and every goal and project in it, which a check-in on that life area measures against its vision; with goalId: that goal or project with everything under it. Call it before creating or linking anything, to use existing items instead of duplicating them; each goal names its direct sub-goals and projects, so use the most specific one the user names. Completed goals and projects are included and marked; archived ones only when asked. When nextCursor is present, call again with it and the same arguments for the rest; life areas, tags, smart lists and the account’s numbers come on the first page. Life areas: vision (the first 250 characters, visionTruncated when there is more), activeGoalCount (open goals in it, as the app’s life-area overview counts them), goalsBehind (of those, behind or past their deadline), and attentionShare over the last 7 and 30 days (its share of the completed one-off tasks and focus blocks and of their minutes; a task counts for every life area it reaches, so shares overlap) and sections (its task sections; a goal’s or project’s come with get_goal). Goals: pace against the deadline (paceStatus, timeElapsedPercent, requiredRate), where the last 28 days’ pace lands it (projectedPercent on the deadline, projectedDate when the target is reached), impact and impactPath (top-level goal first; a high under a low matters less), activity (lastActivityAt; nextActionAt, the first open planned day under it, overdue when before today, with nextActionTask, the task to name as the next step), the progress a goal measured by its tasks counts (metric.current done of metric.target), the open work under it (openTaskCount; openTaskMinutes of those with a duration, unestimatedTaskCount of those without), plannedMinutesNext7d (tasks with a duration and focus blocks from today through the six days after), linkedHabitRate (its habits as one over the four full weeks before this week, across linkedHabitCount habits) and planIssues (noPath: nothing open under it, no sub-goal, project, habit or task; noDeadline; itemAfterDeadline: open work under it planned or due after its deadline; nothingPlanned: the deadline is within 28 days and nothing under it is planned). Projects are listed apart from goals, in projects: work that is done when its tasks are done. Each carries the goals’ signals except type, linkedHabitRate and linkedHabitCount. A project contributes to any mix of goals (parents) and life areas, or to none and stands on its own; lifeAreas are its own, or else its first parent’s. It has no sub-goals and no metric to choose: its progress is always the share of its tasks completed (metric.current done of metric.target), and one at 100% stays open until the user completes it. Habits: what they serve, completionRate4w and trend; get_habit_stats has the rest. The account: alignment (the share of the one-off work completed in the last 7 and 30 days that served a goal) and dailyThroughput (tasks and minutes completed per day over the 14 days before today, to plan a realistic day). A goal kept within a range has metric.range and metric.onTrack instead of a target (progressPercent 100 or 0); a habitCompletion metric is a weekly rate in %; a subTarget logs on metric.mainGoal. Only a habit-completion goal or On complete actions (set in the app) let a habit move a goal. Use the numbers as given.

get_planning

ChatGPT
Griply's planning: returns what is planned in Griply on one or more days, from today up to 31 days, everything the user has planned whatever filters their app shows. It reads only and never creates or changes calendar events. Per day: its todos in the order the user’s Upcoming shows them, focus blocks (time reserved for a goal, life area, tag or smart list, without a task chosen yet), and the time Griply has nothing planned in, from now, in a work window (08:00–18:00) and a private window (18:00–23:00). It never shows events from the user’s Google or Outlook calendars, so that free time does not know their appointments outside Griply: ask about those when they matter. Habits and repeating tasks are listed once under recurring, with each day and time they fall on and today’s progress. When the range starts today, overdue work comes first: at most 50, with the total. Completed work is only counted. postponeCount on a todo: how often its planned day moved to a later day; absent when never. Times are HH:mm in timeZone, and an end past midnight reads 23:59. Which days the user works is not known: go by what the user says, and ask when it matters. A long range can come back shorter: when nextFrom is present, call again with from set to it for the remaining days. Use it to plan a day or week, find free time, or see what is planned when. Today’s tasks are those planned today; the overdue group is separate and belongs to a request only when the user names overdue work.

get_profile

ChatGPT
Returns the user’s time zone, today’s date and the current time in it, and the day their week starts. Use it when you need one of these before another call; every tool that reads dates also answers timeZone and today.

get_tasks

ChatGPT
Returns up to 25 tasks or habits in detail in one call: use it once for all the tasks you need, never one call per task. Each answers its description, planned day and time, duration, deadline, priority, the goals, life areas and tags it is linked to, a todo’s reminders (the user’s default when it has none of its own: defaultReminders true), its subtasks and the task sections it sits in. postponeCount on a todo: how often its planned day moved to a later day; absent when never. A habit or repeating task also answers its schedule (how it repeats, its target per day, time and reminders), as update_habits takes them. Ids that are not the user’s tasks or habits, or are in the trash, come back in notFoundIds; when the answer would grow too long, the rest come back in moreTaskIds, to ask for in a next call.

log_habit

ChatGPT
Use it when the user tells you they did, skipped or missed a habit. Logs a habit for one day, today or earlier, never ahead: done (up to the day’s target, or the value given), skipped, failed or cleared; each replaces what the day held. Logging the same thing twice changes nothing. A logged day also runs the habit’s On complete actions, as the app does; goalsChanged names each goal they logged a value on or took one back from. Never log that value again with log_progress; a goal the report measures that goalsChanged does not name still needs log_progress. No goal moves with a habit otherwise, except a habit-completion goal it serves, through its habits’ weekly completion rate.

log_progress

ChatGPT
Use it when the user reports a result that measures a goal (a distance run, an amount saved). Logs progress on one unit-based goal (a natural unit such as money, kilometres or pages, logged towards a target or kept within a range) or sub target: value sets the new total, delta adds to it: value when the user says where they stand now (a balance, a weight, a personal best such as their longest run), delta when they report an amount on top (km run this week, money put aside today); ask when you cannot tell. For a day that happened, today or earlier. A goal that moves with its completed tasks, through its subgoals or with its habits’ completion rate, or a project, cannot be logged on. A sub target logs on its main goal, as the app does, and loggedOn names it: log a report once, on the sub target or on its main goal. Tasks never count towards a unit-based goal, and a habit only through its On complete actions: a goal that log_habit or complete_tasks just named in goalsChanged already has that value. A goal kept within a range answers range and onTrack instead of start and target. Reaching the target does not complete the goal: ask the user before completing it. Every call adds an entry, so repeating it logs twice unless it carries the same clientRequestId. The answer gives current, the total as the app shows it, which is the latest entry by date: an entry for an earlier day counts towards current unless a later value (an entry that sets the total) replaces it; an earlier delta still adds to a later total built from deltas. Compare current with what you expected instead of assuming. repeated: true means this clientRequestId was logged before and nothing was added.

preview_plan

ChatGPT
Checks a plan of new structure without writing anything; it takes the same input as apply_plan. For one new task, habit or repeating task use create_tasks, for one goal create_goal, for one project create_project, for one life area create_life_area. It answers valid (whether apply_plan would write it as it is), every error with its fix, and warnings, which never stop a plan: raise each with the user when you show it. The plan comes back with every link named. Show it once, with every target, range, amount, deadline or date you proposed marked as your suggestion; when the user then confirms, call apply_plan with the same plan, never preview_plan again. Write new names in the language the user writes in, not their account’s. Pick a goal’s metric.kind by what it measures. unit: a natural unit (money, km, pages) reached as a target or kept within a range (a weight, a budget). completedTasks: the tasks are the progress. subgoalProgress: distinct sub-outcomes, each its own goal. habitCompletion: the weekly completion rate of the habits linked to it (update_habits addGoalIds, or a plan habit’s goalIds / goalRefs). subTarget: a stretch of a parent goal’s number, such as the first 25k of 100k, logged on that parent. habits[].repeat takes kind days, weekdays, monthly, yearly or timesPer. These kinds and their bounds are everything the app’s repeat editor makes, and Griply stores no other rule: not two weekdays of the month such as the 2nd and 4th Tuesday, not several months a year, not hourly, not ending after a number of times. When the user asks for one that these cannot express, say so, offer the nearest options (two repeating tasks, one per weekday, is one of them) and create nothing until the user has chosen. When a request fits two, such as every 2nd Tuesday (every other week, or the second Tuesday of the month), ask which. Errors: more than 100 items, a ref no life area, goal, project or section of the plan has, an id that is unknown or in the Trash, anything under a project, a goal under itself, more than one link on a task or a repeating task (a section names its own), a habit starting before today, and the rules a single goal or task follows. Warnings: a life area, goal, project or habit that already exists under the same name (with its id and status), two items with the same name under one parent, a goal without a deadline or with a passed one, a goal with nothing under it, an item planned or due after the deadline of its goal, an archived goal or life area as a target, and vision text the vision already holds.

restore_items

ChatGPT
Brings up to 25 items back from Griply's Trash, by the type and id delete_items answered. Items deleted earlier or in the app are restored from Griply's Trash in the app; no tool here lists the Trash. A goal or project brings back the sub-goals, projects, tasks and habits that went to the Trash with it; a task brings back its subtasks. Something restored while its goal or life area stays in the Trash shows without it until that is restored too. Doing it twice changes nothing.

search_tasks

ChatGPT
Finds tasks and habits by text and/or by where they belong: a goal, a project, a life area, a task section, a tag, the inbox, or overdue. Give a query, a filter, or both; filters combine. Open items only unless includeCompleted is set. Results come newest first, 50 per page by default; pass nextCursor for the next page. Use it to find the id of a task you only know by name. It answers names, dates, priority and links only: read descriptions, subtasks, reminders or schedules with one get_tasks call for all the tasks you need. A goal, project or life area filter covers everything under it, and every task names its goals and life areas, so one search per life area replaces one per goal. postponeCount on a todo: how often its planned day moved to a later day; absent when never.

uncomplete_tasks

ChatGPT
Undoes a completion for up to 25 tasks or focus blocks: a task or focus block becomes open again; for a repeating task or a habit the day, today unless date says otherwise, is cleared, which also takes back what the habit’s On complete actions logged on goals (goalsChanged names them). Doing it twice changes nothing.

update_focus_blocks

ChatGPT
Moves, resizes or retargets up to 25 existing focus blocks in one call; a field left out stays as it is. A focus block is time on the calendar for a goal or project, life area, tag or smart list, without choosing the task yet; time for one specific task is that task’s start time and duration (update_tasks), and a new appointment with other people is a calendar event, which Griply does not create; one already stored here is a task. A new date keeps the block’s time, a new start keeps its length, and a new target points the block at another goal or project, life area, tag or smart list and gives it that name, such as a generic block one goal now fills. Moving a block does not move the tasks time-blocked inside it: move those with update_tasks in the same confirmed plan. A completed block is the record of time spent and is not changed; complete or reopen a block with complete_tasks or uncomplete_tasks, and delete one with delete_items. A block synced to a calendar moves there too. Answers per block which fields changed (none when it already read that way) and how it reads now: its day, start, end, duration, target and name, or what to fix.

update_habits

ChatGPT
Changes up to 25 habits and repeating tasks in one call; a field left out stays, and each field names the value to end up with, or for links and tags what to add or take off. It changes how one repeats, its target per day, start time and duration, reminders, its tags, the goals, projects and life areas a habit serves, whether it is a habit and shows in the task lists, which days it is planned this period (planDays, without changing the rule), and archives it or completes it forever. A new rule or target applies from today unless the user asks for the schedule start; logged days never change. A habit or repeating task synced to a calendar changes there too. Linking a habit to a goal moves its progress only when the goal measures its habits’ weekly completion rate; On complete actions are set only in the Griply app. Read them first with one get_tasks call for all the habits you change. Moving one occurrence is update_tasks. Answers per item which fields changed (none when it already read that way; repeat is named too when a rule counted from today now lands on other days, even if only the target was sent), appliedFrom for a new rule or target, for planDays each period touched with its planned days from today on, after a schedule change the next five planned days with their weekdays, and after a tag change the tags it has now; or what to fix.

update_item

ChatGPT
Changes one goal, project or life area; a field left out stays as it is. A goal or project takes name, description, startDate, deadline, impact, target (a unit-based goal or sub target in its unit, a habit-completion goal as a weekly rate 0–100), range (only a goal kept within one; the complete new range), metric (only a goal without one), replaceParentGoalIds and replaceLifeAreaIds (each the complete new set: to move a goal under another goal, give its replaceParentGoalIds and replaceLifeAreaIds: []), completed and archived. A life area takes name, archived and appendToVision, which adds text after its vision and never replaces it. Completing keeps the progress as it is; archiving a goal archives its tasks and habits too; a goal moved under an archived goal is archived with it. A frozen goal can only be archived. The answer gives changed (the fields that changed; [] when all already matched), previous (their old values, to undo with this tool), archived (also when only a goal above it is, named in archivedThrough) and the values that result. Repeating a call changes nothing more.

update_profile

ChatGPT
Changes the user’s Griply account settings: the time zone, the first day of the week, the time, date and number formats, the theme (one for desktop and mobile alike), which push notifications are off, and the reminder new tasks get by default; a field left out stays as it is. Use it only when the user asks to change one of these settings. For a trip or one answer in another zone, pass timezone on that call instead: accountTimeZone (an IANA zone, or automatic to let their devices set it the next time they open Griply) changes the account’s zone everywhere, plans every reminder again and syncs every connected calendar again, and can change at most 5 times a day. Notifications can only be turned off here; turning one on needs the device’s permission, so point the user to the notification settings of the app. The app’s language and the app lock are not changed here either. get_profile reads every setting. The answer gives changed (the fields that changed; [] when all already matched), previous (their old values: to undo, pass previous.accountTimeZone, or automatic when previous.automaticTimeZone is true; a theme that differed between desktop and mobile, a notification turned off and a reminder that was no preset are put back in the app), settings (every setting after the call), and timeZone and today: the zone this call’s dates are in, which the client’s location can set apart from settings.accountTimeZone. Repeating a call changes nothing more.

update_tasks

ChatGPT
Changes up to 25 existing tasks and habits in one call; a field left out stays as it is. A todo can move to another day or be unplanned, get a start time and duration, reminders, a deadline, a priority, a new name or description, and goals, projects and life areas linked or unlinked (it may serve several). Tags are added or taken off on any task or habit. A todo or repeating task moves into a task section with moveToSectionId (last in it and out of that item’s other sections, linked to that item when not yet; its other links stay: removeGoalIds or removeLifeAreaIds takes one off) or out of one with removeFromSectionId. A repeating task can change its name, description, priority and its one link; a habit its name, description and priority. One occurrence of a repeating task or habit moves to another day, gets another time, or is removed (date null), named by occurrenceDate; that never changes its rule, which update_habits does, as it does a habit’s links. An occurrence on a day already logged stays on that day; a completed one can still get another time. A week is replanned in one call, todos and occurrences together, one occurrence per repeating task or habit per call. To block time for one task, give it date, start and durationMinutes; time for a goal or project, life area, tag or smart list without choosing the task yet is a focus block, which update_focus_blocks changes; a new appointment with other people is a calendar event, which Griply does not create; one already stored here is a task. A task synced to a calendar moves there too. Today’s tasks are the ones planned today, not the overdue ones: move an overdue task only when the user asks for it. Answers per task which fields changed (none when it already read that way) and how it reads now, or what to fix.

apply_plan

Claude

complete_tasks

Claude

create_focus_blocks

Claude

create_goal

Claude

create_life_area

Claude

create_project

Claude

create_sections

Claude

create_tags

Claude

create_tasks

Claude

delete_items

Claude

get_completed

Claude

get_goal

Claude

get_habit_stats

Claude

get_hierarchy

Claude

get_planning

Claude

get_profile

Claude

get_tasks

Claude

log_habit

Claude

log_progress

Claude

preview_plan

Claude

restore_items

Claude

search_tasks

Claude

uncomplete_tasks

Claude

update_focus_blocks

Claude

update_habits

Claude

update_item

Claude

update_tasks

Claude

Similar Apps

Listed on MCP App Store

Listed on MCP App Store

Add this badge to your site or README. It links to this page.

HTML

<a href="https://mcp-app-store.keenethics-labs.com/app/griply"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>

Markdown

[![Listed on MCP App Store](https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg)](https://mcp-app-store.keenethics-labs.com/app/griply)