A
licenseA
qualityF
maintenanceEnables interaction with Sber GigaChat API for chat, embeddings, image generation, token counting, balance checks, assistants, and file uploads through natural language tools.
8
63 npm
MIT
Gcore MCP Server
Officialby G-Core
Related Servers
Alternatives to Gcore MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceEnables AI assistants to interact with Google Cloud Platform resources through natural language queries. Supports querying and managing GCP services like Compute Engine, Cloud Storage, BigQuery, and more across multiple projects and regions.94,042 npmMIT
- AlicenseCqualityDmaintenanceProvides tools and context for interacting with Google Cloud services, enabling natural language management of billing, monitoring, logging, IAM, Spanner, and more.56120 npmApache 2.0
- FlicenseNot gradedqualityDmaintenanceProvides 30+ read-only tools for querying Google Cloud Platform infrastructure, designed for AI assistants and Terraform workflows.-
- AlicenseCqualityDmaintenanceEnables AI assistants to manage multi-cloud resources (AWS, Azure, GCP) including resource operations, cost analysis, monitoring metrics, and security compliance checks through natural language commands.265 npm2MIT
- FlicenseNot gradedqualityDmaintenanceEnables managing Google Cloud Platform infrastructure through natural language, including VM deployment, SSH key management, remote command execution, and Terraform infrastructure-as-code operations.2-
TDQS
C2.8/5.0
Scored across 42 tools
Disambiguation3/5
Most tools have distinct purposes, but there is confusion because image-related tools (e.g., cloud_insts_imgs_ls) are nested under the 'insts' prefix, making them appear to be instance operations. Also, cloud_insts_act is a proxy for various actions, which could overlap with specific tools like cloud_insts_resz.
Naming Consistency2/5
Naming is inconsistent: abbreviations like 'insts' and 'placegrps' mix with full words like 'projects' and 'regions'. Verb forms vary (new, del, upd, act, resz, add_placegrp, rm_placegrp) and the 'cloud_insts_' prefix is reused for flavors and images, violating the pattern.
Tool Count2/5
42 tools is excessive for a coherent set. Many are narrowly scoped sub-operations (e.g., assign/unassign security group, add/remove placement group) that could be merged. A typical well-scoped server has 3-15 tools.
Completeness2/5
The tool surface covers instances, projects, regions, quotas, and tasks but lacks fundamental resources: no volume CRUD, no security group lifecycle, no network/subnet/router management. Agents would likely fail when needing those operations.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive