Gigachat MCP vs Hive Compute
A side-by-side look at the Gigachat MCP 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 Gigachat MCP 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 Gigachat MCP when
- You need dedicated capabilities in the Conversational AI domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
GIGACHAT_AUTH_KEY.
Choose Hive Compute when
- You need dedicated capabilities in the Conversational AI domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Conversational AI | Conversational AI |
| Quality signal | 28/100 · Emerging | 35/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | GIGACHAT_AUTH_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Gigachat MCP | View Hive Compute |
Tools & capabilities
Gigachat MCP tools
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.
Gigachat MCP
{
"mcpServers": {
"gigachat-mcp": {
"command": "npx",
"args": [
"-y",
"@theyahia/gigachat-mcp"
],
"env": {
"GIGACHAT_AUTH_KEY": "YOUR_GIGACHAT_AUTH_KEY_HERE"
}
}
}
}
Hive Compute
{
"mcpServers": {
"hive-compute": {
"url": "https://hive-mcp-gateway.onrender.com/compute/mcp"
}
}
}
Frequently asked questions
Gigachat MCP 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 Gigachat MCP 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.
Gigachat MCP 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 gigachat-mcp and hive-compute as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Gigachat MCP has a quality signal of 28/100 (Emerging) with 1 views, 0 installs and 0 GitHub stars. Hive Compute has 35/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.
