Skip to main content
Glama
jahfer

JMAP MCP Server

by jahfer
README.md
# JMAP-MCP

Read emails via MCP!

<a href="https://glama.ai/mcp/servers/@jahfer/jmap-mcp-server">
  <img width="380" height="200" src="https://glama.ai/mcp/servers/@jahfer/jmap-mcp-server/badge" alt="JMAP MCP server" />
</a>

## 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.

## MCP Configuration

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

```jsonc
{
  "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:

    ```bash
    npm install
    ```

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 issues