Skip to main content
Glama
Sign In
DoiT MCP Server

DoiT MCP Server

Official
by doitintl
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Remote

Related Servers

Alternatives to DoiT MCP Server

No user-submitted related servers found.

    Related Servers

    • agentic-ai-devops

      satyajeetkumarsing
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLM agents to connect to multi-cloud DevOps control planes for Terraform plan inspection, drift detection and remediation, cost estimation, incident triage, and cloud resource discovery across Azure, AWS, and GCP. It supports autonomous workflows for PR review, FinOps optimization, and self-healing operations through MCP tools.
      MIT

    • E2E Networks Cloud & TIR MCP

      vingupta3
      A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to provision and manage cloud infrastructure and AI/ML workloads—such as GPUs, nodes, storage, networking, databases, Kubernetes, and training/inference resources—through natural language. It also provides a universal REST tool for authenticated access to the underlying cloud API.
      46
      18 npm
      Apache 2.0

    • cloud-tools

      munhq
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.8/5.0

    Scored across 188 tools

    Disambiguation2/5

    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.

    Naming Consistency2/5

    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.

    Tool Count1/5

    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.

    Completeness3/5

    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'.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Resources