MIST - Model Intelligence System for Tasks

Created By
CLoaKY233a year ago
MCP server empowering AI assistants with real-world capabilities: Gmail, Calendar, Tasks, Git integration, and note management. Bridges AI assistants to external services through standardized protocol with secure authentication.
Overview

What is MIST?

MIST is a Model Context Protocol (MCP) server that empowers AI assistants with real-world capabilities, enabling them to manage notes, interact with Gmail, Calendar, Tasks, and Git integration.

How to use MIST?

To use MIST, clone the repository, install dependencies, configure your environment, and run the MCP server. Connect it to your AI assistant for seamless integration.

Key features of MIST?

  • Note management with rich text formatting and search capabilities.
  • Gmail integration for email management and organization.
  • Calendar event management including creation and updates.
  • Task organization with lists and completion tracking.
  • Git operations for version control and repository management.

Use cases of MIST?

  1. Automating email responses and management.
  2. Organizing personal notes and tasks efficiently.
  3. Managing calendar events and reminders.
  4. Integrating Git operations into daily workflows.

FAQ from MIST?

  • Can MIST integrate with other services?

Yes! MIST is designed to connect with various external services through the Model Context Protocol.

  • Is MIST free to use?

Yes! MIST is open-source and free to use under the MIT License.

  • What are the prerequisites for using MIST?

You need Python 3.13 or newer, a Google account for API integrations, and Git for version control features.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
CLoaKY233
Star
8
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 hours ago