OpsBeacon python client library to interact with the OpsBeacon API
Connect Opsbeacon to Claude, Cursor or any other MCP client and it stops being a tab you switch to. OpsBeacon python client library to interact with the OpsBeacon API. The opsbeacon mcp server is what makes that connection.
A comprehensive Python SDK for interacting with the OpsBeacon API, including support for command execution, MCP (Model Context Protocol) triggers, policy management, and more.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Commands — The Commands tool exposed by this serverConnections — The Connections tool exposed by this serverUsers — The Users tool exposed by this serverGroups — The Groups tool exposed by this serverFiles — The Files tool exposed by this serverConnection — Connect using the URL and token from trigger creation: URL: https://api.console.opsbeacon.com/trigger/ws/{workspaceId}/mcp/{triggerId}/Configuration is passed through the environment: OPSBEACON_API_DOMAIN, OPSBEACON_API_TOKEN, YOUR_API_TOKEN, YOUR_MCP_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
The server ships on PyPI as opsbeacon, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Opsbeacon's toolset — Commands, Connections, Users and 3 more — is a fair guide to whether it matches your workflow. It is maintained by Cihan Sahin; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Commands | The Commands tool exposed by this server. |
| Connections | The Connections tool exposed by this server. |
| Users | The Users tool exposed by this server. |
| Groups | The Groups tool exposed by this server. |
| Files | The Files tool exposed by this server. |
| Connection | Connect using the URL and token from trigger creation: URL: https://api.console.opsbeacon.com/trigger/ws/{workspaceId}/mcp/{triggerId}/ Authorization: Bearer YOUR_MCP_TOKEN |
{
"mcpServers": {
"opsbeacon": {
"command": "uvx",
"args": ["opsbeacon"],
"env": {
"OPSBEACON_API_DOMAIN": "your-value",
"OPSBEACON_API_TOKEN": "your-value",
"YOUR_API_TOKEN": "your-value",
"YOUR_MCP_TOKEN": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| OPSBEACON_API_DOMAIN | Configuration value read at startup. | Optional |
| OPSBEACON_API_TOKEN | Credential the server authenticates with. | Yes |
| YOUR_API_TOKEN | Credential the server authenticates with. | Yes |
| YOUR_MCP_TOKEN | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.