Skip to main content
Glama
JMAP MCP Server

JMAP MCP Server

by jahfer

JMAP-MCP

Read emails via MCP!

Introduction

JMAP-MCP is a connector designed to interact with a JMAP (JSON Mail Access Protocol) server, allowing you to read emails via the Model Context Protocol (MCP). This project specifically demonstrates integration with a Fastmail JMAP server.

Related MCP server: email-mcp

MCP Configuration

To use JMAP-MCP, you need to configure it as an mcpServer in your MCP configuration file. Here is an example configuration:

{
  "mcpServers": {
    "emails": {
      "command": "npx",
      "args": ["-y", "@jahfer/jmap-mcp-server"],
      "env": {
        "JMAP_SESSION_URL": "https://api.fastmail.com/jmap/session", // for example
        "JMAP_TOKEN": "<your-jmap-token>"
      }
    }
  }
}

API Token Configuration

You need to set your JMAP API token to authenticate with your email server (e.g., Fastmail). Obtain your API token from your server's settings.

Set the JMAP_SESSION_URL and JMAP_TOKEN environment variables when running the application.

Tools

Once configured in MCP, you can use commands or features within MCP that interact with the server definition to read your emails via the JMAP protocol.

Local Development

  1. Prerequisites: Ensure you have Node.js installed.

  2. Clone the repository: Clone this repository to your local machine.

  3. Install dependencies: Navigate to the project directory and run:

    npm install

Available Tools

3 tools
get_email_contentD

Inputs: inputSchema (required).

get_mailboxesD

Inputs: inputSchema (required).

search_emailsD

Inputs: inputSchema (required).

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    D1.8/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools have clearly distinct purposes: get_email_content retrieves specific email content, get_mailboxes lists mailboxes, and search_emails searches across emails. There is no overlap in functionality, making it easy for an agent to select the right tool for each task.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case (get_email_content, get_mailboxes, search_emails). The naming is predictable and readable throughout the set.

    Tool Count3/5

    With only 3 tools, the set feels thin for an email server, as it lacks operations like creating, updating, or deleting emails or mailboxes. While the tools cover basic retrieval and search, the scope is limited and may not support full email workflows.

    Completeness2/5

    The tool surface is significantly incomplete for an email domain, missing essential CRUD operations such as send_email, delete_email, create_mailbox, or update_email. This will likely cause agent failures when attempting comprehensive email management tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      Local MCP server for Hey.com email - read, search, send, reply, and manage the screener via stored session cookies. Runs over stdio, stores no credentials.
      37
      13
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Local MCP server for multi-account IMAP/SMTP email (iCloud + Gmail via app-specific passwords). Never marks mail read. Cross-folder search, idempotent sends, TLS verified.
      8
      41 PyPI
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A minimal MCP server for reading, searching, managing, and sending email over IMAP and SMTP.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A self-hostable Gmail MCP server that enables Gmail search/read, sending, replies, drafts, labels, and attachment downloads via MCP tools with OAuth authorization. Supports stdio and streamable HTTP transports.
      MIT