AgentLair vs Imap MCP Server

A side-by-side look at the AgentLair and Imap MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

AgentLair logoAgentLairCommunication · Local subprocess (stdio)Give AI agents a real @agentlair.dev email address and encrypted vault. Send/receive email.60GoodAuth: not declaredImap MCP Server logoImap MCP ServerCommunication · Local subprocess (stdio)IMAP/SMTP MCP server to search, read, organize, send, reply & forward email for AI assistants71GreatAuth: other

Verdict: choose AgentLair for communication work as a local process; choose Imap MCP Server for communication as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

AgentLair logoChoose AgentLair when

  • You need dedicated capabilities in the Communication domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: AGENTLAIR_API_KEY, AGENTLAIR_EMAIL.
  • You want tools like claim_address, send_email, check_inbox.
Explore AgentLair

Imap MCP Server logoChoose Imap MCP Server when

  • You need dedicated capabilities in the Communication domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: other.
  • You want tools like imap_add_account, imap_update_account, imap_list_accounts.
Explore Imap MCP Server

Feature & specification comparison

Rows where the two servers differ are marked.

SpecAgentLair logoAgentLairImap MCP Server logoImap MCP Server
CategoryCommunicationCommunication
Quality signal60/100 · Good71/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredother
PricingNot declaredFree
Required env varsAGENTLAIR_API_KEYAGENTLAIR_EMAILNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars5111
Directory activity 2 views 0 installs 0 upvotes 8 views 0 installs 0 upvotes
Tools1540

Tools & capabilities

AgentLair tools 15

  • claim_addressClaim a new @agentlair.dev email address for your agent. No DNS or SMTP setup required. Free tier: up to 3 addresses.
  • send_emailSend an email from an @agentlair.dev address you own to any recipient. No SMTP setup needed.
  • check_inboxCheck the inbox for an @agentlair.dev address. Returns recent messages with sender, subject, and received time.
  • read_messageRead the full content of a specific email message, including the body. Use message IDs from check_inbox.
  • list_addressesList all @agentlair.dev addresses claimed on your account.
  • vault_putStore a value in the AgentLair Vault. Use this to persist API keys, secrets, or any data your agent needs across sessions. Best practice: encrypt sensitive data client-side before storing (the server stores whatever you send).
  • vault_getRetrieve a stored value from the AgentLair Vault by key name.
  • vault_listList all keys stored in your AgentLair Vault (metadata only, values not returned).
  • vault_deleteDelete a key and all its versions from the AgentLair Vault.
  • calendar_create_eventCreate a calendar event on your AgentLair calendar. Events are published via iCal feed for human subscription (Google Calendar, Apple Calendar, Outlook).
  • calendar_list_eventsList events on your AgentLair calendar. Optionally filter by date range.
  • calendar_delete_eventDelete an event from your AgentLair calendar by event ID. Use calendar_list_events to find event IDs.
  • +3 more on the listing page

Imap MCP Server tools 40

  • imap_add_accountAdd a new IMAP account configuration
  • imap_update_accountUpdate an existing IMAP account. Useful for fixing SMTP settings without removing and re-adding the account.
  • imap_list_accountsList all configured IMAP accounts
  • imap_remove_accountRemove an IMAP account configuration
  • imap_connectConnect to an IMAP account
  • imap_disconnectDisconnect from an IMAP account
  • imap_test_accountTest an existing account connection without re-entering credentials. Validates IMAP connectivity and returns folder count and message count.
  • imap_search_emailsNote: on some servers a 'flagged' or starred message carries a custom keyword (e.g. an Open-Xchange color label or Apple's $MailFlagBit*) instead of, or in addition to, the \Flagged system flag. After any flagged search, inspect each result's customKeywords field before concluding a message is or isn't flagged — do not rely on the flagged filter alone. Search for emails matching criteria (sender, recipient, subject, body text, date range, read/flagged status). Use this to FIND messages when you know something about them but not their UID — e.g. "emails from amazon last week", "unread invoices". By default searches a single folder (INBOX). Set searchAllFolders=true to scan every mailbox at once — this catches messages filed away by rules (e.g. a receipt routed to a custom folder); Trash/Spam/Drafts are skipped unless you opt in. By default returns lightweight headers (uid, from, subject, date, and folder when searching across folders); set `includeBody=true` to also return the parsed body in one round-trip instead of paying the N+1 cost of calling imap_get_email per match. For the newest messages without criteria, prefer imap_get_latest_emails.
  • imap_get_emailRead the FULL content of a single email by its UID (body, sender/recipients, date, attachment list, optional raw headers and text-attachment previews). By default the body is returned as clean Markdown in markdownContent and raw HTML is omitted so it never crosses the boundary; set bodyFormat to "html" for the legacy raw htmlContent, or "text" for plain text only. Use after imap_search_emails or imap_get_latest_emails gives you a uid. Body text is truncated to maxContentLength to protect the context window — raise it for long messages. To fetch attachment bytes, use imap_download_attachment.
  • imap_upload_fileUpload a file to the server for use as an email attachment. Returns a path that can be used with imap_send_email attachments. This allows sending large attachments without hitting context window limits. Max size: 26214400 bytes (configurable via IMAP_MAX_UPLOAD_SIZE). Uploads are auto-deleted after 86400000 ms (configurable via IMAP_UPLOAD_TTL_MS).
  • imap_download_attachmentDownload a single attachment from an email (folder + uid + attachment filename/contentId, as listed by imap_get_email). Images are returned inline for viewing; PDFs are saved and their text is extracted inline (extractText); other files are saved to the shared downloads directory (or savePath). Use when the user wants the actual file contents, not just the message body.
  • imap_mark_as_readMark one or many emails as read. Accepts a single UID or an array — pass an array to flag N messages in one IMAP STORE round-trip (useful when triaging).
  • +28 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

AgentLair

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "agentlair": {
      "command": "npx",
      "args": [
        "-y",
        "@agentlair/mcp@latest"
      ],
      "env": {
        "AGENTLAIR_API_KEY": "YOUR_AGENTLAIR_API_KEY_HERE",
        "AGENTLAIR_EMAIL": "YOUR_AGENTLAIR_EMAIL_HERE"
      }
    }
  }
}

Imap MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "imap-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "imap-mcp-server"
      ]
    }
  }
}

Frequently asked questions

AgentLair is categorized under Communication and uses a local stdio subprocess. Imap MCP Server belongs to Communication and uses a local stdio subprocess. Pick AgentLair for communication work and Imap MCP Server for communication.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

AgentLair has no declared pricing — check the project's own site. Imap MCP Server is listed as free. Auth: other. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add agentlair and imap-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, AgentLair has a quality signal of 60/100 (Good) with 2 views, 0 installs and 5 GitHub stars. Imap MCP Server has 71/100 (Great) with 8 views, 0 installs and 111 GitHub stars.