v1.0.0 · 32 Free tools · 32 Pro-only tools · 64 total

Talk to Dataverse

Use DVQR from Copilot without leaving the investigation model behind.

DV Quick Run's extension-owned Local MCP server exposes the same metadata, query, relationship, Business Path and investigation capabilities used by the rest of the product. Ask in natural language; DVQR keeps the environment, capability, bounds and evidence semantics in application code.

64 MCP tools94 guided promptsWorkspace-owned lifecycleLocal-first evidence
Local MCP in the DV Quick Run Hub
DV Quick Run v1.0.0 Hub showing Local MCP status and investigation starting points

What it delivers

Start conversationally. Stay inside DVQR's evidence-backed workflows.

Understand metadata

Search tables, columns, lookups, relationships and business capability anchors from the active Dataverse environment.

Generate and run bounded queries

Move from natural-language intent to metadata-aware OData and bounded GET execution without turning the assistant into an unrestricted Dataverse administrator.

Explore relationships

Discover candidate paths, test real routes, preserve exact relationship identity and continue through Guided Traversal.

Use Managed Business Paths

Save reviewed routes explicitly, Reverify metadata separately, Runtime Verify the exact saved path from a real source record, and keep BusinessPreferred under human governance.

Inspect Operational Profile + DVQR Score

Use the same canonical profile and calibrated score surfaced by the editor experience.

Discover Custom APIs

Explain, compare, preview and—where eligible—execute supported Custom APIs through the governed preview/confirmation lifecycle.

Run Professional Investigations · Pro

Persist subject and intent, acquire bounded evidence, assess readiness and preserve evidence-backed investigation continuity.

Generate bounded Mini RCA · Pro

Synthesize already-acquired evidence without allowing the explanation layer to silently reacquire or remediate.

Setup

Enable once. Ask when you need it.

Local MCP is optional. Select the environment DVQR should expose, enable the server once for the workspace, sign in to the tenant through Azure CLI when required, then use GitHub Copilot Chat.

  1. 1Select the Dataverse environment
  2. 2Run DV Quick Run: Enable Local MCP Server
  3. 3Sign in to the environment tenant with Azure CLI when required
  4. 4Enable the DV Quick Run MCP tools in Copilot Chat
  5. 5Ask a Dataverse question or open the Prompt Library for a guided start
Start with the task you have
DV Quick Run v1.0.0 Welcome page showing ways to start

Free vs Pro MCP

The capability boundary is visible.

Free is a meaningful Dataverse investigation foundation. Pro adds persisted investigation continuity and deeper evidence workflows; it does not buy stronger truth or weaker safety.

Free tools

32

Metadata, bounded querying, relationship intelligence, Operational Profile, Business Paths and eligible governed Custom API workflows.

Pro-only tools

32

Persisted Professional Investigation, advanced evidence, readiness, Mini RCA, comparison, timeline and investigation continuity.

Total with Pro

64

The complete v1 Local MCP catalogue.

Free truth = Pro truth · Free safety = Pro safety

Custom API Intelligence

Understand the operation before asking DVQR to run it.

Capability Explorer and Local MCP share the same metadata-backed Custom API model. Eligible execution remains preview-first, confirmation-bound and evidence-backed.

Actions vs Functions
Bound vs unbound
Parameter readiness
Preview-confirmed execution
Capability Explorer · v1.0.0
DV Quick Run v1.0.0 Capability Explorer

Prompt playground

Start with the outcome, not the tool name.

The built-in Prompt Library contains 94 guided prompts—69 Free and 25 Pro. These examples show the range from orientation through managed investigation.

Using DV Quick Run, show me what I can investigate in this Dataverse environment and recommend where to start.
Get the current live Operational Profile and DVQR Score for contact and explain the evidence behind the score.
Find metadata-valid relationship paths from account to task and tell me which routes still require runtime validation.
Start a DVQR managed investigation for why the expected related record is missing and assess readiness before generating Mini RCA.

What Local MCP does not become

A conversational surface, not unrestricted Dataverse authority.

No generic DELETE

DVQR does not expose broad delete authority through Local MCP.

No hidden remediation

Investigation recommendations do not silently become operational mutations.

No autonomous RCA

Mini RCA explains already-acquired evidence; it does not independently acquire or remediate.

No model-owned environment

The configured/current DVQR environment remains the execution boundary.