concert-operate-mcp
OfficialEvents: Create new events.
Alerts: Create, retrieve, update, bulk-update, comment, and manage insights (create, retrieve, delete) for alerts, with filtering by severity and other fields.
Incidents: Retrieve, update, comment, and view timelines for incidents.
Policies: Full CRUD (create, read, update/patch, replace/put, delete), bulk-create, retrieve execution status and timeline.
Runbooks: Full CRUD, manage versions, references, statistics; execute and manage executions (list, get, update, delete).
Algorithms: List, get, register, and unregister algorithms.
Training: Manage training definitions (CRUD), start/monitor training and prechecks (start, stop, get status), manage trained model versions (list, get, delete).
Metering: Create and retrieve metering jobs, get job status/result, list resources, and get aggregate resource statistics.
User Preferences: Get, upsert, and delete preferences for the current user; admin operations for all users.
Automation Tools: Full CRUD for runbook automation tools.
UI Configuration: CRUD for UI menus, views, and visualization filters; bulk-delete filters; check name existence.
Topology UI Configuration: Backup and restore topology UI configuration.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@concert-operate-mcpList all active alerts with severity 5 or higher"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
concert-operate-mcp
An MCP (Model Context Protocol) server for IBM Concert Operate (formerly IBM Cloud Pak for AIOps). Connects any MCP-compatible AI assistant to your Concert Operate instance, exposing the full v2 REST API as callable tools.
Compatibility
Package version | Concert Operate version |
|
|
Related MCP server: openhab
Prerequisites
Node.js 18 or later
A running Concert Operate instance (Cloud Pak for AIOps)
Installation
Option A — npx (recommended, no install required)
Add the following to your MCP client config (e.g. mcp.json for Bob, .vscode/mcp.json for GitHub Copilot in VSCode (change "mcpServers" to "servers"), ~/.cursor/mcp.json for Cursor):
{
"mcpServers": {
"concert-operate": {
"command": "npx",
"args": ["-y", "concert-operate-mcp"],
"env": {
"CONCERT_BASE_URL": "https://your-instance.example.com",
"CONCERT_CPD_USER": "cpadmin",
"CONCERT_CPD_PASSWORD": "yourpassword"
}
}
}
}Option B — global install
npm install -g concert-operate-mcpThen use concert-operate-mcp as the command instead of npx:
{
"mcpServers": {
"concert-operate": {
"command": "concert-operate-mcp",
"args": [],
"env": {
"CONCERT_BASE_URL": "https://your-instance.example.com",
"CONCERT_CPD_USER": "cpadmin",
"CONCERT_CPD_PASSWORD": "yourpassword"
}
}
}
}Option C — build from source
git clone https://github.com/ibm-client-engineering/concert-operate-mcp
cd concert-operate-mcp
npm install
npm run buildThen point your MCP client at the absolute path to build/index.js.
Configuration
Environment variable | Required | Default | Description |
| ✅ | — | Base URL of your Concert Operate instance, e.g. |
| ✅ | — | Cloud Pak for Data username |
| ✅ | — | Cloud Pak for Data password |
| ❌ |
| Tenant ID. The default is the standard value shipped with every Concert Operate installation. Override only if your instance uses a custom tenant ID. |
Self-signed certificates
TechZone and many on-premises Concert Operate deployments use self-signed TLS certificates. The server automatically bypasses certificate verification (rejectUnauthorized: false), matching the behaviour of curl -k. If your instance has a valid trusted certificate this has no effect.
Token lifecycle
The server authenticates against the CPD platform auth endpoint (/icp4d-api/v1/authorize) on first use and caches the token for approximately 11 hours 45 minutes (proactive refresh before the ~12-hour CPD expiry). If a 401 is received mid-session the token is force-refreshed and the request is automatically retried once.
Available tools
Events
Tool | Description |
| Create a new event |
Alerts
Tool | Description |
| Create a new alert |
| List alerts, optionally filtered (e.g. |
| Get a single alert by ID |
| Update fields on an alert |
| Update all alerts matching a filter |
| Get timeline entries for an alert |
| Add a comment to an alert timeline |
| Get insights for an alert |
| Add an insight to an alert |
| Get a specific insight by ID and type |
| Delete a specific insight |
Incidents
Tool | Description |
| List all incidents |
| Get a single incident by ID |
| Update fields on an incident |
| Get timeline entries for an incident |
| Add a comment to an incident timeline |
Policies
Tool | Description |
| List all policies |
| Get a policy by ID |
| Create a new policy |
| Create multiple policies in one request |
| Partially update a policy (PATCH) |
| Replace a policy entirely (PUT) |
| Delete a policy |
| Get execution status for a policy |
| Get timeline entries for a policy |
Runbooks
Tool | Description |
| List all runbooks |
| Get a runbook by ID |
| Create a new runbook |
| Update a runbook |
| Delete a runbook |
| List all versions of a runbook |
| Get a specific runbook version |
| Get references for a runbook |
| Get execution statistics for a runbook |
| Execute a runbook |
| List all executions for a runbook |
| Get a specific execution by instance ID |
| Update a runbook execution |
| Delete a runbook execution record |
Algorithms
Tool | Description |
| List all registered algorithms |
| Get an algorithm by name |
| Register a new algorithm |
| Unregister an algorithm |
Training
Tool | Description |
| List all training definitions |
| Get a training definition by name |
| Create a training definition |
| Update a training definition |
| Delete a training definition |
| Get the latest training run status |
| Start a training run |
| Get the latest precheck status |
| Start a precheck run |
| Stop the current precheck run |
| List all trained model versions |
| Get a trained model version |
| Delete a trained model version |
Metering
Tool | Description |
| Create a metering job |
| Get a metering job |
| Get metering job status |
| Get metering job result |
| List metering resources |
| Get aggregate resource stats for a date range |
User Preferences
Tool | Description |
| Get current user preferences |
| Create or update a preference |
| Delete a preference |
| (Admin) Get all user preferences |
| (Admin) Get preferences for a user |
| (Admin) Get a specific preference for a user |
| (Admin) Create or update a preference for a user |
| (Admin) Delete a preference for a user |
| (Admin) Delete all preferences for a user |
Automation Tools
Tool | Description |
| List all runbook automation tools |
| Get an automation tool |
| Create an automation tool |
| Update an automation tool |
| Delete an automation tool |
UI — Menus, Views, Visualization Filters
Tool | Description |
| Menu CRUD |
| View CRUD |
| Visualization filter CRUD |
Topology UI Configuration
Tool | Description |
| Backup topology UI configuration |
| Restore topology UI configuration |
Testing
An end-to-end test scenario is available in docs/test-scenario.md. It walks through the full AIOps lifecycle — event ingestion → alert correlation → story creation → enrichment → resolution — using prompt-by-prompt instructions for Bob. No tool knowledge required; Bob calls the correct MCP tools automatically.
Development
git clone https://github.com/ibm-client-engineering/concert-operate-mcp
cd concert-operate-mcp
npm install
npm run build # compiles src/index.ts → build/index.js
npm run dev # watch modeTo test locally with the MCP Inspector:
$env:CONCERT_BASE_URL="https://your-instance.example.com"
$env:CONCERT_CPD_USER="cpadmin"
$env:CONCERT_CPD_PASSWORD="yourpassword"
npx @modelcontextprotocol/inspector node build/index.jsTesting directly inside Bob (IBM Bob IDE)
The repo ships a .bob/mcp.json.sample template. Copy it to .bob/mcp.json, fill in your credentials, and Bob will register the local build as an MCP server automatically when you open the folder.
.bob/mcp.json is listed in .gitignore so it is never tracked by git — your credentials stay local.
First-time setup:
Copy the sample and fill in your credentials:
On Windows (PowerShell):
Copy-Item .bob/mcp.json.sample .bob/mcp.jsonOn macOS / Linux:
cp .bob/mcp.json.sample .bob/mcp.jsonThen open
.bob/mcp.jsonand replace the three placeholder values:CONCERT_BASE_URL→ your Concert Operate base URLCONCERT_CPD_USER→ your CPD usernameCONCERT_CPD_PASSWORD→ your CPD password
Run
npm run build(ornpm run devfor watch mode) — Bob connects to the freshly compiledbuild/index.js.Open the MCP panel in Bob and confirm the
concert-operateserver is listed with all its tools.
After any source change, re-run npm run build. The server restarts automatically on the next tool call.
Troubleshooting the Bob MCP connection
1. Confirm the build exists
Test-Path build/index.jsls build/index.jsIf missing, run npm run build first.
2. Run the server manually
This is the fastest way to see a raw error. The server speaks stdio, so a clean start will block silently waiting for input — that's correct. Any output before that is an error.
On Windows (PowerShell):
$env:CONCERT_BASE_URL="https://your-instance.example.com"
$env:CONCERT_CPD_USER="cpadmin"
$env:CONCERT_CPD_PASSWORD="yourpassword"
node build/index.jsOn macOS / Linux:
CONCERT_BASE_URL="https://your-instance.example.com" \
CONCERT_CPD_USER="cpadmin" \
CONCERT_CPD_PASSWORD="yourpassword" \
node build/index.js3. Check the Bob MCP logs
The quickest way is the Output panel: in Bob open View → Output and select IBM Bob MCP from the dropdown — this streams the live log.
To open the log files directly:
On Windows, the logs are under %APPDATA%\IBM Bob\logs\<session>\<window>\exthost\IBM.bob-code\. Open the two most relevant files from a terminal:
# List sessions newest-first to find the right <session> folder
Get-ChildItem "$env:APPDATA\IBM Bob\logs" | Sort-Object Name -Descending | Select-Object -First 3 Name
# Open the MCP log for the most recent session (replace <session> and <window>)
code "$env:APPDATA\IBM Bob\logs\<session>\<window>\exthost\IBM.bob-code\IBM Bob MCP.log"
code "$env:APPDATA\IBM Bob\logs\<session>\mcpGateway.log"On macOS, the equivalent paths are under ~/Library/Application Support/IBM Bob/logs/ with the same structure:
# List sessions newest-first
ls -t ~/Library/Application\ Support/IBM\ Bob/logs/ | head -3
# Open the MCP log (replace <session> and <window>)
open ~/Library/Application\ Support/IBM\ Bob/logs/<session>/<window>/exthost/IBM.bob-code/IBM\ Bob\ MCP.logReleasing a new version
Make and test your changes
Run
npm run buildto confirm it compiles cleanlyBump the version and create the git tag:
npm version patch # bug fix: 1.0.0 → 1.0.1 npm version minor # new endpoints: 1.0.0 → 1.1.0 npm version major # breaking change (new Concert major): 1.0.0 → 2.0.0Push the commit and tag:
git push --follow-tags
The GitHub Actions workflow triggers automatically on the tag push, builds the package, and publishes it to npm. No manual npm publish needed.
Version compatibility
npm package major | Concert Operate version |
1.x | 5.1.x |
When a new major Concert Operate version introduces breaking API changes, bump the npm major version and update this table.
Contributing
Issues and pull requests welcome. When adding tools for a new API version, please update the compatibility table above.
License
MIT
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityCmaintenanceA generic MCP server that dynamically converts OpenAPI-defined REST APIs into tools for LLMs like Claude. It supports multiple authentication methods and transport protocols, enabling seamless interaction with any OpenAPI-compliant API.17MIT
- AlicenseCqualityAmaintenanceMCP server for OpenHAB v5+ that exposes the entire REST API as tools for AI models, enabling complete control over items, things, rules, persistence, and semantic model.257MIT
- FlicenseBqualityDmaintenanceMCP server for IBM Watson Orchestrate (WXO). Manage tools, agents, connections, flows, and execute tools from Cursor, VS Code Copilot, Claude Desktop, Antigravity, Windsurf, or the WxO Builder extension.35
- Alicense-qualityCmaintenanceA Model Context Protocol server that connects AI agents to IBM Concert, enabling autonomous workflow health monitoring, incident diagnosis, auto-remediation, CVE triage, and Slack alerting through natural language.Apache 2.0
Related MCP Connectors
MCP server for Pentest-Tools.com: run scans, manage findings and reports via your preffered LLM.
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
MCP server exposing the Backtest360 engine API as tools for AI agents.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ibm-client-engineering/concert-operate-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server