Sign in to read the documentation
This documentation is for Corporater staff. Sign in with your Corporater work account, the same one your Claude connector uses.
Claude, connected to your Corporater environments. What it does, how to get access, how to work with it, and every tool it has.
This documentation is for Corporater staff. Sign in with your Corporater work account, the same one your Claude connector uses.
The Corporater MCP connects Claude to Corporater. It gives Claude tools to read and configure a Corporater BMP environment, and a knowledge base of Extended documentation, tested patterns and known pitfalls to work from. You describe the change in plain language; Claude looks up what it needs, previews the change and builds it.
Template ids, aliases and property ids come from your environment, not from guesswork.
Every change runs as a preview first. Nothing is saved to Corporater until you confirm.
Each call uses your own BMP login, so changes carry your name in Corporater and in the audit trail.
For DEV, TEST and DEMO environments. Production changes follow the normal release process and never go through the Corporater MCP.
From a change request to a configuration built in DEV and transferred to TEST.
Captions are built into the video.
The Corporater MCP is a standard connector in the Corporater Claude account. There is nothing to install and no API key to request. Setup takes about five minutes.
In the Claude desktop app or at claude.ai. A personal Claude account does not include the Corporater connector.
Open Settings → Connectors, find Corporater in the list and click Connect.
Use your Corporater work account and your usual MFA. There is no separate password for the Corporater MCP.
On My environments, paste the address of each Corporater environment you work on, enter your BMP username and password, and choose Save and test. Mark the one you use most as the default.
The password goes straight to the Corporater MCP server and is stored encrypted. It never passes through a chat.
Start a new chat and ask:
Claude replies with the environment it reached and the BMP username it works as.
Working in Claude Code? Add the server once, then run /mcp inside Claude Code and sign in with Microsoft.
claude mcp add --transport http --scope user corporater https://mcp.corporater.dev/mcpDescribe the outcome you want, as you would to a colleague who knows Corporater well. Claude chooses the tools. Every change follows the same four steps.
Claude finds the real templates, classes and property ids in your environment.
It runs the change without saving and shows you what would happen.
Once you agree, it runs the change again and saves it.
It reads the result back to confirm the change landed.
In claude.ai and the desktop app, every chat uses your default environment unless you name another one. If you work on more than one, name it in the request, for example "on presales-demo, list the risk templates". Asking Claude to switch environment changes your default for all of your chats, not only the current one. You can set the default on My environments.
For larger tasks Claude follows step-by-step skills: dashboards, custom visualisations, Word reports, modules, forms, access policies, compliance frameworks and more. If Claude takes a long way round, name the skill, for example "use the create-dashboard skill", or ask "which skills do you have?".
You do not call these yourself. Claude picks them from your request. The list comes straight from the server, so it always matches the current release.
Loading the tool list…