Figshare vs Site — MCP Server Comparison | AllMCPs
Figshare vs Site
A side-by-side look at the Figshare and Site MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
No tool names declared yet. Check the project README from the listing page.
Site tools
No tool names declared yet. Check the project README from the listing page.
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.
No confirmed install command for Site yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Figshare is categorized under Research and uses a local stdio subprocess. Site belongs to Research and uses an install path we have not confirmed yet. Pick Figshare for research work and Site for research.
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. Site has no confirmed install command yet — follow its own setup instructions.
Figshare has no declared pricing — check the project's own site. Site is listed as free. Auth: no auth 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 figshare and site-37 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Figshare has a quality signal of 40/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Site has 43/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.