The local ChangePilot MCP server runs as a process launched by your AI client and uses an API key. The hosted OAuth server is also available and offers more tools; use the remote MCP guide if your client supports it.
Before you start
You need Plus or an activated Plus trial with API access, an API key, Node.js 20 or later, and an AI client that supports local stdio MCP servers. Check your organisation's policy for using tenant information with the chosen AI provider.
Configure the client
Create an API key from the API page in the main navigation.
Open your AI client's MCP configuration.
Add a local server that runs npx with arguments -y and @changepilot/mcp-server.
Set the environment variable CHANGEPILOT_API_TOKEN to your key in the client's secure configuration.
Save the configuration and restart or reconnect the client as its documentation requires.
Check that the ChangePilot tools are available, then ask a small read-only question.
For Claude Code, the official project documents this command; replace the placeholder locally with your key:
claude mcp add changepilot --env CHANGEPILOT_API_TOKEN=cpat_YOUR_TOKEN -- npx -y @changepilot/mcp-server
Follow the official ChangePilot MCP setup guide for client-specific configuration and current supported tools. Avoid sharing command history that contains the key.
Try a useful first question
Ask “Find recent Teams Message Center changes with high admin impact, and include item IDs and links.” Then open the cited items to check the evidence. The current server provides read tools for Message Center, Roadmap and supporting metadata such as history and taxonomy.
The local server provides the twelve read-only Message Center, Roadmap and taxonomy tools described on the MCP Server page. Azure, watchlist, bookmark and personal-label tools are available through the hosted OAuth server. Local installation does not provide those hosted capabilities.
Understand the data path
The local server uses the key to retrieve authorised ChangePilot data. The AI client can pass retrieved content to its AI provider. Running the connector locally does not mean all retrieved information stays on the computer.
If tools do not load
Confirm that the client can run Node and npx, that it supports local MCP, and that the environment variable is available to the server process. Check authentication errors and the official guide before changing network or gateway settings.