Dataverse MCP Server
Related Servers
Alternatives to Dataverse MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables comprehensive management of Microsoft Dataverse environments, including schema operations for tables, columns, and relationships through the Dataverse Web API. It also supports solution management, security role configuration, and the generation of WebAPI calls and Mermaid ERD diagrams.MIT
- AlicenseNot gradedqualityDmaintenanceEnables comprehensive schema and solution management for Microsoft Dataverse, including operations for tables, columns, relationships, and security roles via the Dataverse Web API. It also supports PowerPages configuration, automated WebAPI call generation, and schema visualization through Mermaid ERD diagrams.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI applications to interact with Power BI through the Model Context Protocol, supporting comprehensive API operations including data retrieval and management.-
- FlicenseNot gradedqualityDmaintenanceEnables CRUD operations and schema exploration on Microsoft Dataverse databases using service principal authentication. It allows users to query records with OData filters, manage table entries, and retrieve metadata through a standardized MCP interface.-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables CRUD operations and querying on Microsoft Dataverse through natural language.6 npmMIT
- AlicenseBqualityDmaintenanceA Model Context Protocol (MCP) server that provides intelligent access to PowerPlatform/Dataverse entities and records. This tool offers context-aware assistance, entity exploration and metadata access.3869 npm44MIT
TDQS
Scored across 71 tools
Most tools have distinct purposes targeting specific Dataverse components (e.g., business units, tables, columns, roles, teams) with clear CRUD operations, but some overlap exists in management tools like 'generate_webapi_call' and 'generate_powerpages_webapi_call' which could cause confusion in selection. Overall, descriptions help differentiate, but the high count increases complexity.
Tool names follow a highly consistent verb_noun pattern throughout, such as 'create_dataverse_table', 'get_dataverse_column', 'list_dataverse_solutions', and 'update_dataverse_role'. There are no deviations in style, making it predictable and easy to understand the action and target resource.
With 71 tools, the count is excessive for a single server, making it overwhelming and difficult for agents to navigate. While Dataverse is a complex platform, this many tools suggests poor scoping, likely leading to confusion and inefficiency in tool selection and usage.
The tool set provides comprehensive coverage for Dataverse administration, including full CRUD operations for all core components (tables, columns, relationships, roles, teams, business units, etc.), lifecycle management (e.g., set/clear solution context), and auxiliary functions like schema export and diagram generation. No obvious gaps are present for the domain.