Figmanage vs Discord MCP

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

Figmanage logoFigmanageCommunicationManage your Figma workspace. 76 tools for files, projects, teams, permissions, and org admin.48FairAuth: not declaredDiscord MCP logoDiscord MCPCommunication · Local subprocess (stdio)Lightweight multi-guild Discord MCP server with 60+ tools for messages, channels, roles, forums, webhooks, and moderation.67GreatAuth: api key required

Verdict: choose Figmanage for communication work; choose Discord 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?

Figmanage logoChoose Figmanage when

  • You need dedicated capabilities in the Communication domain.
  • You want tools like check_auth, list_orgs, switch_org.
Explore Figmanage

Discord MCP logoChoose Discord MCP when

  • You need dedicated capabilities in the Communication domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: DISCORD_TOKEN, DISCORD_MESSAGE_CONTENT, DISCORD_GUILD_MEMBERS, DISCORD_MCP_TOOLSETS, DISCORD_ALLOWED_GUILDS.
  • You want tools like discord_list_guilds, discord_get_guild_info, discord_list_channels.
Explore Discord MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecFigmanage logoFigmanageDiscord MCP logoDiscord MCP
CategoryCommunicationCommunication
Quality signal48/100 · Fair67/100 · Great
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredAPI key required
PricingNot declaredFree
Required env varsNone listedDISCORD_TOKENDISCORD_MESSAGE_CONTENTDISCORD_GUILD_MEMBERSDISCORD_MCP_TOOLSETSDISCORD_ALLOWED_GUILDS
Verified ownerCommunity listingCommunity listing
GitHub stars829
Directory activity 2 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
Tools8099

Tools & capabilities

Figmanage tools 80

  • check_authValidate PAT and cookie authentication
  • list_orgsList available Figma workspaces
  • switch_orgSwitch active workspace for this session
  • list_teamsList teams in your org
  • list_projectsList projects in a team
  • list_filesList files in a project
  • list_recent_filesRecently viewed/edited files
  • searchSearch files across the workspace
  • get_file_infoFile metadata: name, project, team, link access
  • list_favoritesFavorited files (broken -- Figma BigInt bug)
  • create_fileCreate design, whiteboard, slides, or sites file
  • rename_fileRename a file
  • +68 more on the listing page

Discord MCP tools 99

  • discord_list_guildsList every Discord server (guild) the bot is a member of (id, name, member count, icon). Takes no arguments. Read-only. Start here to discover the guild_id needed by most other tools.
  • discord_get_guild_infoGet details about one server: name, description, member/channel/role counts, boost tier, owner, and creation date. Read-only. Use discord_get_server_stats for a finer breakdown (humans vs bots, channel types).
  • discord_list_channelsList all channels in a server, grouped by their parent category and ordered by position. Returns a JSON object keyed by category name. Read-only. Use discord_find_channel_by_name to locate a specific channel.
  • discord_find_channel_by_nameFind channels whose name contains a substring (case-insensitive). Returns matching channels (id, name, type) as a JSON array. Read-only. Useful for resolving a channel_id when you only know the channel's name.
  • discord_read_messagesRead messages from a text channel or thread, oldest-to-newest. Page backwards by re-calling with before set to the id of the oldest message you received, which walks a channel past the 100-message per-call cap. Requires the View Channel and Read Message History permissions. Returns { messages: [...] } with id, author, content, timestamp, attachment count, pinned flag. Use discord_search_messages to filter by keyword, or discord_fetch_pinned_messages for pinned messages only.
  • discord_send_messageSend a plain-text message to a channel or thread. For rich content (title, color, fields, images) use discord_send_embed; to attach a reply reference to an existing message use discord_reply_message. Requires the bot to have the Send Messages permission. Returns the new message ID.
  • discord_reply_messageReply to a specific message, attaching a reply reference so clients show it as a threaded reply. Use discord_send_message for a standalone message with no reference. Requires the Send Messages permission. Returns the new reply's message ID.
  • discord_edit_messageEdit the text content of a message previously sent by this bot. Discord forbids editing other users' messages, so this fails for non-bot messages. Use discord_edit_embed for embed messages. Works in text channels and threads. Returns the edited message ID.
  • discord_add_reactionAdd a single emoji reaction to a message as the bot. Requires the Add Reactions and Read Message History permissions. Use discord_remove_reactions to undo. Idempotent: re-adding the bot's existing reaction has no effect.
  • discord_create_threadCreate a thread, either branching from an existing message (pass message_id) or as a standalone thread in a text channel (omit message_id). Standalone creation requires a parent text channel and fails if channel_id is itself a thread. Requires the Create Public Threads permission. Returns the new thread's ID.
  • discord_bulk_delete_messagesPermanently delete multiple recent messages in one call. IRREVERSIBLE. SAFE BY DEFAULT: dry_run is true unless explicitly set to false, so call it first to preview, then re-call with dry_run:false to actually delete. Discord only allows bulk-deleting messages younger than 14 days; older ones are skipped. Requires the Manage Messages permission. Returns the number deleted.
  • discord_send_embedSend a single rich embed (title, description, color, fields, author, footer, images, timestamp). Use discord_send_message for plain text, or discord_send_multiple_embeds to send several embeds at once. Requires the Send Messages and Embed Links permissions. Returns the new message ID.
  • +87 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.

Discord MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "pasympa-discord-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@pasympa/discord-mcp"
      ],
      "env": {
        "DISCORD_TOKEN": "YOUR_DISCORD_TOKEN_HERE",
        "DISCORD_MESSAGE_CONTENT": "YOUR_DISCORD_MESSAGE_CONTENT_HERE",
        "DISCORD_GUILD_MEMBERS": "YOUR_DISCORD_GUILD_MEMBERS_HERE",
        "DISCORD_MCP_TOOLSETS": "YOUR_DISCORD_MCP_TOOLSETS_HERE",
        "DISCORD_ALLOWED_GUILDS": "YOUR_DISCORD_ALLOWED_GUILDS_HERE"
      }
    }
  }
}

Frequently asked questions

Figmanage is categorized under Communication and uses an install path we have not confirmed yet. Discord MCP belongs to Communication and uses a local stdio subprocess. Pick Figmanage for communication work and Discord 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. Discord MCP is listed as free. Auth: api key required. 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 pasympa-discord-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. Discord MCP has 67/100 (Great) with 2 views, 0 installs and 29 GitHub stars.