Nps vs Figma Context MCP

A side-by-side look at the Nps 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.

Nps logoNpsEnvironment & Nature · Local subprocess (stdio)NPS MCP — US National Park Service (free key, generous limits)59GoodAuth: 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 Nps for environment & nature 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?

Nps logoChoose Nps when

  • You need dedicated capabilities in the Environment & Nature domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: PLATFORM_NPS_KEY.
  • You want tools like list_parks, get_park, list_alerts.
Explore Nps

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.

SpecNps logoNpsFigma Context MCP logoFigma Context MCP
CategoryEnvironment & NatureArchitecture & Design
Quality signal59/100 · Good71/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredAPI key required
PricingNot declaredFree
Required env varsPLATFORM_NPS_KEYFIGMA_API_KEYPORT
Verified ownerCommunity listingCommunity listing
GitHub stars016,057
Directory activity 1 views 0 installs 0 upvotes 9 views 0 installs 0 upvotes
Tools62

Tools & capabilities

Nps tools 6

  • list_parksList or search NPS parks. Filter by free-text query, state code (2-letter, comma-separated), or parkCode list. Returns full name, description, designation, states, GPS, address, official URL.
  • get_parkFetch a single park by parkCode. Returns full description, designation, activities, topics, address, contacts, operating hours, entrance fees, and image gallery.
  • list_alertsCurrent park alerts — closures, road conditions, weather warnings, danger advisories. Filter by parkCode or state.
  • list_campgroundsCampgrounds inside a park or state. Returns name, description, RV/tent capacity, amenities, reservation info, GPS.
  • list_things_to_doActivities recommended by the park service — hikes, ranger programs, scenic drives, ranger-led activities. Filter by parkCode or state.
  • nps_visitationNational park visitor statistics — how many people visited a park. Answers "how many people visited Yellowstone", "NPS visitation numbers", "annual visitors to Grand Canyon", "busiest national park", "park attendance by month". Monthly + annual recreation and total visitor counts from the NPS Visitor Use Statistics service (keyless). Pass a park name or 4-letter code (e.g., YELL, GRCA, GRSM) and a year, or system_total:true for the whole national park system. Example: {"park":"yellowstone","year":2023}.

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.

Nps

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "nps": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-nps"
      ],
      "env": {
        "PLATFORM_NPS_KEY": "YOUR_PLATFORM_NPS_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

Nps is categorized under Environment & Nature and uses a local stdio subprocess. Figma Context MCP belongs to Architecture & Design and uses a local stdio subprocess. Pick Nps for environment & nature 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.

Nps 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 nps and glips-figma-context-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Nps has a quality signal of 59/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Figma Context MCP has 71/100 (Great) with 9 views, 0 installs and 16,057 GitHub stars.