MIST MCP Server

MIST MCP server exists for a simple reason — assistants are far more useful when they can act on MIST directly instead of describing what you should do. MIST is a comprehensive MCP (Model Context Protocol) server that empowers AI assistants with real-world capabilities for note management, Gmail, Calendar, Tasks, and Git integration. It bridges the gap between AI assistants and external.

What you get

By implementing the Model Context Protocol (MCP), MIST enables AI assistants to perform actions in external systems, access real-time information, and maintain context across interactions.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

What the assistant can call

Once MIST is connected, these are the calls the assistant has available:

• Function — Description
• add_note — Create a new note
• read_note — Read a note by ID or title
• list_notes — List notes with filters
• search_notes — Search notes by content
• edit_note — Update an existing note
• delete_note — Delete a note
• search_emails — Find emails by criteria
• get_emails — Get email content by IDs
• send_email — Send a new email
• list_available_labels — Get Gmail labels
• list_calendars_tool — List all calendars

Configuration and credentials

You will need 3 environment variables: MIST_GOOGLE_CREDENTIALS_PATH, MIST_GOOGLE_TOKEN_PATH, MIST_NOTES_DIR. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Python 3.13 or newer - UV package manager (recommended) or pip - Google account (for Gmail/Calendar/Tasks integration) - Git (for Git integration features)

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch MIST.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the mist mcp server does with a few real requests.

Choosing this one

Among the planning and project tracking options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MIST's toolset — Function, add_note, read_note and 11 more — is a fair guide to whether it matches your workflow. It is maintained by CLoaKY233; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.