Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

Related Servers

Alternatives to Dynamics 365 MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to query and maintain Microsoft Dataverse and Dynamics 365 Customer Engagement environments via MCP, with 84 tools for records, metadata, web resources, plugin registration, data model management, diagnostics/audit, solutions, and classic Ribbon customization.
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      A 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.
      38
      990 npm
      45
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Provides intelligent access to PowerPlatform/Dataverse entities and records, enabling entity metadata exploration, OData querying, relationship mapping, and AI-assisted query building through MCP.
      8
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to query, inspect, and manage Microsoft Dataverse records, metadata, schema, forms, views, and Power Platform environments via the Dataverse OData Web API.
      97
      74 PyPI
      3
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables interaction with Microsoft Dataverse and Dynamics 365 data through natural language, including CRUD operations, metadata exploration, and saved views.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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

    TDQS

    C2.8/5.0

    Scored across 167 tools

    Disambiguation2/5

    Large overlapping families make selection hard: prepare_form_candidate vs prepare_component_candidate vs prepare_form_node_candidate vs prepare_form_row_candidate vs prepare_composite_form_candidate, and capture_form_baseline vs capture_model_baseline vs capture_published_form_baseline vs capture_published_script_baseline all sound interchangeable without deep reading. Multiple publish paths (publish_sitemap, publish_appmodule, publish_model_table, publish_model_choices, publish_web_resource, publish_ribbon_solution, publish_isolated_release_component/table) and three record-write paths (update_existing_record, update_record_with_journal, upsert_record_by_key) require careful discrimination that descriptions only partly resolve.

    Naming Consistency3/5

    Casing is uniformly snake_case, which helps, but verb placement is mixed: most tools are verb_noun (create_model_column, get_model_key), while the plugin family inverts to noun_verb with a prefix (d365_plugin_assembly_inspect, d365_plugin_steps_query, d365_plugin_image_register, d365_plugin_step_update). A few tools also bundle a second action into the name (create_web_resource_and_publish, update_web_resource_and_publish), breaking the single-verb pattern.

    Tool Count1/5

    167 tools is an extreme mismatch for practical agent selection, spanning records, metadata, forms, solutions, ribbon, plugins, security, flows, audit, charts and templates. Even if the domain is genuinely broad, this volume guarantees tool-selection errors and makes the surface unmanageable without heavy external guidance.

    Completeness4/5

    Coverage of the Dynamics customization lifecycle is unusually thorough: metadata, forms/views, sitemap, solutions (export/import/verify), ribbon, plugin assemblies/steps/images, security, web resources, flows, notes, templates, records and audit/diagnostics all have supporting operations. Gaps exist on the destructive side of metadata (no delete_model_column, delete_model_table, or delete_model_relationship, and no web-resource delete), which agents would have to work around.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data