Skip to main content
Glama
Harsh-Mer623

Mitti MCP Server

by Harsh-Mer623
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Mitti MCP Server

No user-submitted related servers found.

    Related Servers

    • vcf-automation-mcp-server

      mdegrasse
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables LLM clients to browse and manage VCF Automation projects, catalog items, and deployments through MCP tools, including provisioning, day-2 actions, and deleting infrastructure.
      -

    • MCP Dev MCP

      kongyo2
      A
      license
      A
      quality
      D
      maintenance
      Enables LLM agents to programmatically inspect, debug, and test other MCP servers by wrapping the MCP Inspector CLI. Supports listing and calling tools, reading resources, and testing prompts on both local and remote MCP servers.
      6
      10 npm
      MIT

    • Workspace MCP

      Deepak5106
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables LLM agents to list Google Drive files, read/write Google Sheets, and query external REST APIs through MCP tools.
      -
    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

    A3.8/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools are clearly separated by resource (templates, inspections, actions, users) and action (list, get, create, update). The main ambiguity is between inspections_list_inspections and inspections_list_inspections_view, which return the same data but differ only in presentation format, and templates_get_template_definition vs templates_get_template could confuse agents looking for template details.

    Naming Consistency4/5

    Tool names follow a consistent resource_action pattern (e.g., inspections_list_inspections, actions_get_action, users_search_users). Minor deviations include request_approval lacking a resource prefix and templates_get_template_definition being more verbose than the pattern, but overall the convention is predictable.

    Tool Count4/5

    17 tools is slightly above the ideal range but reasonable for a server covering four distinct resource domains (templates, inspections, actions, users) plus an approval utility. Each tool serves a clear purpose, though a few could be consolidated (e.g., list_inspections vs list_inspections_view).

    Completeness4/5

    The server covers the main workflows: listing and retrieving templates, inspections, actions, and users, plus creating actions and updating action status/title. Gaps include no create/update for templates or inspections, no delete operations, and no way to update inspection details, but the core read and action-management workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources