Skip to main content
Glama
Soundhannes

IMAP MCP Server

by Soundhannes

auto_connect

Automatically establish IMAP email connections using stored configuration credentials to access email accounts for reading, searching, and organizing messages.

Instructions

Connect using config.json credentials (no parameters needed)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core logic for auto_connect which loads configuration, connects, authenticates, and initializes the watcher.
    def auto_connect(self, config_path: str = "config.json") -> bool:
        """Connect using config.json credentials."""
        self.load_config(config_path)
        self.config["_config_path"] = config_path  # Store for watcher
        imap_config = self.config.get("imap", {})
        creds = self.config.get("credentials", {})
    
        self.connect(
            host=imap_config.get("host"),
            port=imap_config.get("port", 993),
            secure=imap_config.get("secure", True),
        )
        self.authenticate(creds.get("username"), creds.get("password"))
        self._load_auto_archive_config()
    
        # Auto-start watcher if cache is enabled
        if self.config.get("cache", {}).get("enabled", True):
            self.watcher = get_watcher(config_path)
            self.watcher.start()
            self.watching = True
    
        return True
  • Registration/Dispatch of the auto_connect MCP tool in the server request handler.
    elif name == "auto_connect":
        return imap_client.auto_connect()
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the credential source but lacks details on what happens on success/failure, whether it establishes a persistent session, error handling, or any side effects. This is inadequate for a connection tool with zero annotation coverage.

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?

The description is a single, efficient sentence that front-loads the key information (action and credential source) with no wasted words. It is appropriately sized for a simple, parameterless tool.

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

Completeness2/5

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

Given the complexity of a connection operation, no annotations, and no output schema, the description is incomplete. It doesn't explain what the tool returns, error conditions, or behavioral traits like session management, which are critical for an agent to use it correctly.

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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description correctly states 'no parameters needed,' which adds value by clarifying this explicitly, aligning with the schema. A baseline of 4 is appropriate for zero-parameter tools.

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

Purpose4/5

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

The description clearly states the action ('Connect') and specifies the authentication method ('using config.json credentials'), which distinguishes it from the sibling 'connect' tool that likely requires explicit parameters. However, it doesn't explicitly mention what is being connected (e.g., to an email server), leaving some ambiguity.

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

Usage Guidelines3/5

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

The description implies usage when credentials are pre-configured in config.json, suggesting an alternative to parameter-based authentication. However, it doesn't explicitly state when NOT to use it (e.g., if config.json is missing) or compare it directly to the sibling 'connect' tool, leaving some context to inference.

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

Install Server

Other Tools

Latest Blog Posts

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/Soundhannes/IMAP-MCP'

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