Back to Focusly

Use Focusly from your AI app

Focusly works as a connector (a remote MCP server) for Claude, ChatGPT, Gemini, Claude Code, Cursor and other AI apps. Once connected, you can ask the AI you already use to plan your day, add and move tasks, log habits, update goals and boards, capture ideas, sketch on whiteboards and review how your week went, all in your own Focusly account.

What you need

Connect

Server address:

https://focusly.rocketbrains.in/api/mcp

Claude (web, desktop, mobile)

Add Focusly from the connectors directory, or in Settings → Connectors choose Add custom connector, name it Focusly and paste the address. Press Connect, sign in to Focusly and allow access. In a chat, switch Focusly on in the tools menu.

ChatGPT

Settings → Apps & Connectors (turn on Developer mode under Advanced if there's no option to add one). Create a connector, paste the address, pick OAuth, then sign in to Focusly.

Claude Code

claude mcp add --transport http focusly https://focusly.rocketbrains.in/api/mcp

Then run /mcp and choose focusly to sign in.

Gemini, Gemini CLI, Cursor and others

Add a remote MCP server (Streamable HTTP) with the address above; the app opens Focusly's sign-in page the first time it connects. Signed in to Focusly, Settings → Connected apps shows the exact steps for each app.

Sign-in and permissions

Safety

Your data

The connector reads and writes only your Focusly data, through Focusly's own servers, and doesn't read your conversations. Changes are logged so they can be undone. What you send to your AI app, and what it receives from Focusly, is also handled under that app's privacy policy. See the privacy policy and terms.

Example requests

Tools

60tools. “Reads” never changes anything; “Changes” can be undone; “Asks first” only runs after you confirm.

Tasks

  • Find tasksfind_tasksReads

    Find tasks (get ids before changing one). list: planned (default; from/to, ≤31 days, default today), backlog, archived, overdue (missed deadlines + carried over), goal (a goal's board). query: title text or card number (FIT-12); alone, it searches all dates.

  • Create taskcreate_taskChanges

    Create a task on the dashboard on `date` (default today), or backlog=true (no date), or on a goal's board (goal, optional column/date), or as a subtask (parent_task_id). Keep date/time words out of the title.

  • Update taskupdate_taskChanges

    Change a task (dashboard or goal). Pass only what the user asked to change; null clears. Covers reschedule, quadrant, times, tags, board column (the completion column completes it), nesting, assignee, and moving between dashboard and a goal.

  • Complete taskcomplete_taskChanges

    Mark a task done (or not done with completed=false). For repeating tasks, `date` picks the occurrence (default today). Get the id from find_tasks first.

  • Get taskget_taskReads

    Everything about one task: description (screenshots marked [image N], listed under images), subtasks, tags, goal and column, time logged, recurrence, and its attached files (open one with get_attachment).

  • Get attachmentget_attachmentReads

    Open a file attached to a task (ids from get_task's files). Text files (txt, md, csv) come back as text; images and PDFs are attached for you to look at; anything else gets a download link valid for 10 minutes.

  • Move tasksmove_tasksChanges

    Move several tasks at once to another day or to the backlog, in one step: pass task_ids, or from_date to take every unfinished task planned that day (or 'overdue' for everything carried over from earlier days). Repeating and finished tasks are skipped and reported. Use this instead of many update_task calls.

  • Delete taskdelete_taskAsks first

    Delete a task and its subtasks. The user confirms first; it can be undone afterwards (attached files can't be restored).

  • Log timelog_timeChanges

    Log time spent on a task (like a finished focus session), e.g. "I spent 25 minutes on the invoice".

Daily plan and focus

  • Get day planget_day_planReads

    Read the user's plan for a day: their Top 3 (the tasks that make the day a win), available focus time vs planned work, open tasks ranked by value for the time (value_score: importance, impact, goal work and deadline, divided by effort), tasks that would fit better on another day when the day is overfull, and how many unfinished tasks were carried over. Use it when the user asks what to focus on, to plan their day, or what to drop.

  • Update day planupdate_day_planChanges

    Change a day's plan (default today): top3 = up to 3 task ids on that day, most important first, replacing the current ones (empty list clears); capacity_minutes = the focus time available that day (null = back to the default); planned / closed mark the day as planned or reviewed. Tasks must already be on that day: if one isn't, ask before moving it.

  • Close dayclose_dayChanges

    Close a day (default today): moves its unfinished one-off tasks to `roll_to` (default the next day, or 'backlog'), and marks the day reviewed. Repeating tasks stay. Returns what was finished and what moved.

Habits

  • List habitslist_habitsReads

    List the user's habits with their schedule, today's progress, current streak, and how often they hit them over the last 7 and 30 days (rate = completed / scheduled days). Pass history_days to also get each day's log (most recent first). Use it for questions like "how are my habits going?" or "which habit do I keep missing?".

  • Log habitlog_habitChanges

    Log progress on one of the user's habits. Quantitative habits (with a unit/target): mode 'add' adds `amount` to the day's value, 'set' replaces it; convert the user's amount into the habit's unit first (e.g. 1 L → 1000 when the unit is ml). Yes/no habits: mode 'complete' or 'uncomplete'. This only logs a day; to pause or edit a habit use update_habit.

  • Create habitcreate_habitChanges

    Create a habit. Yes/no habits ("meditate") have no target; quantitative ones ("drink 2000 ml of water") have a target_value and unit. Schedule: daily (default), specific_days (pick weekdays) or every_n_days.

  • Update habitupdate_habitChanges

    Change a habit: rename, target/unit, schedule, emoji, description, grace days, or pause it (active=false) / resume it (active=true). Pausing keeps its history; it just stops showing up and counting.

  • Delete habitdelete_habitAsks first

    Delete a habit and its whole history. The user confirms first; it can be undone. Suggest pausing (update_habit active=false) if they might come back to it.

Goals and boards

  • List goalslist_goalsReads

    List the user's goals (their own and ones shared with them) with progress: tasks done/total, overdue tasks, milestones and the next one, last activity. A goal's tasks have card numbers starting with its task_key (FIT-12); list them with find_tasks list='goal'.

  • Get goalget_goalReads

    One goal in detail: description, target date, board columns with task counts, milestones, and members.

  • Create goalcreate_goalChanges

    Create a goal with a board (To Do / In Progress / Done, or a simple list). Optionally a target date, description, category and tags.

  • Update goalupdate_goalChanges

    Change a goal: title, description, target date, category, tags, or status (active, completed = achieved, archived = put away). Only the owner can change a shared goal's details.

  • Delete goaldelete_goalAsks first

    Delete a goal with its whole board (tasks, milestones). The user confirms first. This can't be undone, so suggest archiving (update_goal status='archived') instead.

  • Manage milestonemanage_milestoneChanges

    Milestones on a goal: action 'add' (title, optional due_date), 'edit' (milestone_id + title/due_date), 'complete' / 'reopen', or 'delete'. Get milestone ids from get_goal.

  • Manage columnmanage_columnChanges

    Board columns: action 'add' a column (title) or 'rename' one (column = current name). Deleting or reordering columns is done on the board.

Ideas

  • List ideaslist_ideasReads

    List the user's saved ideas (the someday/maybe list, separate from tasks). Optional text filter.

  • Save ideasave_ideaChanges

    Save an idea to the Ideas list (not a task: no date, no quadrant). Use when the user says idea, someday, maybe, or 'remember this thought'.

  • Update ideaupdate_ideaChanges

    Change an idea: title, description, tags, or archive / unarchive it.

  • Delete ideadelete_ideaAsks first

    Delete an idea. The user confirms first; it can be undone. Archiving (update_idea archived=true) keeps it out of the way instead.

  • Convert ideaconvert_ideaChanges

    Turn an idea into a task (on `date`, in `quadrant`) or a goal. The idea is archived afterwards unless keep_idea=true. The new task/goal keeps the idea's description and tags.

Tags

  • List tagslist_tagsReads

    List the user's tags with how many tasks, ideas and goals use each.

  • Manage tagmanage_tagChanges

    Tags: action 'create' (name, optional color/emoji), 'rename' (tag + new_name), 'recolor' (tag + color: violet, red, orange, amber, yellow, lime, green, emerald, teal, cyan, blue, indigo, purple, pink, rose, slate or #hex), 'emoji' (tag + emoji, null clears). Merging and deleting are separate (merge_tags, delete_tag).

  • Delete tagdelete_tagAsks first

    Delete a tag; it comes off every task, idea and goal (they stay). The user confirms first; it can be undone.

  • Merge tagsmerge_tagsAsks first

    Merge one tag into another: everything tagged `from` gets `into`, and `from` is deleted. The user confirms first; this can't be undone.

Rewards

  • List rewardslist_rewardsReads

    The user's rewards: each reward with what earns it, plus earned rewards (unused ones can be redeemed).

  • Create rewardcreate_rewardChanges

    Create a reward ("Movie night"), optionally with what earns it: achieving a goal, completing a habit, finishing a task, or a Top 3 day (focus_day). Rewards are earned each time the trigger happens; there's no 'N times' counter, so say so if asked.

  • Update rewardupdate_rewardChanges

    Change a reward's title, icon or description, add what earns it (add_trigger) or remove a trigger (remove_trigger_id from list_rewards).

  • Delete rewarddelete_rewardAsks first

    Delete a reward, its triggers and its earned history. The user confirms first; this can't be undone.

  • Claim rewardclaim_rewardChanges

    Rewards: action 'grant' gives the user one of their rewards now (earned manually); 'redeem' uses an earned one (earned_id from list_rewards).

Pillars

  • Get pillarsget_pillarsReads

    The user's pillars (life areas they score 1–5 each period): mode (focus / maintain / rest), what each score means, this period's score and last period's, this week's quick pulse, and the habits/goals linked to each.

  • Rate pillarrate_pillarChanges

    Score a pillar 1–5 for the current period (kind 'rating', the monthly/quarterly check-in) or this week (kind 'pulse', focus pillars). Scores are 1–5: convert other scales (7/10 ≈ 4) and say so. Optional note and next_fix (the one improvement for the next 30 days).

  • Update pillarupdate_pillarChanges

    Change a pillar's mode (focus = actively improving, maintain = keep steady, rest = on hold), or link / unlink a habit or goal to it (link: 'habit:<name or id>' or 'goal:<name or id>'). A habit or goal belongs to at most one pillar.

Statistics

  • Get statsget_statsReads

    A summary of how a period went, for reviews and feedback ("how was my week?", "am I on track?"): tasks done (by quadrant and goal), first-try rate and slips, Top 3 days hit, open planned tasks, most-slipped tasks, focus time, habit consistency and streaks, goal progress. Includes tasks done in the previous period of the same length, for comparison.

Shared goals

  • List memberslist_membersReads

    Who a goal is shared with (name, email, role: owner / editor / viewer) and, for the owner, pending invites. Member ids are for assigning tasks.

  • Invite memberinvite_memberAsks first

    Share a goal: creates an invite link (bound to `email` if given, otherwise anyone with the link can join) as editor or viewer. The user confirms first, then shares the link themselves; nothing is emailed.

  • Revoke inviterevoke_inviteChanges

    Cancel a pending invite (id from list_members).

  • Set member roleset_member_roleChanges

    Change a member's role in a shared goal (editor or viewer). Owner only.

  • Remove memberremove_memberAsks first

    Remove someone from a shared goal (owner only), or leave a goal someone else shared with you (member = 'me'). The user confirms first.

Settings

  • Get settingsget_settingsReads

    The user's app settings that can be changed here: Pomodoro lengths, daily focus capacity, accent color, completion sound, Today view, Undo, pillar cadence, time zone.

  • Update settingsupdate_settingsChanges

    Change app settings. Accent colors: purple, blue, cyan, green, orange, rose, crimson, amethyst. Sounds: none, soft, ding ("Glock"), kalimba, marimba, triple ("Bubbles"), chime, crystal ("Wind chimes"), harp, bell, bowl ("Singing bowl"), fanfare ("Success"), pop. Undo window: 3, 5, 8 or 10 seconds. Dark/light mode is set_theme, not this.

Whiteboards

  • List whiteboardslist_whiteboardsReads

    List the user's whiteboards (freeform boards for brain dumps, mind maps and sketches): id, title, how many notes, first lines.

  • Get whiteboardget_whiteboardReads

    Read a whiteboard: its notes, shapes and frames (with ids, to edit them or attach new items), the mind-map outline, and its connections.

  • Create whiteboardcreate_whiteboardChanges

    Create a whiteboard, optionally filled in: a mind map, a brainstorm of notes, a plan split into sections. Items are laid out for you: items with a parent form left-to-right mind maps (a tree per root), the rest go in a grid, placed beside what's already on the board. Use parent for hierarchy (topic → subtopics → details) and connections for other links. Keep each note short (a few words to a sentence).

  • Add to whiteboardadd_to_whiteboardChanges

    Add notes, mind-map branches and connections to an existing whiteboard. To grow an existing mind map, set an item's parent to an element id from get_whiteboard. Items are laid out for you: items with a parent form left-to-right mind maps (a tree per root), the rest go in a grid, placed beside what's already on the board. Use parent for hierarchy (topic → subtopics → details) and connections for other links. Keep each note short (a few words to a sentence).

  • Update whiteboardupdate_whiteboardChanges

    Rename a whiteboard, change its background, or edit elements on it (text, colour, size) by id from get_whiteboard.

  • Remove from whiteboardremove_from_whiteboardAsks first

    Remove elements (and their connections) from a whiteboard, by id from get_whiteboard. Needs the user's OK.

  • Delete whiteboarddelete_whiteboardAsks first

    Delete a whole whiteboard. Needs the user's OK.

Undo and confirmations

  • List recent actionslist_recent_actionsReads

    What the AI (this app or connected apps) changed recently, newest first, with ids for undo_action and whether each can still be undone.

  • Undo actionundo_actionChanges

    Undo an earlier AI change: pass action_id (from list_recent_actions or an earlier result), or leave it out to undo the latest undoable one.

  • Confirm actionconfirm_actionChanges

    Runs a destructive action that an earlier call proposed (it returned needs_confirmation and a proposal_id), once the user has seen the proposal and agreed to it.

  • Cancel actioncancel_actionChanges

    Drop a proposed destructive action the user declined.

Support

Questions or problems with the connector? Email support@rocketbrains.in.