Skip to content
Dataverse Ops MCP

Security

Architecture: local stdio, no hosted service

Section titled “Architecture: local stdio, no hosted service”

Dataverse Ops MCP is an npm package that your MCP host (Claude Desktop, Claude Code, …) spawns as a local child process and talks to over stdio.

  • There is no hosted service and the server opens no network ports.
  • The only network connections the server makes are outbound to your own Dataverse environment (Web API v9.2) and to Microsoft Entra ID for tokens.
  • Access tokens are cached in memory only and are never logged or written to disk. Secrets are supplied by you via environment variables.

Data residency

Section titled “Data residency”

All Dataverse data — trace logs, async job details, import job XML, performance metrics — is fetched directly from your tenant to your machine and returned to your MCP host. It never transits any third-party server of ours. What your AI assistant then does with tool results is governed by the assistant you chose to run.

The single exception is license validation, and it is opt-in: if you set LICENSE_KEY, the server validates it against our licensing worker. That request carries only the license key and a hashed org identifier — never org data, never tokens, never query results. Without LICENSE_KEY set, the server makes no calls to us at all (pro tools simply reply with an upgrade notice; free tools are never blocked).

No telemetry by default

Section titled “No telemetry by default”

The server sends no telemetry, crash reports, or usage analytics. There is no opt-out to configure because there is nothing to opt out of.

(This documentation website uses Cloudflare Web Analytics — cookie-free page counts on the website only; the MCP server itself phones home to nothing.)

Credentials

Section titled “Credentials”
  • Client credentials mode: DATAVERSE_URL, CLIENT_ID, CLIENT_SECRET, TENANT_ID. Scope the app user’s security role to the read privileges the tools need (plug-in trace logs, system jobs, import jobs, step registrations) rather than full admin.
  • DefaultAzureCredential fallback: omit the client secret trio and the server uses your ambient Azure identity (Azure CLI login, managed identity, etc.) via @azure/identity.

Questions or disclosures: support@simplesmoothsafe.com.