mail-index MCP server

Read from the package source without running it. The installed server may list more.

• catch_up

  The "what did I miss" briefing since a time (30d, 2w, 12h, 1mo, or ISO): new mail from curated-important contacts, new replies in your threads, and interest-keyword hits. Compact rows + a body command handback. If the index is stale it returns now and spawns a background sync.

• digest_sources

  Newsletter/list senders ranked by engagement + interest, with unread/unsummarized issue counts — the digest routine worklist. Stale index returns now and spawns a background sync.

• domains_to_categorize

  PROPOSE domains with back-and-forth contacts (Correspondents) plus sample senders/subjects as context, so you can assign an entity category. Then save_domain_category.

• find_person

  Fuzzy contact resolution from a vague hint (name fragment, handle, or domain). Ranks Correspondents (people you have written to) first. The entry point for "who was that contact from last spring?".

• get_contact

  One contact by address: stats, curation, recent threads. A near-miss returns ranked candidates rather than nothing.

• get_message

  One message by <account:id>. level: "summary" (default — agent summary or snippet), "body" (distilled body; inline-enriches a still-meta row once, the only provider fetch), or "meta". Bodies are opt-in.

• get_thread

  A thread by <account:thread-id>: metadata, its messages (compact, snippet-first), and the thread summary if present.

• graph_communities

  Detected social circles (Louvain communities) with top members by centrality. Returns a build command handback when no graph exists yet.

• graph_neighbors

  Co-recipiency neighbours of a contact, ranked by shared threads. On a miss, returns ranked near-miss contacts so the answer is never empty.

• interest_get

  Read back the curated interest profile: curated contacts/domains + keywords.

• interest_propose

  The curation SEED: a ranked shortlist of top contacts + domains by engagement, each with a suggested action (important/muted/none). Present it, take fuzzy edits, then interest_set.

• interest_set

  Persist the curation disposition: contact/domain curation labels (important/muted/blocked, or null to clear) and freeform interest keywords (replaces the set). This profile drives which bodies get enriched.

• list_contacts

  Ranked contacts. sort: engagement (default) | volume | recency | community. filter: "correspondent" (people you have written to) | important | muted | blocked.

• list_threads

  Conversations by contact (address) OR by query (FTS). Compact thread shapes.

• save_domain_category

  PERSIST an entity category you assigned to a domain (open vocabulary: client, vendor, travel operator, finance, publisher, …). Used as a filter/grouping axis.

• save_summary

  Persist your summary of a message or thread (provenance-marked, FTS-indexed). level: "message" (default) or "thread". For bulk/non-curated mail this makes the body eligible for demotion after a grace window.

• search

  Ranked fuzzy full-text recall over the indexed mail (subject/sender/snippet/body/summaries). Snippet-first, compact; opt into a body via get_message. Recall, not lookup: a half-remembered phrase still surfaces ranked neighbours.

• setup_instructions

  SETUP MODE (no config yet). Return the exact steps + commands to finish onboarding mail-index, flagging the human steps (browser OAuth consent; manual install when Homebrew is unavailable). The server is advisory only — run `mail-index setup --account <email>` in your shell, then restart the server.

• setup_status

  SETUP MODE (no config yet). Report what is installed / authenticated / configured for mail-index — read-only observation (PATH + filesystem). Tells you whether onboarding is complete and the server can be restarted into full recall mode.

• sync_status

  Per-account freshness (index_as_of), whether a sync is running, message counts, and the meta/full/summary-only body-ladder split.

• Code scan44 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 12 days ago15/15
• Maintainer identityregistry namespace matches repository owner7/10

Safety score

91/100

higher than 88% of 916 Email servers

Tools

20

the typical Email server has 7

Tools that change things

0%

typical: 25%. Fewer write tools means less an agent can break

GitHub stars

4

more than 80% of 493 Email servers

Downloads a week

60

more than 45% of 235 Email servers with a package

mail-index: common questions

Is mail-index MCP server safe?

Yes, by our scan: it is graded A (91/100). Read the mail-index safety report

How do I install mail-index?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does mail-index need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is mail-index maintained?

The last commit was 51 days ago (2026-09-14). The latest release is v1.0.0.

What can I use instead of mail-index?

Servers from other publishers that do the same job: Outlook MCP server, PipesHub MCP server and Outlook MCP server. Compare all mail-index alternatives.

How does mail-index compare with other Email MCP servers?

safety score 91/100 (higher than 88% of 916 Email servers); tools 20 (the typical Email server has 7); tools that change things 0% (typical: 25%. Fewer write tools means less an agent can break). Full comparison.