What is the key difference between Ethora MCP Server and Figmanage?

Ethora MCP Server belongs to the Communication category with local stdio execution, while Figmanage belongs to the Communication category with local stdio execution.

How do I install Ethora MCP Server or Figmanage in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Ethora MCP Server and Figmanage free or paid?

Ethora MCP Server operates under a Free / Open Source model (OAuth 2.0). Figmanage operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Ethora MCP Server lists 89 tools with 3 views and 6 GitHub stars. Figmanage lists 80 tools with 1 views and 8 GitHub stars.

Can I use both Ethora MCP Server and Figmanage together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Ethora MCP Server vs Figmanage

In-depth architectural comparison of the Ethora MCP Server and Figmanage MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Ethora MCP Server

Communication · Local stdio

Quality: 64/100 (Good) | Auth: OAuth 2.0

Figmanage

Communication · Local stdio

Quality: 52/100 (Good) | Auth: No auth required

Verdict Summary: Choose Ethora MCP Server if you need specialized Communication tools running via a local process. Choose Figmanage if your workspace requires Communication integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Ethora MCP Server when:

You need dedicated capabilities in the Communication domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (Free / Open Source).
You have access to required keys: ETHORA_API_URL, ETHORA_APP_JWT, ETHORA_B2B_TOKEN, ETHORA_MCP_AUTH_ISSUER.
Primary tools included: ethora-configure, ethora-status, ethora-help.

Explore Ethora MCP Server Details

Choose Figmanage when:

You need dedicated capabilities in the Communication domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: check_auth, list_orgs, switch_org.

Explore Figmanage Details

Feature & Specification Comparison

Specification	Ethora MCP Server Communication	Figmanage Communication
Summary	MCP server for the Ethora chat & messaging platform: chat ops, AI agents, RAG, automation.	Manage your Figma workspace. 76 tools for files, projects, teams, permissions, and org admin.
Category & Scope	Communication	Communication
Quality signal

Tools & Capabilities Breakdown

Ethora MCP Server Tools (89)

ethora-configure

Set the Ethora API URL and credentials for this MCP session. Stores values in memory only; each call merges with omitted fields kept. Alternative to env vars (ETHORA_API_URL / ETHORA_APP_JWT / ETHORA_APP_TOKEN / ETHORA_B2B_TOKEN). On a hosted server `apiUrl` is fixed and cannot be changed; credentials are per session. Auth: none required — this establishes auth material. Errors: only if a value is structurally invalid. Follow with an `ethora-auth-use-*` tool to pick the active mode.

ethora-status

Report the current Ethora MCP session state: configured API URL, active auth mode, which credentials are present (booleans like `hasAppJwt` — values never echoed), the selected appId/agentId, and `hosted`/`sessionId` on the hosted (Streamable HTTP) server. Auth: none required. Errors: effectively none. Related: `ethora-doctor` for an active connectivity check.

ethora-help

Task-oriented orientation for this MCP server: explains the three Ethora auth modes (user / app-token / B2B) and recommends next tool calls + recipes based on current session state. Auth: none required — inspects state, no API calls. Errors: effectively none. Related: pass a recommended recipe id to `ethora-run-recipe`.

ethora-run-recipe

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Ethora MCP Server Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "ethora-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@ethora/mcp-server"
      ],
      "env": {
        "ETHORA_API_URL": "YOUR_ETHORA_API_URL_HERE",
        "ETHORA_APP_JWT": "YOUR_ETHORA_APP_JWT_HERE",
        "ETHORA_B2B_TOKEN": "YOUR_ETHORA_B2B_TOKEN_HERE",
        "ETHORA_MCP_AUTH_ISSUER": "YOUR_ETHORA_MCP_AUTH_ISSUER_HERE"
      }
    }
  }
}

Figmanage Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "figmanage": {
      "command": "npx",
      "args": [
        "-y",
        "figmanage"
      ]
    }
  }
}

Frequently Asked Questions

Ethora MCP Server is categorized under Communication and uses a local stdio subprocess. In contrast, Figmanage belongs to Communication using local stdio subprocess. Select Ethora MCP Server when you need capabilities focused on communication and Figmanage when you require tools for communication.

More alternatives to Ethora MCP Server More alternatives to Figmanage Communication category hub