Celestial Node vs Figma Context MCP

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

Celestial Node logoCelestial NodeAerospace & Astrodynamics · Local subprocess (stdio)Real-time space data — ISS tracking, rocket launches, space news, Mars weather, and more47FairAuth: not declaredFigma 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 required

Verdict: choose Celestial Node for aerospace & astrodynamics work as a local process; choose Figma Context MCP for architecture & design as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Celestial Node logoChoose Celestial Node when

  • You need dedicated capabilities in the Aerospace & Astrodynamics domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: CELESTIAL_NODE_API_KEY.
  • You want tools like get_iss_position, get_tiangong_position, get_crew_in_space.
Explore Celestial Node

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecCelestial Node logoCelestial NodeFigma Context MCP logoFigma Context MCP
CategoryAerospace & AstrodynamicsArchitecture & Design
Quality signal47/100 · Fair71/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredAPI key required
PricingNot declaredFree
Required env varsCELESTIAL_NODE_API_KEYFIGMA_API_KEYPORT
Verified ownerCommunity listingCommunity listing
GitHub stars016,047
Directory activity 2 views 0 installs 0 upvotes 9 views 0 installs 0 upvotes
Tools182

Tools & capabilities

Celestial Node tools 18

  • get_iss_positionReal-time ISS position (lat, lon, altitude, velocity)
  • get_tiangong_positionReal-time Tiangong station position
  • get_crew_in_spaceAstronauts/cosmonauts/taikonauts currently in orbit
  • get_upcoming_launchesUpcoming rocket launches worldwide
  • get_space_newsCurated space news from NASA, ESA, CNSA, JAXA, Roscosmos, ISRO
  • get_mars_missionsAll 18 Mars missions with instruments and discoveries
  • get_mars_roversMars rovers with instruments, discoveries, and status
  • get_mars_weatherMars surface weather (temperature, pressure, wind)
  • search_starsSearch 1M+ stars from ESA Gaia catalog
  • get_star_detailsFull astronomical data for a star by Gaia source ID
  • get_constellationsAll 88 IAU constellations
  • get_near_earth_objectsUpcoming asteroid close approaches
  • +6 more on the listing page

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

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.

Celestial Node

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "celestial-node": {
      "command": "npx",
      "args": [
        "-y",
        "celestialnode-mcp"
      ],
      "env": {
        "CELESTIAL_NODE_API_KEY": "YOUR_CELESTIAL_NODE_API_KEY_HERE"
      }
    }
  }
}

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

Frequently asked questions

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

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.

Celestial Node has no declared pricing — check the project's own site. Figma Context 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 celestial-node and glips-figma-context-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Celestial Node has a quality signal of 47/100 (Fair) with 2 views, 0 installs and 0 GitHub stars. Figma Context MCP has 71/100 (Great) with 9 views, 0 installs and 16,047 GitHub stars.