A
licenseNot graded
qualityC
maintenanceA self-hosted MCP server that enables AI assistants to inspect and manage Microsoft Power Automate cloud flows and Dataverse records locally, using your own Azure identity.
MIT
Dataverse Plugin MCP
Related Servers
Alternatives to Dataverse Plugin MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceA 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.3811143MIT
- 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-
- AlicenseNot gradedqualityCmaintenanceThe most complete MCP server for Microsoft Dataverse.17714MIT
- AlicenseBqualityCmaintenanceMCP server for Microsoft Fabric REST APIs that enables data engineers and analysts to manage Fabric components using AI assistants.21921AGPL 3.0
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables interaction with Microsoft Dynamics 365 CRM from Claude Desktop, allowing users to retrieve, create, and update CRM data through natural language.521MIT
TDQS
A3.9/5.0
Scored across 24 tools
Disambiguation5/5
Each tool targets a distinct resource and action: environments, projects, builds, registrations, steps, images, assemblies, packages, available messages, logs, and tracing. Even similar delete/update/list tools are clearly differentiated by their object type (image vs assembly vs package, etc.).
Naming Consistency5/5
All tool names follow a consistent verb_noun snake_case pattern (e.g., list_steps, create_step, update_step, delete_step, toggle_step, configure_tracing). Compound verbs like open_registration_tool and push_plugin_update still adhere to the same structural pattern, maintaining predictability throughout.
Tool Count4/5
At 24 tools, the set is slightly above the typical 3-15 well-scoped range, but each tool serves a distinct purpose within the plugin development lifecycle. The count is justified by the broad domain coverage, from project creation to deployment and diagnostics, without redundant or trivial tools.
Completeness5/5
The tool set covers the full lifecycle: project scaffolding, build, registration (with a manual PRT step workaround), CRUD for steps and images, environment management, secure configuration, tracing, and a comprehensive xray_assembly report. There are no obvious dead ends or missing critical operations for the plugin development workflow.
Maintenance
ActivitySlowing
ResponsivenessNo issues