Skip to main content
Glama
Davidgraciano

appsmith-mcp

by Davidgraciano
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to appsmith-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-server

      gwanghun-choi
      A
      license
      Not graded
      quality
      C
      maintenance
      A universal MCP server for registering internal, external, and OpenAPI-based APIs as MCP tools. It exposes them to MCP clients via Streamable HTTP and provides admin portal, RBAC/session auth, credential injection, and audit logging.
      Academic Free v1.1

    • jumpcloud-mcp

      LesterAJohn
      A
      license
      B
      quality
      B
      maintenance
      MCP server for JumpCloud APIs with full OpenAPI-driven coverage, enabling endpoint discovery, operation invocation, and direct API requests while managing multi-tenant user tokens in Vault and guarding mutating tools.
      20
      MIT

    • Gripp MCP

      maxancedecot
      F
      license
      A
      quality
      B
      maintenance
      MCP server for the Gripp API, enabling CRUD operations on Gripp entities with built-in confirmation safety for mutations.
      9
      6 npm
      1
      -

    • 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

    • hamravesh-mcp

      bakhtarimohammad
      A
      license
      C
      quality
      B
      maintenance
      MCP server to manage Hamravesh (Darkube) apps via the console's internal API, supporting read and write operations like listing apps, viewing logs, restarting, scaling, and updating environment variables.
      30
      2
      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

    B3.4/5.0

    Scored across 30 tools

    Disambiguation4/5

    Most tools target clearly distinct resources and actions (workspaces, applications, pages, queries, JS objects, widgets, datasources). A few overlaps exist: appsmith_list_applications vs appsmith_search_entities both find apps, and get_widget/update_widget/clone_widget vs get_page are adjacent, but descriptions clarify each tool's distinct purpose well.

    Naming Consistency4/5

    Tools largely follow the appsmith_verb_noun pattern consistently (list_, create_, update_, delete_, get_, clone_, execute_, export_). Minor deviations like appsmith_whoami (noun-style) and appsmith_api_request (generic verb) break the pattern slightly, but the overall convention is coherent and predictable.

    Tool Count3/5

    At 30 tools, this is on the heavy side for an MCP server, exceeding the typical 3-15 well-scoped range. However, Appsmith is a broad platform covering workspaces, apps, pages, queries, JS objects, widgets, and datasources, so each tool reasonably earns its place across the resource categories.

    Completeness4/5

    The surface covers CRUD across most resource types: workspaces (create/list), applications (create/list/clone/delete/export/publish), pages (create/get/list), queries (create/update/delete/execute), JS objects (create/update/delete), widgets (get/update/clone). Minor gaps include no delete_page or delete_datasource, and the generic appsmith_api_request fallback covers edge cases.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources