D-Tools MCP Server
Related Servers
Alternatives to D-Tools MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI assistants to discover, install, configure, and manage MCP servers through natural language conversation, automating tedious manual setup across multiple clients.11MIT
- FlicenseNot gradedqualityDmaintenanceA production-ready MCP server that connects AI assistants to LevelBlue's USM Anywhere security platform, enabling advanced security queries, investigation management, and threat analysis through natural language.1-
- AlicenseNot gradedqualityCmaintenanceA production-ready MCP server that enables AI assistants to manage enterprise Active Directory environments through 45 specialized tools for users, groups, and GPOs. Its multi-client architecture allows for the secure management of multiple AD domains from a single codebase using natural language commands.3MIT
- -licenseNot gradedqualityCmaintenanceAn MCP server that bridges AI assistants with SQL databases, enabling natural language querying across multiple database types with built-in optimization and security.3-

oitvoip-mcp-serverofficial
FlicenseBqualityDmaintenanceA Model Context Protocol (MCP) server that provides AI agents with seamless access to the NetSapiens VoIP platform for user management, call analytics, and system administration.234-- AlicenseAqualityBmaintenanceMCP server for the Housecall Pro API, letting AI assistants read and write Housecall Pro data—customers, jobs, invoices, estimates, scheduling, and more—through natural language.440 npmMIT
TDQS
Scored across 25 tools
Most tools are clearly distinct per resource, but there is overlap between archive_project and update_project (both can change archive status) and between search_products and list_catalogs (both filter catalog entries). This creates some ambiguity.
Naming predominantly follows verb_noun pattern (create_client, get_project, list_tasks), though exceptions like analyze_project_profitability, health_check, and server_status break the pattern, causing minor inconsistency.
25 tools is on the higher side but well-justified given the multiple domain entities (clients, projects, tasks, service orders, purchase orders, catalogs) plus utility tools. The count is reasonable for the scope.
Basic CRUD is present for clients and projects, but missing for other entities: no create for purchase orders, no update for service orders, and no delete operations for any entity. These gaps hinder full workflow coverage.