Flick MCP
Connect Flick to your AI apps
Flick for Mac can run a small MCP server on your Mac. MCP (Model Context Protocol) is the open standard that AI apps use to talk to the tools you already use. Once it is connected, apps like Claude, Cursor, Codex, Copilot, and Gemini can read your Flick projects, tasks, and calendar events — and, if you allow it, create and update them for you.
Last modified: August 22, 2026
Everything runs locally. Flick's MCP server listens on 127.0.0.1 on your own machine, and your data never passes through a Flick server for this feature.
Each AI company has its own privacy and data usage policies. Make sure you trust them to access and edit the data you save on Flick when connecting the app to their LLMs.
Before you start
Flick for Mac. The MCP server is a Mac-only feature. It is not available on iPhone, iPad, or Apple Watch.
Flick must be open. The server runs inside the app, so the connection only works while Flick is running.
You'll need an AI app that supports MCP over HTTP. Almost every current AI client does. See the list below.
Step 1
Turn on the server in Flick
Open Flick → Settings → MCP.
Turn on Enable MCP. The status badge changes to Running.
Optionally turn on Allow write tools if you want your AI app to be able to create and edit tasks, projects, and events. With this off, the connection is read-only.
Press Test connection to confirm the server is reachable.
The MCP page shows the two values every AI app needs:
Value
What it looks like
Where you see it
Bearer token
a long random string
The Authorization header, as Bearer <your-token>
Use the copy buttons next to each value. The token is masked on screen, but the copy button copies the real value.
Keep your token private. It is the key to your Flick data. If you ever paste it somewhere you should not have, press Rotate token in Flick and set up your AI apps again with the new one.
Throughout this page, replace http://127.0.0.1:37653/mcp with the endpoint shown in your copy of Flick (the port can differ), and replace YOUR_TOKEN with your bearer token.
Step 2
Add Flick to your AI app
Every client needs the same three things: a name (flick), the URL, and the Authorization header. The transport is always Streamable HTTP — never STDIO, because Flick is already running the server. That means fields like Command, Arguments, Environment variables, and Working directory should be left empty.
Connect Claude Code
Run this in Terminal:
claude mcp add --transport http flick ‘http://127.0.0.1:37653/mcp’ --header ‘Authorization: Bearer YOUR_TOKEN’
Then start Claude Code and run /mcp to confirm that flick is connected.
What your AI app can do
Give your AI app the context it needs to plan, organize, and coordinate work in Flick.
Read
Tool / resource
What it does
list_projects
List Flick projects, with optional search and completion filters.
list_sections
List project sections, optionally limited to one project.
search_tasks
Search tasks by text, project, section, date range, and completion state.
get_task
Get one task by identifier.
list_calendars
List the calendars Flick can read, with visibility, writability, and source filters.
search_calendar_events
Search events by date range, calendar, source, text, and all-day inclusion.
get_calendar_event
Get one event by Flick identifier or provider event ID.
flick://workspace/summary
flick://projects/{projectID}
flick://tasks/{taskID}
flick://sections/{sectionID}
Read workspace counts, or retrieve one project, task, or section by its Flick identifier.
Write
Tool / resource
What it does
create_project
update_project
create_section
create_task
update_task
set_task_done
create_calendar_event
update_calendar_event
Create and update projects, sections, and tasks; mark tasks complete or incomplete; and create or update non-recurring events in writable calendars.