Figma Context MCP vs Imap MCP Server

A side-by-side look at the Figma Context MCP 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.

Figma Context MCP logoFigma Context MCPArchitecture & Design · Local subprocess (stdio)Provide coding agents direct access to Figma data to help them one-shot design implementation.71GreatAuth: api key requiredImap 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 Figma Context MCP for architecture & design 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?

Figma Context MCP logoChoose Figma Context MCP when

  • You need dedicated capabilities in the Architecture & Design domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: FIGMA_API_KEY, PORT.
  • You want tools like get_figma_data, download_figma_images.
Explore Figma Context MCP

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.

SpecFigma Context MCP logoFigma Context MCPImap MCP Server logoImap MCP Server
CategoryArchitecture & DesignCommunication
Quality signal71/100 · Great71/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthAPI key requiredother
PricingFreeFree
Required env varsFIGMA_API_KEYPORTNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars16,047111
Directory activity 9 views 0 installs 0 upvotes 8 views 0 installs 0 upvotes
Tools240

Tools & capabilities

Figma Context MCP tools 2

  • get_figma_dataGet comprehensive Figma file data including layout, content, visuals, and component information
  • download_figma_imagesDownload SVG and PNG images used in a Figma file based on the IDs of image or icon nodes. Images will be saved relative to the server's image directory: /home/user

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.

Figma Context MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "glips-figma-context-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "figma-developer-mcp"
      ],
      "env": {
        "FIGMA_API_KEY": "YOUR_FIGMA_API_KEY_HERE",
        "PORT": "YOUR_PORT_HERE"
      }
    }
  }
}

Imap MCP Server

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

Frequently asked questions

Figma Context MCP is categorized under Architecture & Design and uses a local stdio subprocess. Imap MCP Server belongs to Communication and uses a local stdio subprocess. Pick Figma Context MCP for architecture & design 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.

Figma Context MCP is listed as free. Auth: api key required. 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 glips-figma-context-mcp and imap-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Figma Context MCP has a quality signal of 71/100 (Great) with 9 views, 0 installs and 16,047 GitHub stars. Imap MCP Server has 71/100 (Great) with 8 views, 0 installs and 111 GitHub stars.