Fetchwire Social Data vs Stashr
A side-by-side look at the Fetchwire Social Data and Stashr MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
F
Fetchwire Social DataSocial MediaYouTube, TikTok, Instagram, X, Reddit, LinkedIn and Threads: public data in one schema.37FairAuth: not declaredS
StashrSocial Media · Remote HTTP/SSESearch, read, and organize your saves from X, Reddit, TikTok, Instagram, and more.37FairAuth: not declaredVerdict: choose Fetchwire Social Data for social media work; choose Stashr for social media over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
FChoose Fetchwire Social Data when
- You need dedicated capabilities in the Social Media domain.
SChoose Stashr when
- You need dedicated capabilities in the Social Media domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | F Fetchwire Social Data | S Stashr |
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 37/100 · Fair | 37/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | — |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Fetchwire Social Data | View Stashr |
Tools & capabilities
Fetchwire Social Data tools
No tool names declared yet. Check the project README from the listing page.
Stashr 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.
Fetchwire Social Data
No confirmed install command for Fetchwire Social Data yet — follow the setup steps linked from its listing page rather than a guessed package name.
Stashr
{
"mcpServers": {
"stashr": {
"url": "https://stashr.me/docs/mcp"
}
}
}
Frequently asked questions
Fetchwire Social Data is categorized under Social Media and uses an install path we have not confirmed yet. Stashr belongs to Social Media and uses a remote HTTP/SSE transport. Pick Fetchwire Social Data for social media work and Stashr for social media.
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. Fetchwire Social Data has no confirmed install command yet — follow its own setup instructions.
Fetchwire Social Data has no declared pricing — check the project's own site. Stashr 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 fetchwire-social-data and stashr as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Fetchwire Social Data has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Stashr has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.