Skip to main content
Glama
LeeFlannery

imap-mcp

by LeeFlannery
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
IMAP_MCP_ACCOUNTSNoPath to the accounts.toml configuration file. Defaults to accounts.toml next to pyproject.toml.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_accountsA

List configured mail accounts and whether each is reachable right now.

Performs a live IMAP login per enabled account. Returns status so the caller knows which mailboxes are queryable.

list_emailsA

List recent emails, newest first.

account: account key (see list_accounts). Omit to merge ALL enabled accounts.
since: ISO date (YYYY-MM-DD) lower bound, optional.
unread_only: only unseen messages.
limit: max rows (per account when merging).
search_emailsA

Search emails across from/subject/body text, newest first.

query: free text; matched against sender, subject, and body (IMAP OR).
account: omit to search ALL enabled accounts.
since: ISO date (YYYY-MM-DD) lower bound, optional.
limit: max rows (per account when merging).
get_emailA

Fetch one full email (plain-text body preferred) by account + message id.

id is the value returned in list_emails/search_emails rows (IMAP UID).
Reading does not mark the message as read.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.4/5.0

Scored across 4 tools

Disambiguation5/5

Each tool targets a distinct operation: listing accounts, listing emails, searching emails, and fetching a single email. There is no overlapping purpose between them, and the parameters clearly differentiate list_emails from search_emails.

Naming Consistency5/5

All tools follow a consistent verb_noun snake_case pattern: list_accounts, list_emails, search_emails, get_email. The naming is predictable and uniform.

Tool Count5/5

With 4 tools, the server is well-scoped for basic email retrieval. Each tool earns its place, covering the essential actions without unnecessary bloat or redundancy.

Completeness4/5

The set covers the core email-reading workflow: identify accounts, list/search emails, and fetch full content. Minor gaps like flag management or folder operations exist, but the primary use case is fully supported.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources