Skip to main content
Glama
inbox-relay

inbox-relay

by Sriya03

inbox-relay

An MCP server that triages a recruiter inbox: read, label, draft. It never sends mail — by permission, not by promise.

What it does

  • Searches and reads recruiter mail over Gmail

  • Labels threads into eight categories: interview, offer-process, recruiter/new, recruiter/replied, rejects, application, read-later, promos

  • Archives labeled mail out of the inbox (reversible — everything stays findable under its label)

  • Drafts replies for you to send manually

Related MCP server: Gmail Guardian

What it never does

  • Send mail. The only Gmail scope requested is gmail.modify (read, label, archive, create drafts). The gmail.send scope is never requested, so sending is impossible even if the code tried.

  • Auto-archive unsure mail. Low-confidence classifications stay in the inbox for human review.

Quickstart

npm install
npm run build

Set up a Google Cloud OAuth client (Desktop app), enable the Gmail API, and put the credentials in your environment (see .env.example). Mint the token with the auth helper — it prints a consent URL, you approve, and it saves the token at GMAIL_TOKEN_PATH (gitignored, never committed):

GOOGLE_CLIENT_ID=... GOOGLE_CLIENT_SECRET=... npm run auth

Then:

npm start
# or inspect the tools live:
npm run inspect

Tools (v1)

Tool

What it does

search_messages

Gmail search over the inbox

get_message

Fetch one message in full

list_threads

Thread-level inbox view

list_labels

All Gmail labels + ids

apply_label

Label + archive (high-confidence only)

create_draft

Draft only — you send it

classify_message (category + priority + confidence + reason) lands in Week 2 with the rubric-driven LLM classifier and the rules baseline.

Labels

See docs/annotation-guide.md for definitions, signals, precedence rules, and the thread-history rule (cold-outreach vs recruiter/new is decided by thread history, not memory).

Evals

The golden dataset is the contract: see evals/README.md. Real mail stays local and gitignored; the public repo carries no real emails, only the annotation guide and the eval methodology.

Project status

Week 1 scaffold: server skeleton, Gmail wiring for search/get/labels/drafts, taxonomy, annotation guide. Week 2: classifier + rules baseline scored. Week 3: draft tool polish, LLM classifier scored vs baseline, eval write-up.

License

MIT.

Available Tools

6 tools
apply_labelA

Label a message AND archive it out of the inbox (reversible). Only call this for high-confidence classifications; unsure messages stay in the inbox.

Inputs: label_id (required), message_id (required).

create_draftA

Create a Gmail DRAFT only. The user sends it manually. This never sends.

Inputs: to (required), body (required), subject (required).

get_messageB

Fetch one message in full: headers, body, and labels.

Inputs: id (required).

list_labelsA

List all Gmail labels with their ids (needed before apply_label).

Inputs: no named parameters.

list_threadsB

List inbox threads, optionally filtered by a Gmail search query.

Inputs: query.

search_messagesB

Search the inbox (Gmail search syntax). Returns matching message ids.

Inputs: query (required), max_results.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.8/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools target distinct resource+action pairs (search messages, fetch message, list labels, label+archive, draft). The only real overlap is search_messages vs list_threads, since both accept Gmail search queries, but the message-vs-thread distinction and the return shapes are stated clearly enough to pick correctly.

    Naming Consistency5/5

    Every tool follows a clean verb_noun snake_case pattern: search_messages, get_message, list_threads, list_labels, apply_label, create_draft. No style mixing or vague verbs.

    Tool Count5/5

    Six tools is tightly scoped for a triage/relay workflow: search, read, enumerate threads/labels, label-and-archive, and draft. Each tool earns its place with no filler.

    Completeness4/5

    Covers the core triage loop (find, read, classify, draft) well. Minor gaps: there is no tool to fetch a full thread (only list_threads) and no way to undo the archive/label despite apply_label being described as reversible, which leaves a potential dead end.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to read unread Gmail messages and create threaded draft replies, without ever sending email automatically.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables intelligent Gmail management, including email triage, newsletter classification, promotional email cleanup, summarization, filter suggestions, draft replies, and audit logging.
      -
    • A
      license
      A
      quality
      B
      maintenance
      Lets users search and read Gmail messages and threads, list labels, and create drafts via the official Gmail API, with self-hosted OAuth for privacy.
      5
      3
      MIT