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
      D
      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
      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
      21 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
      21 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.6/5.0

    Scored across 23 tools

    Disambiguation4/5

    Each tool targets a distinct resource and action (records, entities, attributes, keys, option sets, relationships, solutions, actions/functions), and the two invoke_* tools are cleanly separated by HTTP verb (POST action vs GET function). A few adjacent metadata tools (add/update/delete_attribute, get_entity_schema) sit close together, but descriptions make the boundaries clear.

    Naming Consistency5/5

    Every tool follows a strict verb_noun snake_case pattern (get_record, create_record, update_record, delete_record, add_attribute, list_entity_keys, update_picklist_option, invoke_action, etc.). No mixed conventions or stray verbs.

    Tool Count4/5

    23 tools is on the heavier side of the ideal range, but Dataverse's surface (record CRUD, metadata CRUD, option sets, alternate keys, relationships, actions/functions) is genuinely broad, so each tool earns its place. Slightly more than strictly needed but well-scoped.

    Completeness4/5

    Strong coverage: full record CRUD, entity/attribute create+update+delete, option set full CRUD, alternate key add/list/delete, plus invoke_action/invoke_function escape hatches. Gaps like entity update/delete and relationship deletion exist, but the generic invoke_* tools let agents work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources