Skip to main content
Glama
Sign In
dataverse-mcp-server

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
      21
      -

    • 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
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for OData v4 endpoints, especially Microsoft Dataverse/Dynamics 365, enabling authentication, schema discovery, querying, CRUD, and more via natural language.
      MIT

    • Microsoft Business Central MCP

      knowall-ai
      A
      license
      A
      quality
      C
      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
      2,547 npm
      10
      MIT

    • Microsoft Business Central MCP

      EdwardHayes91
      A
      license
      B
      quality
      D
      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
      2,547 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

    B3.4/5.0

    Scored across 23 tools

    Disambiguation4/5

    Most tools are cleanly separated by resource + action (entity vs record vs attribute vs key vs picklist), and generic escape hatches (invoke_action vs invoke_function) are distinguished by POST/GET semantics. Minor overlap remains between get_entity_schema and get_picklist_options (schema dump already summarizes option sets), and create_entity vs create_record could briefly confuse newcomers to Dataverse terminology.

    Naming Consistency5/5

    Every tool follows a consistent snake_case verb_noun pattern (list_entities, create_record, update_attribute, delete_picklist_option, get_attribute_dependencies). The only deviation is 'query_records' using a different read verb, but it remains within the same convention and clearly signals a filter-based read versus a list.

    Tool Count4/5

    23 tools is on the heavy side but is justified by the genuinely broad domain: records, tables, columns, alternate keys, option sets, relationships, solutions, plus two escape hatches. There is little obvious redundancy, though the set is at the upper edge of comfortable before it becomes unwieldy.

    Completeness3/5

    Record CRUD and attribute/key/picklist lifecycles are largely covered, but there are notable gaps: relationships can be created but not listed or deleted, tables can be created but not updated or deleted, and solutions are read-only. Several delete operations (record, entity key, picklist option, attribute) are explicitly disabled for safety, which will leave agents at dead ends when cleanup is required.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Resources