How do I use JMAP MCP Server?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@JMAP MCP Server show me my latest 5 emails" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

de en es ja ko ru zh

JMAP MCP Server

by jahfer

Overview Schema Related Servers Score Discussions

JavaScript

Remote

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

Prerequisites: Ensure you have Node.js installed.
Clone the repository: Clone this repository to your local machine.
Install dependencies: Navigate to the project directory and run:
```
npm install
```

Available Tools

3 tools

get_email_contentD

ParametersJSON Schema

Name	Required	Description	Default
`inputSchema`	Yes

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_mailboxesD

ParametersJSON Schema

Name	Required	Description	Default
`inputSchema`	Yes

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

search_emailsD

ParametersJSON Schema

Name	Required	Description	Default
`inputSchema`	Yes

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

3 tool updatesAug 15, 2025
- First observedget_email_content
- First observedget_mailboxes
- First observedsearch_emails

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

D1.8/5.0

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

ResponsivenessSyncing

Resources

Need Help?

Reddit Discussion

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

nylas A
io.usefulapi
MCP server for Nylas — read email, calendars, events and contacts, and send email or create events.
Email Calendar Management CRM
152
mailtempo
com.mailtempo
MCP server for MailTempo's public free temporary email inboxes.
Email Testing & QA Tools
2
email A
dev.primitive
Email infrastructure for AI agents — send, receive, search, and reply to email over MCP.
Email Communication
302
Cite CaddyOAuth
dk.herbertkokholm.citecaddy
Remote MCP server for full read/write access to a Zotero library
Research & Data Knowledge & Memory
1

Related MCP Servers

mcp-hey
Email App Automation
Sealjay
A
license
A
quality
C
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.
Updated 2 months ago (2026-07-13 04:09 UTC)
34
11
MIT
email-mcp
Email Communication
swapnilsurdi
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.
Updated 3 months ago (2026-06-06 21:18 UTC)
8
MIT
protonmail-mcp-server
Email Communication
mattias242
A
license
A
quality
C
maintenance
MCP server for reading, searching, and sending ProtonMail emails via the ProtonMail Bridge.
Updated 5 months ago (2026-03-29 06:47 UTC)
16
2
GPL 3.0
mcp-email
Email Communication
algonacci
A
license
Not graded
quality
C
maintenance
A minimal MCP server for reading, searching, managing, and sending email over IMAP and SMTP.
Updated a month ago (2026-07-28 03:49 UTC)
MIT

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jahfer/jmap-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server