mcp-server-dalux
Related Servers
Alternatives to mcp-server-dalux
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP Server to communite with the Procore API722MIT
- MIT
- AlicenseAqualityAmaintenanceMCP server for Taskboi task management, enabling project and task operations with recurrence and priority support via the Taskboi API.163 npmApache 2.0
- AlicenseAqualityDmaintenanceMCP server for Dataiku DSS REST APIs, enabling flow analysis and day-to-day operations on projects, datasets, recipes, jobs, scenarios, folders, variables, connections, and code environments.949 npmMIT
- AlicenseAqualityDmaintenanceMCP server for interacting with Realm MinistryPlatform data, enabling queries, record creation, and updates from any MCP client.1MIT
- AlicenseAqualityCmaintenanceMCP server for the bexio API, enabling interaction with contacts, sales, accounting, projects, and more through 35 tools. Supports both PAT and OAuth authentication with read-only mode and tool group filtering.354MIT
TDQS
Scored across 24 tools
Resource domains (projects, tasks, forms, quality plans, files, companies, metadata) are mostly cleanly separated, and the change/export/download tools have unique roles. The main ambiguity is that many `list_*` tools also fetch a single record by id (e.g. list_projects vs get_project, list_files, list_companies, list_version_sets), overlapping conceptually with `get_*` tools, though descriptions usually clarify.
All tools use a uniform `dalux_` prefix with snake_case verb_noun naming (list_, get_, search_, export_, download_, upload_, change_). The `change_` verb consistently covers create/update for both companies and projects, so the convention is predictable throughout.
24 tools is at the heavy end of the 16–25 range. The breadth of Dalux subdomains (Field tasks, forms, QA plans, Box files, companies, metadata, writes) justifies many tools, but some consolidation (e.g. attachment listings, single-record fetch behavior patched into list tools) could reduce surface area.
Read coverage is broad and coherent across projects, users, tasks, forms, quality plans, work packages, files, version sets and companies, with export, download, upload and change operations for the writable parts. Gaps remain: no delete operations, no folder creation, and the task/form domains are read-only (partly due to Dalux API limitations), but core workflows are coverable.