indexfo

The MCP server for Index — the deterministic data layer that scans Gmail for your active two-way conversations and hands them to your AI client (Claude) to classify and triage.

Index is AI-powered: the classification, deadline extraction, and action items are all done by the LLM in your client. This server is the part that isn't — it does the reusable plumbing in code (two-way detection, automated-sender/newsletter filtering, thread assembly) and returns structured, unclassified conversations. Because the server itself makes no model calls and holds no API key, it's free and stateless to run; the intelligence is whatever Claude you already have.

Install & connect

Requires Node 18+ and your own Google OAuth credentials (read-only Gmail). See Connect Gmail → Path B.

export INDEX_GOOGLE_CLIENT_ID=...
export INDEX_GOOGLE_CLIENT_SECRET=...
npx -y indexfo auth      # one-time browser consent, caches ~/.index/token.json

Register it with any MCP client:

{
  "mcpServers": {
    "index": {
      "command": "npx",
      "args": ["-y", "indexfo"],
      "env": {
        "INDEX_GOOGLE_CLIENT_ID": "your-google-oauth-client-id",
        "INDEX_GOOGLE_CLIENT_SECRET": "your-google-oauth-client-secret"
      }
    }
  }
}

Tools

| Tool | Description | |------|-------------| | index_scan_active_conversations | Scan Gmail for active two-way threads in the last days (default 30, maxThreads default 50). Returns structured, unclassified conversations. | | index_get_profile | The authenticated user's email + domain. |

Privacy

Read-only Gmail scope. Tokens are cached locally (~/.index/token.json, chmod 600) and mail is processed on your machine — nothing is sent to any Index server.

MIT © Index · full docs & skill