Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Manage Microsoft 365 in natural language with PnP PowerShell and author PnP PowerShell scripts.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
PNP_MCP_READONLY, PNP_MCP_ALLOW_SETUPWhich app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"pnp-powershell": {
"command": "dnx",
"args": [
"PnP.PowerShell.MCPServer",
"--yes"
],
"env": {
"PNP_MCP_READONLY": "your-value",
"PNP_MCP_ALLOW_SETUP": "your-value"
}
}
}
}Run this in your terminal
claude mcp add pnp-powershell --env PNP_MCP_READONLY=your-value --env PNP_MCP_ALLOW_SETUP=your-value -- dnx PnP.PowerShell.MCPServer --yesFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"pnp-powershell": {
"command": "dnx",
"args": [
"PnP.PowerShell.MCPServer",
"--yes"
],
"env": {
"PNP_MCP_READONLY": "your-value",
"PNP_MCP_ALLOW_SETUP": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"pnp-powershell": {
"type": "stdio",
"command": "dnx",
"args": [
"PnP.PowerShell.MCPServer",
"--yes"
],
"env": {
"PNP_MCP_READONLY": "your-value",
"PNP_MCP_ALLOW_SETUP": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
PNP_MCP_READONLY envPNP_MCP_ALLOW_SETUP envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account pnp, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.7-beta) reached the registry 32 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need .NET on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, zanadir
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Find what a repository's CI is missing, and which security checks cannot fail the build.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
This MCP server allows the use of natural language to run PnP PowerShell commands and to author complex PnP PowerShell scripts. It may handle complex prompts that are executed as a chain of PnP PowerShell cmdlets that try to fulfill the user's request, and it can search the community's PnP Script Samples library for ready-to-adapt scripts. This way you can manage many different areas of Microsoft 365 — SharePoint Online, Microsoft Teams, Entra ID, OneDrive, Planner, Power Platform, Microsoft 365 Groups, taxonomy, search, and tenant administration — straight from your MCP client, and use it as a jump-start for writing your own automation scripts.
pwsh) installed and available on PATHPnP.PowerShell module installed: Install-Module -Name PnP.PowerShell -Scope CurrentUser -Force -AllowClobber
This MCP server shells out to the locally installed PnP PowerShell module — it does not do any authentication for you. Authenticate first using Connect-PnPOnline (see Best Practices for the recommended auth methods), then the MCP server will reuse the same PnP PowerShell connection context.
Local (stdio)The one-click buttons above register the server under the name
pnp-powershelland point it at thepnp-powershell-mcp-servercommand, so install the tool first (below) — otherwise the client will register a server it cannot start.
dotnet tool install --global PnP.PowerShell.MCPServer --prerelease
This installs a self-contained, native AOT executable named pnp-powershell-mcp-server on your PATH. Supported platforms: Windows (x64, arm64), macOS (arm64, x64) and Linux (x64, arm64, musl x64).
To update an existing install:
dotnet tool update --global PnP.PowerShell.MCPServer --prerelease
Hitting `Version of package PnP.PowerShell.MCPServer. is not found in NuGet feeds`?
This tool ships as a small wrapper package plus one package per platform, and that error means the platform package for your machine was never published for that version. It affects
0.1.1-betaand earlier — install0.1.3-betaor later, or build and run from source. Maintainers: see RELEASING.md.
MCP: Add Server.Command (stdio) as the server type. pnp-powershell-mcp-server
PnP PowerShell MCP Server).As a result, you should have the following configuration in your .vscode/mcp.json file:
{
"servers": { "PnP PowerShell MCP Server": { "type": "stdio", "command": "pnp-powershell-mcp-server" } } }
Now when you open the GitHub Copilot chat in VS Code, you should be able to select the PnP PowerShell MCP Server from the list of available MCP servers and start using it to manage Microsoft 365 using natural language. In the prompt specify that "Using PnP PowerShell, I want you to..." and GitHub Copilot Agent will use the MCP server to execute your request.
If you are using GitHub Copilot CLI, you may add the PnP PowerShell MCP server to Copilot by doing the following:
copilot
/mcp add
pnp-powershell-mcp-serverLocalpnp-powershell-mcp-serverAfter that click Ctrl+S to save and q to exit the MCP form. You can now use the PnP PowerShell MCP server in GitHub Copilot CLI, e.g. "Using PnP PowerShell, I want you to...".
claude mcp add pnp-powershell --scope user -- pnp-powershell-mcp-server
--scope user makes the server available in every project; drop it to register it for the current project only. Check it was picked up with claude mcp list.
Ctrl + ,).claude_desktop_config.json in your favorite text editor and add: {
"mcpServers": { "PnP-PowerShell": { "command": "pnp-powershell-mcp-server" } } }
Note: On Windows, Claude doesn't exit when you close the window — it keeps running in the background. Find it in the system tray, right-click and select Quit to exit completely.
Agent settings option.Tools & MCP tab and click on New MCP server.mcp.json configuration as follows: {
"mcpServers": { "PnP PowerShell MCP Server": { "type": "stdio", "command": "pnp-powershell-mcp-server" } } }
PnP PowerShell MCP Server in the Tools & MCP tab and wait for the tools to load.The below use cases are only a few examples of how you may use this MCP server. It is capable of handling many different tasks, so feel free to experiment and manage Microsoft 365 using natural language.
prompt:
Add a new list to this site with title 'awesome ducks'. Then add new columns to that list including them in the default view. The first should be a text description column and the second one should be a user column. Then add 3 items to this list with some funny jokes about ducks added in the description column and my user in the user column.
prompt:
Create a new Team on Teams with name 'Awesome Ducks' and in the General channel add a welcome post.
prompt:
I need a PnP PowerShell script that exports all SharePoint list items to a CSV file — find a community sample and adapt it for the 'Documents' list on my site.
prompt:
Do I have a script in my samples that reports inactive sites? If so, run it for the last 90 days.
Then, once a new script works:
Save that script to my samples as inactive-sites-report.
See Your own script samples for the one-time setup.
prompt:
Can you check if I have a Power Automate flow called 'HoursReportingReminder' and if so disable it?
| Tool | Description |
|---|---|
| pnp_search_commands | Finds which cmdlet does a job. Scores a compiled-in index of every cmdlet — name, verb, noun, synopsis, description, parameters and examples — with field-weighted BM25, so a plain-language question like "add a column to a list" finds Add-PnPField. Answers entirely in process: no pwsh, no session and no network, so it works on a machine that is not set up yet. Returns structured content alongside the text, and states the module version it was indexed from. |
| pnp_get_command_docs | Gets the reference documentation for one named cmdlet — syntax, parameters, parameter sets and examples — preceded by links to both the raw markdown source of its documentation page and the rendered HTML page. The markdown is the same content for a fraction of the tokens. |
| pnp_run_command | Runs PnP PowerShell against the connected tenant and returns the result. Runs in a persistent session, so a Connect-PnPOnline connection is reused across calls. Destructive commands require confirmation first. A result set too large for the output cap is summarised and paged rather than truncated. |
| pnp_get_result_page | Returns the next page of a result set pnp_run_command summarised. Pages over rows already fetched, so it costs nothing against the tenant and returns exactly the rows the original command saw. |
| pnp_get_connection_status | Checks whether the session is signed in, to which site, and as which account. |
| pnp_diagnose_connection | Checks everything that has to be true before a command can run: pwsh on PATH, the PnP.PowerShell module, what connection the session holds, and — when it holds none — which app registration, persisted login or certificate this machine can actually sign in with. Every failing check names its cause and the exact next command, with no placeholder left in it where the facts can fill one in. Pass targetUrl to get the command for a specific site. The pwsh, module and auth-material checks need no tenant and no network, so it still works on a machine that is not set up yet; once a connection exists it also inspects that connection, which asks PnP for a Graph token and so reaches Entra ID. |
| pnp_reset_session | Ends a session and its PnP connection. Use it to sign out, switch accounts, or recover a session that has stopped responding. |
| pnp_get_best_practices | Returns best practices for using PnP PowerShell via this MCP server. Takes an optional section (workflow, docs, sessions, config, readonly, output, destructive, auth, execution, patterns) to retrieve one topic instead of the whole guide, which keeps the response small. |
| pnp_search_script_samples | Lists community PnP Script Samples, plus your own from PNP_SCRIPT_SAMPLES_PATH, matching a keyword — titles, descriptions and links, no code. The community index is compiled into the server, so it needs no network; a Git URL in PNP_SCRIPT_SAMPLES_PATH is
Only the beginning is shown; read the rest in the repo