dataverse

This MCP server provides tools to manage Dataverse schemas, including creating and updating custom tables, columns, relationships, and option sets via the Dataverse Web API. It also offers a WebAPI Call Generator to produce ready-to-use HTTP requests, cURL commands, and JavaScript snippets for common Dataverse operations, plus PowerPages-specific WebAPI generation and configuration management. Use this server when you need a programmatic way to model and deploy Dataverse schemas, automate solution management, and generate reproducible API calls for integration and debugging. The server emphasizes a solution-based approach with persistent context, security role and team management, and comprehensive error handling to support enterprise deployments.

Prerequisites:

• Node.js (LTS) and npm installed on your machine
• Access to a Dataverse environment (with appropriate credentials)

Installation steps:

1. Install the MCP server via npx (no local install required):
   • Run: npx -y mwhesse-dataverse-mcp
2. If you prefer a persistent local setup, you can install the package globally and run it from a script:
   • Run: npm install -g mwhesse-dataverse-mcp
   • Then start the server with: mcp-dataverse-server
3. Configure environment variables as needed for Dataverse authentication and environment details (see additional notes for examples).

Note: The MCP server expects to connect to a Dataverse environment using OAuth2 or Web API credentials. Ensure you have the required credentials and permissions before starting the server.

Environment variables you may need:

• DATAVERSE_TENANT_ID: Your Azure AD tenant ID
• DATAVERSE_CLIENT_ID: OAuth2 client ID
• DATAVERSE_CLIENT_SECRET: OAuth2 client secret
• DATAVERSE_ENV_URL: Dataverse Web API endpoint (e.g., https://yourorg.api.crm.dynamics.com)
• MCP_LOG_LEVEL: Logging verbosity (e.g., info, debug, warn)

Configuration tips:

• Use the WebAPI Call Generator to quickly produce HTTP requests for common operations like create_table, add_columns, or create_relationships.
• The solution-based workflow helps ensure all changes are versioned and can be deployed across environments.
• If you run into authentication errors, double-check the OAuth scopes and the configured redirect/return URLs in your Azure app registration.
• For PowerPages integrations, enable the PowerPages generator and verify the /_api/[entity] endpoints align with your site configuration.