A side-by-side look at the Freellmpool and Hive Compute MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Freellmpool for conversational ai work as a local process; choose Hive Compute for conversational ai over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Freellmpool when
You need dedicated capabilities in the Conversational AI domain.
No tool names declared yet. Check the project README from the listing page.
Hive Compute 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.
Freellmpool is categorized under Conversational AI and uses a local stdio subprocess. Hive Compute belongs to Conversational AI and uses a remote HTTP/SSE transport. Pick Freellmpool for conversational ai work and Hive Compute for conversational ai.
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.
Freellmpool has no declared pricing — check the project's own site. Hive Compute 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 freellmpool and hive-compute as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Freellmpool has a quality signal of 45/100 (Fair) with 0 views, 0 installs and 127 GitHub stars. Hive Compute has 35/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.