Skip to main content
Glama
rededis

dataverse-mcp-server

by rededis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to dataverse-mcp-server

No user-submitted related servers found.

    Related Servers

    • xrm-mcp

      jukkan
      F
      license
      A
      quality
      C
      maintenance
      A 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.
      8
      19
      -

    • Dynamics MCP Server

      kavingas
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server to query Microsoft Dynamics 365 CRM records and support workflows using streamable HTTP transport.
      -

    • odatav4-mcp

      singlebarrel
      F
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for OData v4 endpoints, especially Microsoft Dataverse/Dynamics 365, enabling authentication, schema discovery, querying, CRUD, and more via natural language.
      -

    • Microsoft Business Central MCP

      knowall-ai
      A
      license
      A
      quality
      D
      maintenance
      Model Context Protocol (MCP) server for Microsoft Dynamics 365 Business Central. Provides AI assistants with direct access to Business Central data through properly formatted API v2.0 calls.
      6
      8 npm
      8
      MIT

    • Microsoft Business Central MCP

      EdwardHayes91
      A
      license
      B
      quality
      C
      maintenance
      MCP server for Microsoft Dynamics 365 Business Central, enabling AI assistants to perform CRUD operations, query data, and retrieve schemas via Business Central API v2.0.
      6
      8 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 23 tools

    Disambiguation5/5

    Every tool targets a distinct resource and action, from create_entity to invoke_function. The only overlapping pair, invoke_action and invoke_function, is clearly separated by HTTP verb and purpose. Descriptions for related tools (e.g., get_entity_schema vs get_picklist_options) explicitly direct usage.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in lower_snake_case (create_*, list_*, get_*, update_*, delete_*). The style is uniform throughout, with plural nouns only for list operations and singular for others, maintaining predictability.

    Tool Count4/5

    At 23 tools, the set is on the heavier side but justified by Dataverse's complexity (tables, attributes, keys, relationships, picklists, records, and custom API). Each tool addresses a distinct need, and the count is not excessive for a full-featured MCP server.

    Completeness4/5

    The surface covers essential CRUD for records and metadata operations for attributes, keys, picklists, and relationships. Missing pieces like entity update/delete or relationship listing/deletion are notable gaps, but they can be worked around via invoke_action/function or are intentionally omitted for safety.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources