Akiflow MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AKIFLOW_REFRESH_TOKEN | Yes | Your Akiflow refresh token, obtained from the Akiflow web app DevTools Network tab. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-tasksA | Get tasks with optional filters. Returns active (non-deleted, non-trashed) tasks sorted by date. |
| get-eventsB | Get calendar events (v5 API). Returns detailed event data including attendees, location, recurrence. |
| add-taskC | Create a new task in Akiflow |
| edit-taskC | Update an existing task |
| mark-doneB | Mark a task as completed |
| schedule-taskB | Schedule a task on the calendar at a specific date/time |
| unschedule-taskA | Remove a task from the calendar and optionally move to inbox |
| get-projectsA | List all projects and folders. Note: Folders have type='folder', projects/labels have type=null |
| get-tagsA | List all tags |
| get-calendarsA | Get all calendars. Returns calendar metadata including colors, settings, and sync status. |
| add-eventC | Create a new calendar event. Syncs to the source calendar (Google, etc.) |
| edit-eventB | Edit a calendar event. Changes sync back to the source calendar (Google, etc.) |
| get-time-slotsA | Get time slots (internal calendar blocks that don't sync to external calendars) |
| add-time-slotA | Create a time slot (internal calendar block). Does not sync to external calendars. |
| edit-time-slotD | Edit a time slot |
| add-task-to-timeslotB | Add a task to a time slot. Links the task to an existing time slot block on the calendar. |
| remove-task-from-timeslotA | Remove a task from its time slot. Unlinks the task from its associated time slot block. |
| get-recordingsB | List meeting recordings from Meeting Assistant. Each recording has a summary, action items, transcript, and brief. |
| get-recordingA | Get full detail for a single meeting recording including summary, action items, raw transcript, and brief. |
| get-meeting-briefsA | List pre-meeting research briefs. Briefs provide background context and attendee info before meetings. |
| get-meeting-briefB | Get full detail for a single pre-meeting research brief by ID. |
| create-task-from-action-itemA | Create an Akiflow task from a meeting recording's action item. Bridges meeting action items into your task list. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Akiflow Instructions | How to use the Akiflow MCP tools |
TDQS
Scored across 22 tools
Each tool targets a distinct action or resource. Even within the task-related tools (add, edit, schedule, timeslot operations), the descriptions clearly differentiate purposes, so an agent can reliably select the correct one.
Most tools follow verb_noun pattern (e.g., add-event, get-tasks). Minor deviations include 'create-task-from-action-item' uses 'create' instead of 'add', and 'mark-done' uses a state instead of a noun. Overall, predictable.
22 tools is somewhat high but justified by the server's broad scope covering tasks, events, time slots, recordings, and briefs. A few tools could be merged (e.g., get-recording and get-recordings), but the count is still reasonable.
The tool surface covers core CRUD for tasks, events, and time slots, plus meeting briefs and recordings. Missing operations include delete for events/tasks and create for projects/tags, but these are acceptable gaps given the domain.