imap-mcp

Overview Schema Source Related Servers Discussions Admin

Server and account information

get_server_info

Read-onlyIdempotent

Reports the configured mailbox, IMAP capabilities, permanent flags, new-mail keyword support, and enabled tool groups to diagnose configuration failures.

Instructions

Reports what this account and server can do: the configured mailbox, IMAP capabilities, which flags the mailbox stores permanently, whether the new-mail keyword can be used, and which tool groups are enabled. Start here when a call fails for reasons that sound like configuration.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`tls`	Yes
`host`	Yes
`port`	Yes
`limits`	Yes
`mailbox`	Yes	The default this server selects.
`capabilities`	Yes
`can_send_mail`	Yes	This server cannot send mail at all, by design.
`permanent_flags`	Yes
`new_mail_tracking`	Yes
`write_tools_enabled`	Yes
`attachment_downloads`	Yes
`permanent_flags_reported`	Yes	False when the server sent no PERMANENTFLAGS, which means every flag can be stored; permanent_flags is then empty.
`attachment_text_extraction`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.5.2Oct 5, 2026

addedOutput schema / properties / permanent_flags_reported

Added value: +{
+  "description": "False when the server sent no PERMANENTFLAGS, which means every flag can be stored; permanent_flags is then empty.",
+  "type": "boolean"
+}

changedOutput schema / required

Previous value: -[
-  "host",
-  "port",
-  "tls",
-  "mailbox",
-  "capabilities",
-  "permanent_flags",
-  "new_mail_tracking",
-  "write_tools_enabled",
-  "can_send_mail",
-  "attachment_downloads",
-  "attachment_text_extraction",
-  "limits"
-]New value: +[
+  "host",
+  "port",
+  "tls",
+  "mailbox",
+  "capabilities",
+  "permanent_flags",
+  "permanent_flags_reported",
+  "new_mail_tracking",
+  "write_tools_enabled",
+  "can_send_mail",
+  "attachment_downloads",
+  "attachment_text_extraction",
+  "limits"
+]

Changed2 schema fields changedv0.5.0Sep 8, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "attachment_downloads": {
+      "additionalProperties": false,
+      "properties": {
+        "as_resource": {
+          "type": "boolean"
+        },
+        "directory": {
+          "type": "string"
+        },
+        "max_bytes": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        "reason": {
+          "description": "Only when saving to disk is off.",
+          "type": "string"
+        },
+        "to_disk": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "as_resource",
+        "to_disk"
+      ],
+      "type": "object"
+    },
+    "attachment_text_extraction": {
+      "additionalProperties": false,
+      "properties": {
+        "enabled": {
+          "const": true,
+          "type": "boolean"
+        },
+        "extractable_types": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "max_bytes": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        }
+      },
+      "required": [
+        "enabled",
+        "max_bytes",
+        "extractable_types"
+      ],
+      "type": "object"
+    },
+    "can_send_mail": {
+      "const": false,
+      "description": "This server cannot send mail at all, by design.",
+      "type": "boolean"
+    },
+    "capabilities": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "host": {
+      "type": "string"
+    },
+    "limits": {
+      "additionalProperties": false,
+      "properties": {
+        "allowed_attachment_types": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "default_message_limit": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        "max_inline_attachment_bytes": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        }
+      },
+      "required": [
+        "default_message_limit",
+        "max_inline_attachment_bytes",
+        "allowed_attachment_types"
+      ],
+      "type": "object"
+    },
+    "mailbox": {
+      "description": "The default this server selects.",
+      "type": "string"
+    },
+    "new_mail_tracking": {
+      "additionalProperties": false,
+      "properties": {
+        "enabled": {
+          "type": "boolean"
+        },
+        "keyword": {
+          "type": "string"
+        },
+        "reason": {
+          "description": "Only when it is off.",
+          "type": "string"
+        },
+        "storable": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "enabled"
+      ],
+      "type": "object"
+    },
+    "permanent_flags": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "port": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "tls": {
+      "type": "string"
+    },
+    "write_tools_enabled": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "host",
+    "port",
+    "tls",
+    "mailbox",
+    "capabilities",
+    "permanent_flags",
+    "new_mail_tracking",
+    "write_tools_enabled",
+    "can_send_mail",
+    "attachment_downloads",
+    "attachment_text_extraction",
+    "limits"
+  ],
+  "type": "object"
+}

First observedv0.2.0Aug 31, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, and an output schema exists, so the safety/return burden is light. The description still adds value by framing the result as a capability/diagnostic snapshot (permanent flags, new-mail support, enabled groups), which tells the agent what kind of state it is inspecting.

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

Conciseness5/5

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

One dense sentence listing the reported capabilities, followed by a short actionable 'start here' sentence. Front-loaded and waste-free.

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

Completeness4/5

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

For a zero-parameter diagnostic tool with a rich output schema and full annotations, this is nearly complete: it states what is reported and when to reach for it. Only minor gap is it doesn't hint at how to use the output (e.g., adjusting subsequent calls based on capabilities).

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

Parameters4/5

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

There are zero parameters, so the baseline is 4. The description correctly does not invent any parameter discussion.

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

Purpose5/5

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

The description enumerates exactly what the tool reports: the mailbox, IMAP capabilities, permanent flags, the new-mail keyword, and enabled tool groups. This is a much sharper picture than the title and clearly distinguishes it from the data-retrieval siblings (get_message, list_*).

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

Usage Guidelines5/5

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

It gives an explicit trigger — 'Start here when a call fails for reasons that sound like configuration.' That is a concrete when-to-use condition that routes the agent to this diagnostic tool rather than to the data tools.

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

Deploy Server