Figma Context MCP vs HelioSPICE

A side-by-side look at the Figma Context MCP and HelioSPICE 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 requiredHelioSPICE logoHelioSPICEAerospace & Astrodynamics · Local subprocess (stdio)Spacecraft ephemeris made easy — auto-managed SPICE kernels for heliophysics47FairAuth: not declared

Verdict: choose Figma Context MCP for architecture & design work as a local process; choose HelioSPICE for aerospace & astrodynamics 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

HelioSPICE logoChoose HelioSPICE when

  • You need dedicated capabilities in the Aerospace & Astrodynamics domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: XHELIO_SPICE_KERNEL_DIR.
  • You want tools like get_ephemeris, compute_distance, transform_coordinates.
Explore HelioSPICE

Feature & specification comparison

Rows where the two servers differ are marked.

SpecFigma Context MCP logoFigma Context MCPHelioSPICE logoHelioSPICE
CategoryArchitecture & DesignAerospace & Astrodynamics
Quality signal71/100 · Great47/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthAPI key requiredNot declared
PricingFreeNot declared
Required env varsFIGMA_API_KEYPORTXHELIO_SPICE_KERNEL_DIR
Verified ownerCommunity listingCommunity listing
GitHub stars16,0610
Directory activity 10 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools26

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

HelioSPICE tools 6

  • get_ephemerisPosition/velocity — single time (inline) or timeseries (CSV)
  • compute_distanceDistance between two bodies
  • transform_coordinatesCoordinate frame transform
  • list_spice_missionsSupported missions
  • list_coordinate_framesAvailable frames with descriptions
  • manage_kernelsKernel cache management

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"
      }
    }
  }
}

HelioSPICE

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "heliospice": {
      "command": "uvx",
      "args": [
        "xhelio-spice"
      ],
      "env": {
        "XHELIO_SPICE_KERNEL_DIR": "YOUR_XHELIO_SPICE_KERNEL_DIR_HERE"
      }
    }
  }
}

Frequently asked questions

Figma Context MCP is categorized under Architecture & Design and uses a local stdio subprocess. HelioSPICE belongs to Aerospace & Astrodynamics and uses a local stdio subprocess. Pick Figma Context MCP for architecture & design work and HelioSPICE for aerospace & astrodynamics.

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. HelioSPICE has no declared pricing — check the project's own site. 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 heliospice 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 10 views, 0 installs and 16,061 GitHub stars. HelioSPICE has 47/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.