Skip to main content
Glama
imap-mcp

imap-mcp

Related Servers

Alternatives to imap-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to maintain a persistent, queryable memory stored as user-owned Markdown files, with dual-channel retrieval (FTS5 and optional semantic search) and an audited write pipeline.
      11
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects AI clients such as Google Gemini Web, Claude Desktop, and Cursor to a personal vault and cloud storage, letting them list, read, write, and append Markdown notes and search or read documents anywhere on a personal drive through secure OAuth 2.0 authentication over Streamable HTTP or SSE.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides hybrid search (BM25 + vector) and staleness reporting for local markdown notes, exposing search and indexing tools to AI assistants via MCP.
      7 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables LLMs to maintain persistent memory by reading and writing Markdown notes and sibling image assets in a user-selected local or sync folder, with no cloud service, account, or server to run.
      11
      1,197 npm
      MIT

    TDQS

    A3.9/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool maps to a distinct stage of the IMAP workflow: provider discovery, health checks, mailbox listing, searching, reading, syncing, exporting, and filter explanation. The closest pair, imap_sync_to_vault and imap_export_for_runtime, is clearly differentiated by destination and side effects.

    Naming Consistency4/5

    All tools share the imap_ prefix and mostly follow a verb_noun pattern, making them predictable and easy to navigate. The minor exception is imap_health, which uses a noun instead of a verb, and a few names use prepositional suffixes like to_vault or for_runtime.

    Tool Count5/5

    Eight tools is well-scoped for an IMAP connector: setup, diagnostics, discovery, search, read, sync, export, and audit each have one dedicated tool. No tool feels redundant, and no essential phase of the described workload is missing.

    Completeness4/5

    The tool set covers the full inspection and ingestion lifecycle, including provider setup, connection health, mailbox discovery, search, full message retrieval, vault sync, runtime export, and filter auditing. It intentionally avoids mailbox mutation and does not handle attachments, which are minor gaps for a general IMAP tool but acceptable for this ingestion-focused design.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues