Figmanage vs Email MCP
A side-by-side look at the Figmanage and Email MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Figmanage for communication work; choose Email MCP for communication as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Figmanage when
- You need dedicated capabilities in the Communication domain.
- You want tools like
check_auth, list_orgs, switch_org.
Choose Email MCP 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
email_list_accounts, email_add_account, email_remove_account.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 48/100 · Fair | 68/100 · Great |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | other |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 8 | 26 |
| Directory activity | 2 views 0 installs 0 upvotes | 8 views 0 installs 0 upvotes |
| Tools | 80 | 33 |
| Full listing | View Figmanage | View Email MCP |
Tools & capabilities
Figmanage tools 80
check_authValidate PAT and cookie authenticationlist_orgsList available Figma workspacesswitch_orgSwitch active workspace for this sessionlist_teamsList teams in your orglist_projectsList projects in a teamlist_filesList files in a projectlist_recent_filesRecently viewed/edited filessearchSearch files across the workspaceget_file_infoFile metadata: name, project, team, link accesslist_favoritesFavorited files (broken -- Figma BigInt bug)create_fileCreate design, whiteboard, slides, or sites filerename_fileRename a file- +68 more on the listing page
Email MCP tools 33
email_list_accountsList all configured email accounts and their connection statusemail_add_accountAdd a new IMAP or iCloud email account (Gmail and Outlook require the setup wizard for OAuth)email_remove_accountRemove an email account: deletes its stored credentials, revokes the Google grant for Gmail accounts, and removes Outlook tokens from the local token cache. The result reports whether provider-side revocation succeeded.email_test_accountTest an email account connectionemail_list_foldersList all email folders for an accountemail_searchSearch emails with filters. By default returns compact results without full body content to save context. Set returnBody=true to include full email bodies.email_getGet a single email by IDemail_get_threadGet an email thread by thread IDemail_get_attachmentGet an email attachment by ID, returns base64 encoded dataemail_save_attachmentDownload an email attachment and save it directly to disk, returning metadata only (no base64 in the response) — avoids paying the token cost of round-tripping large attachments through the calling model. outputPath is relative to a fixed downloads directory (/home/user/.email-mcp/downloads, override with EMAIL_MCP_DOWNLOADS_DIR) and cannot escape it.email_sendSend a new emailemail_replyReply to an existing email- +21 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.
Figmanage
No confirmed install command for Figmanage yet — follow the setup steps linked from its listing page rather than a guessed package name.
Email MCP
{
"mcpServers": {
"marlinjai-email-mcp": {
"command": "npx",
"args": [
"-y",
"@marlinjai/email-mcp"
]
}
}
}
Frequently asked questions
Figmanage is categorized under Communication and uses an install path we have not confirmed yet. Email MCP belongs to Communication and uses a local stdio subprocess. Pick Figmanage for communication work and Email MCP 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. Figmanage has no confirmed install command yet — follow its own setup instructions.
Figmanage has no declared pricing — check the project's own site. Email MCP 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 figmanage and marlinjai-email-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Figmanage has a quality signal of 48/100 (Fair) with 2 views, 0 installs and 8 GitHub stars. Email MCP has 68/100 (Great) with 8 views, 0 installs and 26 GitHub stars.