get_dataverse_team - Retrieve team metadata and details

update_dataverse_team - Update team properties and settings

delete_dataverse_team - Delete teams

list_dataverse_teams - List teams with filtering options

add_members_to_team - Add users as team members

remove_members_from_team - Remove users from teams

get_team_members - Retrieve all members of a team

convert_owner_team_to_access_team - Convert owner teams to access teams

create_dataverse_businessunit - Create new business units with comprehensive address and contact information
get_dataverse_businessunit - Retrieve business unit metadata and details
update_dataverse_businessunit - Update business unit properties, addresses, and settings
delete_dataverse_businessunit - Delete business units
list_dataverse_businessunits - List business units with filtering and sorting options
get_businessunit_hierarchy - Retrieve the hierarchical structure of business units
set_businessunit_parent - Change the parent business unit in the hierarchy
get_businessunit_users - Get users associated with a business unit (with subsidiary option)
get_businessunit_teams - Get teams associated with a business unit (with subsidiary option)

export_solution_schema - Export solution schema to JSON file including tables, columns, and global option sets. Supports filtering by customization prefix to export only solution-specific entities. Note: Relationship export is not yet implemented.

generate_webapi_call - Generate complete WebAPI calls for Dataverse operations including URLs, headers, and request bodies. Supports all major operations (retrieve, create, update, delete, associate, disassociate, actions, functions) with OData query options and provides output in multiple formats (HTTP, cURL, JavaScript fetch).

generate_powerpages_webapi_call - Generate PowerPages-specific WebAPI calls using the /_api/[logicalEntityName] format. Includes request verification token handling, authentication context, React component examples, and PowerPages-specific features for SPA development.

Solution-Based Architecture

The MCP server implements enterprise-grade solution management following Microsoft Dataverse best practices.

Professional Schema Naming: Uses publisher-based customization prefixes
Solution Association: All schema changes are automatically associated with the active solution
ALM Support: Enables proper solution packaging and deployment across environments
Persistent Context: Solution context survives server restarts via .mcp-dataverse file
Enterprise Governance: Supports multiple publishers and solutions with proper isolation

Create Publisher: Define your organization's customization prefix
Create Solution: Link solution to publisher for schema organization
Set Context: Activate solution for subsequent operations
Create Schema: All tables, columns, and option sets use the publisher's prefix automatically
Deploy: Export solution for deployment to other environments

Categories