Conductor MCP Server

Exposes a CognOS agent system as a machine-readable graph. Full system snapshot with one tool call.

Local serverstdio

What is the Conductor MCP server?

If you already use Conductor, the conductor mcp server is the piece that lets your assistant work with it directly. Exposes a CognOS agent system as a machine-readable graph. Full system snapshot with one tool call.

What the server does

An MCP server that exposes a CognOS agent system as a machine-readable JSON graph. The conductor (Claude) calls a single tool and gets an immediate full system snapshot.

Installation

conductor-graph-mcp on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • get_agent_graph — Full graph — nodes + edges + summary
  • get_edges — Only edges (communication flow)
  • get_blocked_nodes — Shortcut: what is broken right now?

Credentials and setup notes

Configuration is passed through the environment: COGNOS_BASE_URL, COGNOS_API_KEY. 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.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

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. Conductor's toolset — get_agent_graph, get_edges, get_blocked_nodes — is a fair guide to whether it matches your workflow. It is maintained by base76-research-lab; 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.

Available tools

ToolWhat it does
get_agent_graphFull graph — nodes + edges + summary
get_edgesOnly edges (communication flow)
get_blocked_nodesShortcut: what is broken right now?

How to install the Conductor MCP server

Or with `uvx`:

```json
{
  "mcpServers": {
    "cognos-graph": {
      "command": "uvx",
      "args": ["conductor-graph-mcp"],
      "env": {
        "COGNOS_BASE_URL": "http://127.0.0.1:8788",
        "COGNOS_API_KEY": "your-key"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
COGNOS_BASE_URLEndpoint or connection string the server talks to.Yes
COGNOS_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Conductor to get agent graph.
  • Use Conductor to get edges.
  • Use Conductor to get blocked nodes.

Frequently asked questions

It connects Conductor to MCP-compatible AI assistants such as Claude and Cursor, exposing 3 tools (get_agent_graph, get_edges, get_blocked_nodes) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Conductor directly.