Claude MCP time blocking on Mac: plan locally

What does Claude MCP time blocking mean on Mac?

Claude MCP time blocking means using Anthropic's Model Context Protocol to give Claude a controlled set of tools for planning your day. Instead of asking Claude for a plain text schedule and then copying it into your calendar, Claude can call actions exposed by a local app. In Chunk, those actions include reading and writing the time-blocking objects that make up your day.

That changes the job Claude can do. A normal chat might say, “Work on the proposal from 10:00 to 11:30.” With MCP connected to Chunk, Claude can create that block in the app, move it later, split the afternoon, create a morning routine template, or turn a loose task list into scheduled blocks. You still review the plan in Chunk's menu-bar panel, drag blocks by hand when needed, and keep the final say.

This is different from a cloud scheduling assistant. Chunk stores schedule data locally in SQLite on your Mac. Its Claude integration registers a local MCP server with Claude Desktop, and that server reads and writes through local IPC. Nothing extra leaves your machine for Chunk's side of the workflow, beyond the normal Claude prompt processing and any calendar, OAuth, licence or analytics traffic you choose to use.

Why use Claude with a time-blocking app instead of chat alone?

Chat alone is useful for thinking, but it breaks down when the answer needs to become your actual day. You get a neat plan in text, then you still have to copy every item, choose times, resolve overlaps, and keep the plan visible while you work. That copy step is where planning often dies.

Time blocking works because it turns intention into visible time. A block has a start, an end, a name, and a place in the day. Chunk keeps that structure in a Mac panel you can open with a shortcut, including over fullscreen apps. The tray icon can count down the current block, so the plan is not hidden in a chat transcript or a full calendar window.

Claude is useful when your plan is under-specified. You might know the tasks, constraints and energy pattern, but not the order. A good prompt can ask Claude to make trade-offs: protect a deep-work block, leave admin for late afternoon, keep lunch free, or build a lighter Friday. MCP then lets those decisions become blocks, tasks or templates in the planning surface you actually use.

For the basics of the method before adding Claude, see what is time blocking. For a Mac-first overview, best time blocking app for Mac explains why speed and visibility matter so much once your day starts moving.

What can Claude control in Chunk?

Chunk's local MCP server exposes tools for the planning objects inside the app. Claude can get, create, update and delete events, to-do lists, tasks, templates and template items. It can also complete tasks. External calendar events are available to Claude as read-only context, so Claude can plan around meetings without being given direct edit control over those external events through MCP.

That tool set fits the daily planning job. You can ask Claude to “plan my day”, “move my afternoon meetings later”, or “create a morning routine template”. In practice, the most useful prompts are specific about constraints. For example: “Use my existing meetings as fixed commitments, schedule these five tasks around them, keep one 90-minute focus block before lunch, and leave 30 minutes unplanned after 16:00.”

Inside Chunk, the result is still normal time-blocking data. Blocks appear on the vertical 24-hour timeline. You can drag empty space to create more, drag a block to move it, resize its edges, or click it to edit details. Blocks can use one of Chunk's five colours: Indigo, Sky, Emerald, Amber and Rose.

Claude can also help with reusable structure. If your mornings repeat, ask it to create a template with the blocks you want. Chunk's templates are reusable day structures, and routines can auto-apply templates on selected weekdays. That gives Claude a role in designing the system, not just filling one day.

How do you connect Claude Desktop to Chunk?

Chunk's Claude setup is built into the app. In Settings, the AI Integrations section includes a one-click connect flow that registers Chunk's local MCP server with Claude Desktop. After that, Claude can see the tools Chunk exposes and call them when you ask it to plan, adjust or create scheduling objects.

The local shape matters. There is no separate Chunk cloud scheduler between Claude and your day. Chunk's MCP package runs on your Mac, reads and writes the local SQLite-backed app data through local IPC, and keeps the planning surface in the same app you open from the menu bar. If you want an AI-assisted workflow without moving your whole schedule into a new web service, that is the point.

Once connected, start with a small prompt rather than giving Claude your whole life. Ask it to create three blocks for the afternoon, or to turn a short task list into a plan around existing meetings. Then open Chunk with its global shortcut and inspect the result. The best workflow is conversational, but not passive: ask, review, drag, resize, and ask again.

If you are new to the app itself, Chunk 2.0 is here gives the broader product context, including the menu-bar panel, task mode and calendar sync.

How should you prompt Claude to plan a real day?

The best prompts give Claude the same information you would use if you were planning by hand: fixed commitments, flexible tasks, desired block lengths, energy constraints and non-negotiable breaks. A vague prompt like “plan my day” can work, but a constrained prompt produces a schedule you are more likely to keep.

Try a prompt like this: “Plan today in Chunk. Treat existing calendar events as fixed. Schedule these tasks: draft proposal, review invoices, reply to hiring emails, prepare slides. Put the proposal in a 90-minute focus block before lunch. Keep admin after 15:00. Leave 15 minutes between meetings and do not schedule past 17:30.” That tells Claude what to optimise for and what to avoid.

You can also ask Claude to adjust rather than start over. If a meeting overruns, try: “Move the remaining work later, keep the slide prep today, push invoices to tomorrow if needed, and preserve a 30-minute shutdown block.” Because Chunk exposes update and delete tools for its own objects, Claude can revise the plan instead of handing you a second text version.

For focus-heavy days, pair Claude with a stricter blocking rule. Decide which block is protected before you prompt. If you need that pattern, deep work time blocking covers how to protect the work that usually gets squeezed out.

How does this work with Google, Outlook and Apple Calendar?

Chunk can sync with Google Calendar, Outlook Calendar and Apple Calendar. Those integrations are bidirectional in the app: you can create, edit, move, resize and delete connected calendar events from Chunk, and changes push back to the source calendar when editing is allowed. You can connect multiple Google and Outlook accounts, while Apple Calendar uses the system connection on your Mac.

For Claude MCP, the boundary is more cautious. Claude gets read-only access to external calendar events through Chunk's tools. That means it can plan around meetings from your connected calendars, but the MCP integration is not a back door for Claude to directly rewrite those external events. If you want to move a synced meeting, you can still do that yourself in Chunk's calendar surface when the account allows editing.

This gives you a useful split: Claude can arrange your personal time blocks, tasks and templates around the real commitments already on the calendar, while you keep control over external events. If your schedule blends work meetings, personal appointments and self-directed tasks, that separation is usually what you want.

For a calendar-sync-specific walkthrough, read two-way calendar sync for Mac time blocking. For a Google-focused workflow, see Google Calendar time blocking.

What should stay manual when Claude helps you time-block?

Claude is best at drafting and reshaping the plan. You should keep judgement, commitment and sensitive calendar edits manual. A plan can look tidy and still be unrealistic if it ignores your actual energy, the emotional weight of a task, or the fact that one meeting always leaves you drained. Use Claude as a planning assistant, not as proof that the day is possible.

Keep a quick review ritual after each prompt. Open Chunk from the menu bar, scan the timeline, and ask three questions: is there enough slack, is the hardest work placed at the right time, and do the transitions make sense? Then drag or resize blocks yourself before work begins. Because Chunk's panel is quick to open, that review does not have to become a separate planning session.

Use manual controls for external events too. Chunk can edit synced calendar events from the app when you allow it, but Claude's MCP access to external events is read-only. That is a healthy guardrail. Meetings, appointments and shared commitments deserve a deliberate edit, not an accidental prompt side effect.

Finally, avoid using Claude to overfill the day. Time blocking is not about proving that every minute can be assigned. Leave gaps for messages, overruns and recovery. The best AI-assisted plan is often a little emptier than the one Claude first suggests.

How is local-first MCP different from an AI scheduler?

An AI scheduler usually asks you to trust a service to decide when work should happen. Some tools optimise your calendar automatically, move tasks into open slots, and keep adjusting as new events appear. That can be useful if you want a cloud service to manage the calendar logic for you. It is not what Chunk is.

Chunk is a Mac time-blocking app first. Its core surface is the menu-bar panel, day timeline, task sidebar, templates, routines, synced calendars and live countdown. MCP adds a local control layer for Claude, so you can ask for help creating or changing the plan inside that app. The centre of the workflow remains your Mac, your timeline and your review.

Local-first also means clearer data boundaries. Chunk's schedule data is stored locally. The MCP server runs on-device. Claude can only use the tools Chunk exposes. Your prompts still go to Claude, because that is how Claude Desktop works, but Chunk is not uploading your scheduling database to a separate auto-scheduling platform.

If your main objection to AI scheduling is loss of control, this distinction matters. You get natural-language assistance for planning, while the result stays editable as normal blocks and tasks. You can accept the useful parts, delete the rest, and keep working from the same menu-bar view.

When is Claude MCP time blocking worth using?

Use Claude MCP time blocking when your day has enough moving parts that manual planning feels costly, but not so much that you want to surrender the calendar. It is especially useful for mixed days: fixed meetings, flexible tasks, a few deep-work commitments, admin that can move, and a preference for seeing the plan before starting.

It is less useful when the day is already obvious. If you have one meeting and one task, dragging a block in Chunk is faster than prompting Claude. It is also the wrong fit if you want a team scheduling tool, mobile calendar system or web app. Chunk is macOS only, single-user, and designed around a menu-bar panel on your Mac.

The sweet spot is repeatable planning. Ask Claude to draft a Monday template, reshape a disrupted afternoon, or turn a backlog into blocks around your existing calendar. Then use Chunk's normal controls to refine it. Over time, the templates and routines reduce how much prompting you need, while Claude remains useful when the day changes.

If that sounds like the balance you want, try Chunk on your Mac. Connect Claude Desktop from Settings, ask it to plan a small part of tomorrow, then open the menu-bar panel and make the plan yours before the day starts.