appsmith-mcp
Related Servers
Alternatives to appsmith-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server that gives AI agents real browser capabilities including screenshotting, action execution, data extraction, and multi-persona auditing for frontend validation.52 npm6MIT
- FlicenseNot gradedqualityDmaintenanceMCP server that connects AI agents to browser DevTools via CDP, enabling real-time access to console logs, network requests, and page state.-
- FlicenseBqualityDmaintenanceAn MCP server that enables AI coding tools to control a browser for automated actions, UI extraction, network interception, and screenshots.231-
- AlicenseNot gradedqualityDmaintenanceMCP server for browser automation with AI agents, enabling network payload capture and QA workflows.1Apache 2.0
- FlicenseNot gradedqualityDmaintenanceMCP server that enables AI agents to automate browser testing via Chromium, providing tools for navigation, interaction, and inspection.-
- AlicenseNot gradedqualityAmaintenanceMCP server that provides AI coding agents with real-time visual access to web apps, enabling them to see screens, run accessibility and layout inspections, and interact with pages through a shared live panel.177 npm129MIT
TDQS
Scored across 57 tools
Most tools have clearly distinct purposes, with batch and individual versions (e.g., create_datasources vs create_custom_widget). However, some overlap exists between patch_js_objects and update_js_objects, and between patch_widget_code and update_custom_widget, though they target different aspects (targeted edits vs full replacement). Overall, ambiguity is low.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., create_app, list_queries, update_widgets). The naming is predictable and easy to understand, with no mixing of conventions or unclear verbs.
With 57 tools, the server is excessively large. Many tools are batch versions (e.g., create_datasources, delete_queries) that could be combined with optional parameters, and there are numerous delete tools for each resource type. The count feels inflated relative to the domain's core operations.
The tool surface covers CRUD operations for all major resources (widgets, datasources, queries, JS objects, pages, apps, themes) and includes execution, navigation, and diagnostics. Minor gaps exist, such as the lack of individual creation tools for datasources/queries/JS objects (only batch versions), but these are workable.