Figma Context MCP vs Jpl Ssd
A side-by-side look at the Figma Context MCP and Jpl Ssd MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Figma Context MCP for architecture & design work as a local process; choose Jpl Ssd 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?
Choose 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.
Choose Jpl Ssd when
- You need dedicated capabilities in the Aerospace & Astrodynamics domain.
- You prefer a local stdio subprocess transport.
- You want tools like
get_small_body, close_approaches, impact_risk.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Architecture & Design | Aerospace & Astrodynamics |
| Quality signal | 71/100 · Great | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | FIGMA_API_KEYPORT | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 16,061 | 0 |
| Directory activity | 10 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 2 | 4 |
| Full listing | View Figma Context MCP | View Jpl Ssd |
Tools & capabilities
Figma Context MCP tools 2
get_figma_dataGet comprehensive Figma file data including layout, content, visuals, and component informationdownload_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
Jpl Ssd tools 4
get_small_bodyNASA/JPL Solar System Dynamics — look up an asteroid or comet by name or designation and return its orbit and physical parameters (eccentricity, semi-major axis, MOID, diameter, albedo, NEO/PHA flags). Keyless.close_approachesNASA/JPL CNEOS — list near-Earth close approaches to Earth in a date range, with miss distance (AU), relative velocity (km/s), and absolute magnitude (size proxy). Keyless.impact_riskNASA/JPL CNEOS Sentry — Earth impact risk for asteroids. Pass a designation for one object's cumulative impact probability, Palermo/Torino scale, diameter, and impact window; or omit it to list all currently-tracked objects above an impact-probability threshold. Keyless.recent_fireballsNASA/JPL CNEOS — most recent atmospheric fireballs/bolides detected by U.S. Government sensors, with date, radiated and total impact energy (kilotons of TNT), location, altitude, and velocity. Keyless.
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": {
"glips-figma-context-mcp": {
"command": "npx",
"args": [
"-y",
"figma-developer-mcp"
],
"env": {
"FIGMA_API_KEY": "YOUR_FIGMA_API_KEY_HERE",
"PORT": "YOUR_PORT_HERE"
}
}
}
}
Jpl Ssd
{
"mcpServers": {
"jpl-ssd": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-jpl-ssd"
]
}
}
}
Frequently asked questions
Figma Context MCP is categorized under Architecture & Design and uses a local stdio subprocess. Jpl Ssd belongs to Aerospace & Astrodynamics and uses a local stdio subprocess. Pick Figma Context MCP for architecture & design work and Jpl Ssd 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. Jpl Ssd 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 jpl-ssd 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. Jpl Ssd has 51/100 (Good) with 1 views, 0 installs and 0 GitHub stars.