DataverseMCPServer

DataverseMCPServer

3.4

If you are the rightful owner of DataverseMCPServer and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.

Dataverse MCP Chatbot is a lightweight HTTP wrapper around a Model Context Protocol (MCP) server for Microsoft Power Platform/Dataverse, providing a REST endpoint and a simple HTML chatbot UI.

The Dataverse MCP Chatbot is designed to facilitate interaction with Microsoft Power Platform/Dataverse through a Model Context Protocol (MCP) server. It provides a RESTful interface via the `/invoke` endpoint, allowing users to perform various operations using natural language queries. The project includes a simple HTML chatbot UI that interprets user queries and routes them to the appropriate MCP tool. This setup is particularly useful for developers and users who need to interact with Dataverse entities and records without delving into complex API calls. The server is built using Node.js and Express, with CORS support for seamless integration with front-end applications. Configuration is managed through environment variables, ensuring secure handling of credentials and other sensitive information.

Features

  • MCP Tools: Supports 8 core MCP operations including entity overview, metadata fetching, attribute listing, and record querying.
  • Natural-Language Front End: HTML + JavaScript UI that parses free-text questions and invokes the correct MCP tool.
  • Environment Configuration: Uses environment variables for all Power Platform credentials.
  • Express + CORS: Simple HTTP server for integration with any front-end.

Tools

  1. use-powerplatform-prompt

    Entity overview, attribute details, query templates, relationship maps.

  2. get-entity-metadata

    Fetch metadata for an entity.

  3. get-entity-attributes

    List all attributes of an entity.

  4. get-entity-attribute

    Retrieve a specific attribute definition.

  5. get-entity-relationships

    One-to-many and many-to-many relationships.

  6. get-global-option-set

    Global option set definitions.

  7. get-record

    Fetch a record by GUID.

  8. query-records

    OData-filtered record queries.