Powerplatform MCP Server

Most developer tooling work still happens through a UI a human drives. Powerplatform MCP MCP server moves it into the conversation instead. PowerPlatform Model Context Protocol server.

The short version

A Model Context Protocol (MCP) server and standalone CLI for querying and configuring PowerPlatform / Dataverse environments. Supports multiple environments, entity metadata, records, plugins, flows, solutions, workflows, business rules, security roles, custom APIs, web resources, and more — including write operations for automated environment setup.

The tools it exposes

The server publishes 14 tools. What each one is for:

• get-custom-apis — List Custom API definitions
• get-custom-api — Get a Custom API by unique name
• create-custom-api — Create a Custom API definition
• get-custom-api-response-properties — List response properties
• create-custom-api-response-property — Create a response property
• get-custom-api-request-parameters — List request parameters
• create-custom-api-request-parameter — Create a request parameter
• Entity — The Entity tool exposed by this server
• Records — The Records tool exposed by this server
• Plugins — The Plugins tool exposed by this server
• Solutions — The Solutions tool exposed by this server
• Configuration — The Configuration tool exposed by this server

What it needs from you

Configuration is passed through the environment: POWERPLATFORM_DEV_URL, POWERPLATFORM_DEV_CLIENT_ID, POWERPLATFORM_DEV_CLIENT_SECRET, POWERPLATFORM_DEV_TENANT_ID, POWERPLATFORM_UAT_URL, POWERPLATFORM_UAT_CLIENT_ID, POWERPLATFORM_UAT_CLIENT_SECRET, POWERPLATFORM_UAT_TENANT_ID. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Getting it running

powerplatform-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Powerplatform MCP's toolset — get-custom-apis, get-custom-api, create-custom-api and 11 more — is a fair guide to whether it matches your workflow. It is maintained by michsob; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Powerplatform MCP.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.