Usgs Water vs Figma Context MCP
A side-by-side look at the Usgs Water 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.
Verdict: choose Usgs Water 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?
Choose Usgs Water when
- You need dedicated capabilities in the Environment & Nature domain.
- You prefer a local stdio subprocess transport.
- You want tools like
current_conditions, daily_values, find_sites.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Environment & Nature | Architecture & Design |
| Quality signal | 52/100 · Good | 71/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | None listed | FIGMA_API_KEYPORT |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 16,057 |
| Directory activity | 1 views 0 installs 0 upvotes | 9 views 0 installs 0 upvotes |
| Tools | 3 | 2 |
| Full listing | View Usgs Water | View Figma Context MCP |
Tools & capabilities
Usgs Water tools 3
current_conditionsLatest instantaneous (real-time) readings for one or more USGS gauge sites. Returns the most recent value per site × parameter — e.g. current streamflow and gage height for a river. Common parameter codes: 00060 = discharge/streamflow (ft³/s), 00065 = gage height (ft), 00010 = water temperature (°C…daily_valuesDaily-values time series for a single USGS site + parameter over a date range. Returns one statistic per day (default mean). Useful for trends, hydrographs, and historical comparison. Common statCd: 00003 = mean, 00001 = max, 00002 = min. Common parameter codes: 00060 = discharge (ft³/s), 00065 = g…find_sitesDiscover active USGS gauge sites in a US state that are currently reporting a given parameter (real-time). Returns sites with their latest reading; useful for finding which gauges are live in a region. Can match many sites, so results are capped. Keyless.
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
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.
Usgs Water
{
"mcpServers": {
"usgs-water": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-usgs-water"
]
}
}
}
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"
}
}
}
}
Frequently asked questions
Usgs Water 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 Usgs Water 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.
Usgs Water 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 usgs-water and glips-figma-context-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Usgs Water has a quality signal of 52/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.