Skip to main content
Glama
bakhtarimohammad

hamravesh-mcp

by bakhtarimohammad
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to hamravesh-mcp

No user-submitted related servers found.

    Related Servers

    • quads-mcp

      grafuls
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for interacting with QUADS infrastructure systems via API, enabling resource management and automation through LLM applications.
      MIT

    • Kubernetes MCP Server

      dkeeno
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for generating Kubernetes manifests (deployments, services, configmaps, secrets, ingresses, namespaces) and performing kubectl operations like apply, delete, get, describe, logs, and exec.
      MIT

    • Infisical MCP

      plgonzalezrx8
      F
      license
      Not graded
      quality
      D
      maintenance
      FastMCP server for managing a self-hosted Infisical instance, exposing tools to create, read, update, and delete projects, environments, folders, and secrets, and to render .env and shell-export formats.
      -

    • litellm-mcp

      weeebdev
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that provides tools to interact with the LiteLLM proxy API, enabling LLM completions, embeddings, image generation, and admin operations.
      7 npm
      MIT
    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.9/5.0

    Scored across 30 tools

    Disambiguation4/5

    Each tool targets a distinct resource/action, and the main potential confusions (e.g., list_saas vs. list_marketplace_products, create_saas vs. create_app) are clarified by their descriptions. A couple of similar lifecycle actions on different resources could still cause misselection, but the boundaries are mostly clear.

    Naming Consistency4/5

    The dominant hamravesh_verb_noun pattern is consistent and readable. The few exceptions like app_containers, app_logs, app_manifests, and database_power break the otherwise predictable convention, but they are still recognizable and not chaotic.

    Tool Count2/5

    At 30 tools, the server exceeds the 25-tool threshold and feels heavy even for a broad cloud-management API. Several write tools are disabled by default, and some subresource operations could plausibly be consolidated, making the surface larger than necessary.

    Completeness3/5

    Core app and database lifecycles are well covered, including create/read/delete, but SaaS has no update/delete tool, database plans/updates are missing as dedicated tools, and app updates are limited to envs/basic auth. The raw hamravesh_request tool helps agents work around these gaps, but notable operations still lack first-class support.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources