jaj-dataverse-dev-mcp
Related Servers
Alternatives to jaj-dataverse-dev-mcp
No user-submitted related servers found.
Related Servers
- 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.-
- AlicenseAqualityAmaintenanceEnables AI agents to query, inspect, and manage Microsoft Dataverse records, metadata, schema, forms, views, and Power Platform environments via the Dataverse OData Web API.972MIT
- 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
- AlicenseAqualityDmaintenanceProvides intelligent access to PowerPlatform/Dataverse entities and records, enabling entity metadata exploration, OData querying, relationship mapping, and AI-assisted query building through MCP.8178 npmMIT
- 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
- FlicenseAqualityCmaintenanceA minimal MCP server that gives AI coding agents clean read and write access to Microsoft Dataverse environments via the Dataverse Web API v9.2. It works as a drop-in alternative to Microsoft's own MCP server, without requiring Copilot Credits or managed environments.819-
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: ping checks server availability, list_environments shows configured environments, whoami returns identity info, and dataverse_request handles arbitrary Dataverse API calls. There is no overlap or ambiguity, as the generic tool is explicitly scoped to the Dataverse Web API.
Tool names do not follow a consistent pattern. ping and whoami are single-word commands, list_environments uses verb_noun, and dataverse_request is a noun_noun combination. While readable, the mixed styles are not predictable.
With only 4 tools, the server is well-scoped for its purpose: a few helper tools plus one powerful generic execution tool. This is a reasonable and focused set, not too thin or bloated.
The dataverse_request tool can execute any Dataverse Web API request (CRUD, OData, functions, actions), providing full coverage of the domain. The auxiliary tools add environment and identity context, leaving no obvious gaps in functionality.