duet-mcp
Related Servers
Alternatives to duet-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceExposes every generated Express service to LLM clients over HTTP as MCP tools (create, update, delete actions) and resources (list and get-by-id context), so AI assistants can discover and manipulate application data without raw HTTP calls. This lets teams run a single codebase that serves both traditional REST clients and AI agents such as Cursor or Claude.MIT
- AlicenseNot gradedqualityAmaintenanceEnables LLMs to discover and invoke generated API actions as MCP tools and read context through MCP resources for list and get-by-id operations. It provides HTTP-based MCP access for clients such as Cursor and Claude without extra glue code.MIT
- AlicenseNot gradedqualityAmaintenanceExposes every generated CRUD service to LLM clients such as Claude, ChatGPT, or Cursor through discoverable MCP tools for create, update, and list actions plus read-only resources, so models can query and manipulate data without raw HTTP calls. It runs alongside the same codebase's REST endpoints, letting clients and AI share one data layer.MIT
- AlicenseNot gradedqualityBmaintenanceEnables LLMs to interact with generated CRUD services through MCP tools and resources, so they can create, update, list, and fetch records via a standard protocol. It also provides REST API access from the same codebase for traditional clients.MIT
- AlicenseNot gradedqualityAmaintenanceEnables LLMs to discover and invoke generated CRUD operations as MCP tools and read data through MCP resources, alongside standard REST endpoints, using one codebase.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server enabling AI agents to collaborate in shared rooms with a document edited via compare-and-swap optimistic concurrency, plus a chat channel and change deltas.34 npmMIT
TDQS
Scored across 7 tools
set_text and set_settings overlap somewhat because set_settings can update 'notes', which could be confused with the note text set_text replaces. The other tools are clearly distinct, but this boundary ambiguity makes mis-selection possible.
Most tools follow a clean verb_noun pattern: set_text, set_settings, set_box, await_change, render_screenshot, and read_blob. gui_url is the outlier and would be clearer as get_gui_url, but the overall convention is still predictable.
Seven tools is well-scoped for this collaborative canvas server. Each tool serves a distinct role: mutating text/settings/box, observing changes, rendering views, and reading blobs.
The surface covers the main observe-modify-render workflow: await_change provides current state and revision, set_* tools make changes, and render_screenshot/read_blob provide outputs. Minor gaps exist around explicit create/delete operations for boxes or blob uploads, but they may not be required by the intended domain.