Skill

Process

Produces business-readable summaries of Dynamics 365 records or sets using schema metadata for targeted queries on entities, relationships, and picklists. For account reports or opportunity pipelines.

database

npx claudepluginhub nickmeron/dataverse-mcp-server

Tool Access

This skill is limited to using the following tools:

mcp__dynamics365__list_environmentsmcp__dynamics365__select_environmentmcp__dynamics365__get_entity_detailsmcp__dynamics365__get_entity_attributesmcp__dynamics365__get_entity_relationshipsmcp__dynamics365__get_picklist_optionsmcp__dynamics365__get_recordmcp__dynamics365__query_recordsmcp__dynamics365__execute_fetchxml

Preview

The user wants a summary or report from Dynamics 365.

SKILL.md

Similar Skills

Dynamics 365 Automation

Automates Dynamics 365 CRM operations: create, update, retrieve, list leads, accounts, contacts, opportunities, sales orders, invoices, cases via Web API tools.

superpowers

dv-python-sdk

Query, create, update, delete, and bulk-import Dataverse records using official Python SDK. Supports CSV import, data profiling, and Jupyter notebook patterns.

dataverse

crm-prospect-mining

Mines high-value prospects from CRM lost/churned stages by cross-referencing LinkedIn data, Apify company scrapes, domain filters, and comms history for re-engagement.

4 files

sales

Stats

Stars6

Forks2

Last CommitMar 25, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

<fetch aggregate="true"> <entity name="opportunity"> <attribute name="stepname" alias="stage" groupby="true"/> <attribute name="estimatedvalue" alias="total_value" aggregate="sum"/> <attribute name="opportunityid" alias="count" aggregate="count"/> <filter> <condition attribute="statecode" operator="eq" value="0"/> </filter> </entity> </fetch>

The user wants a summary or report from Dynamics 365.

Argument provided: $ARGUMENTS

Process

Select environment — call list_environments, ask the user, call select_environment.
Understand the schema — before querying data, call get_entity_attributes and get_entity_relationships to know:
- What fields exist and their types
- Which fields are lookups (so you can $expand them for readable names)
- What option sets mean (so you can translate integer values to labels)
Determine the summary type:
- Single record → get_record with $select and $expand for related data
- Set of records / pipeline view → query_records or execute_fetchxml for aggregates
For account summaries, fetch:
- Account details (name, industry, revenue, owner) via get_record
- Open opportunities via query_records on opportunities filtered by _parentaccountid_value
- Open cases via query_records on incidents filtered by _customerid_value
- Resolve statecode and statuscode labels via get_picklist_options
For pipeline summaries, use FetchXML:

<fetch aggregate="true">
  <entity name="opportunity">
    <attribute name="stepname" alias="stage" groupby="true"/>
    <attribute name="estimatedvalue" alias="total_value" aggregate="sum"/>
    <attribute name="opportunityid" alias="count" aggregate="count"/>
    <filter>
      <condition attribute="statecode" operator="eq" value="0"/>
    </filter>
  </entity>
</fetch>

Present as a clean business summary with tables and clear formatting — never raw JSON. Translate all integer option set values to their labels.