Summary

Your Google account and your git history reachable from the same session.

The combination is the point — an assistant that can read the email about a bug, check the branch it landed on, and write the note, without three separate servers and three sets of config. The setup cost is real: a Google Cloud project of your own with three APIs enabled is not a two-minute task, and you are handing the server the scopes to send mail and push branches.

What it is

An MCP server bundling five areas that usually need five servers: a local note store, Gmail, Google Calendar, Google Tasks and git operations on local repositories. Google access goes through a standard OAuth flow with credentials you create yourself; notes never leave your filesystem.

What you get

Notes created, read, listed, searched, edited and deleted against a directory you choose — `add_note`, `read_note`, `list_notes`, `search_notes`, `edit_note`, `delete_note`
Gmail searched with filters, messages read in full by id, mail sent, and the account's labels listed — `search_emails`, `get_emails`, `send_email`, `list_available_labels`
Calendars listed, events created and events searched by keyword or date range — `list_calendars_tool`, `create_event_tool`, `search_events_tool`
Task lists enumerated, tasks created and tasks completed — `list_task_lists_tool`, `create_task_tool`, `complete_task_tool`
Git worked properly rather than shelled: status, staged and unstaged diffs, staging, reset, commit and log — `status_tool`, `diff_unstaged_tool`, `diff_staged_tool`, `add_tool`, `reset_tool`, `commit_tool`, `log_tool`
Branch and remote operations including merge and rebase with their abort and continue states — `branch_list_tool`, `create_branch_tool`, `checkout_tool`, `merge_tool`, `rebase_tool`, `stash_save_tool`, `pull_tool`, `push_tool`

Requirements

Python 3.13 or newer and the `uv` package manager, plus git for the repository tools. For the Google half you create your own Google Cloud project, enable the Gmail, Calendar and Tasks APIs, configure the OAuth consent screen, create a Desktop application OAuth client and download it as `credentials.json`. Three environment values point the server at everything: `MIST_NOTES_DIR` for where notes live, `MIST_GOOGLE_CREDENTIALS_PATH` and `MIST_GOOGLE_TOKEN_PATH`. The first run opens a browser to authorise; the token is saved for later. If credentials stop working, deleting the token file and re-authenticating is the documented fix.

Setup effort

One command plus a key — uvx mist, then supply credentials