Skip to main content

MCP Installation

Centra MCP is released in two formats:

  • Option 1: MCPB bundle — One-click install connector plugin for Claude Desktop and other MCPB-aware agents.
  • Option 2: Command line tool via Homebrew — for Linux, macOS, and WSL.

First step: Create an API token​

Both formats connect with Centra through a Centra Integration API token. In Centra AMS → System → API Tokens:

  1. Create a new Integration dedicated to this Centra MCP installation. Do not reuse the token from another system or another Centra MCP install.
  2. Grant the token only the permission scopes you want the agent to have — the scopes decide exactly which tools the agent can and cannot use.

Start with a token that grants limited read only access to a non-production environment without any sensitive data at all. You can add more tokens for other environments later.

Install option 1: MCPB bundle​

One click install for Claude Desktop and any other agent that accepts MCPB bundles.

  1. Download centra-mcp.mcpb.
  2. Double-click on the file to open it in Claude Desktop (or your MCPB-aware agent of choice).
  3. Fill in the configuration form:
    • Centra Integration API URL — the full GraphQL endpoint, e.g. https://acme.centra.com/graphql or https://acme.centraqa.com/graphql
    • Centra API token — the token you created above
    • Allow write operations — off by default. Off = the agent can see data but not change it; on = the agent can make changes in Centra (potentially dangerous)
    • Allow production environment access — off by default. A production URL is refused until you turn this on — a second confirmation that you mean to operate on live data
    • I accept the Centra MCP Freeware License — required

Each .mcpb install is bound to a single Centra instance — install once per instance; each gets its own MCP server entry in the host. To update, download the new .mcpb and open it again.

Install option 2: CLI tool via Homebrew​

For macOS, Linux and WSL — terminal users and multi-instance workflows.

If you don't have Homebrew installed, install it first — see brew.sh.

Then type in the terminal:

brew tap centrahq/centra-mcp
brew trust --tap centrahq/centra-mcp
brew install centra-mcp

Then connect it to your Centra environment(s):

centra-mcp setup add acme --env qa --token YOUR_API_TOKEN

acme is the part before .centra.com or .centraqa.com in the URL when opening AMS. Use --env qa or --env prod to pick the environment type; add as many environments as you like — different brands, or prod and QA for the same brand. The first setup add on a machine shows a one-time confirmation of the license (--accept-license skips it for scripted installs).

Verify connectivity, then install into your AI assistant:

centra-mcp setup test
centra-mcp setup install-user claude-code

Supported targets: claude-code, claude-desktop, cursor, gemini (Gemini CLI), codex. install-user writes your user-global config (meaning it is available in all projects); install-project writes a config file into the current directory (meaning it is only available in that folder's project). centra-mcp gui opens a local web control panel for managing environments, permissions, and testing.

Getting going​

Centra has a very large data model, and the MCP that covers it is extensive. For the best results, use a frontier model with a context window of 1M tokens or more — large catalogs, order histories, and multi-step workflows all benefit from the agent being able to hold more of Centra in view at once.

Once Centra MCP is installed and enabled your agent should have access to Centra. Just ask it in human language:

Can you access Centra?

The agent should reply and tell you that it has access. The agent is aware of what Centra tools it has access to, so if you wonder what your agent can do in Centra, you can just ask it.

Last updated on