DoiT MCP Server
OfficialRelated Servers
Alternatives to DoiT MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceProvides tools and context for interacting with Google Cloud services, enabling natural language management of billing, monitoring, logging, IAM, Spanner, and more.56260 npmApache 2.0

Gcore MCP Serverofficial
AlicenseCqualityCmaintenanceEnables interaction with Gcore Cloud API via LLM assistants, providing tools for managing instances, networking, storage, AI/ML, and more.4211Apache 2.0- AlicenseNot gradedqualityDmaintenanceEnables LLM clients to interact with Azure cost analysis, budget tracking, forecasting, and resource optimization across multiple subscriptions.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to query multi-cloud costs, inventory, waste, and commitments across AWS, GCP, Cloudflare, and OVH through read-only MCP tools.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceProvides AI agents with natural language control over AWS, Azure, GCP, and Alibaba Cloud infrastructure through dynamic API discovery and execution. Supports 51,900+ cloud operations and includes OpenTofu integration for complete infrastructure lifecycle management.3MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to query multi-cloud cost and usage data through a uniform read-only toolset, including cost summaries, trends, budgets, forecasts, and optimization recommendations.MIT
TDQS
Scored across 188 tools
Several tool pairs are nearly indistinguishable by name alone, such as delete_insight_result vs delete_insight_results, delete_datahub_dataset vs delete_datahub_datasets, and list_billing_transfer_end_customers vs list_billing_transfer_end_customers_by_reseller. While many descriptions are detailed and include 'do not use' guidance, the sheer number of overlapping concepts (cloud diagrams, insights, cost analysis) creates real misselection risk.
The dominant verb_noun pattern is frequently broken by noun_verb tools (cost_breakdown, ava_feedback), redundant phrasing (test_run_cloudflow_flow, list_cloudflow_flow_runs), and inconsistent terminology (cloud_flow vs cloudflow, custom_theme vs theme, post_ vs create_). Plural/singular inconsistency in delete/post insight and datahub tools further compounds the confusion.
188 tools is an extreme count for an MCP server, far beyond even the 'too many' threshold. While the server spans many DoiT product domains, this breadth creates a sprawling surface that is impractical for an agent to navigate effectively.
Most subdomains have solid CRUD coverage: tickets, budgets, alerts, allocations, labels, annotations, folders, reports, users, and DataHub all have list/get/create/update/delete where appropriate. However, there are notable gaps and inconsistencies—descriptions reference a non-existent list_insights tool, cloud diagram snapshots lack create/delete, and the PerfectScale commitments surface is read-only despite claiming to 'plan and automate purchases'.