A side-by-side look at the Govir and FeedHive MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Govir for social media work over a hosted endpoint; choose FeedHive 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?
G
Choose Govir when
You need dedicated capabilities in the Social Media domain.
No tool names declared yet. Check the project README from the listing page.
FeedHive 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.
Govir is categorized under Social Media and uses a remote HTTP/SSE transport. FeedHive belongs to Social Media and uses a remote HTTP/SSE transport. Pick Govir for social media work and FeedHive 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.
Govir has no declared pricing — check the project's own site. FeedHive 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 govir and feedhive as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Govir has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. FeedHive has 42/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.