Site vs Figshare
A side-by-side look at the Site and Figshare MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
SiteResearchCASP Checklist: the site's own MCP server — checker, enquiry (enquiry = a human handoff, not a...43FairAuth: no auth requiredVerdict: choose Site for research work; choose Figshare for research as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
SChoose Site when
- You need dedicated capabilities in the Research domain.
- Its auth model fits you: No auth required.
Choose Figshare when
- You need dedicated capabilities in the Research domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
Tools & capabilities
Site tools
No tool names declared yet. Check the project README from the listing page.
Figshare 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.
Site
No confirmed install command for Site yet — follow the setup steps linked from its listing page rather than a guessed package name.
Figshare
{
"mcpServers": {
"figshare": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-figshare"
]
}
}
}
Frequently asked questions
Site is categorized under Research and uses an install path we have not confirmed yet. Figshare belongs to Research and uses a local stdio subprocess. Pick Site for research work and Figshare 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.
Site is listed as free. Auth: no auth required. Figshare 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 site-37 and figshare as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Site has a quality signal of 43/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Figshare has 40/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.