JMAP MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_mailboxesD | – |
| search_emailsD | – |
| get_email_contentD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
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.
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.
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.
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.