Diagrid Catalyst MCP server

catalyst-ai

Build and operate Diagrid Catalyst by prompting — Dapr Workflows, Durable Agents, and the running system.

Verified end to end in Claude Code — installs in under 5 seconds, every skill registers, and a real Catalyst question fires the right skill and gets a grounded answer. In Codex and GitHub Copilot the install and every skill are verified, and Codex is confirmed to put them in front of the model; neither has yet answered a Catalyst question here, for reasons that are nothing to do with the skills.

Early release. The skills drive Catalyst through the remote Catalyst MCP server:

you add the server and sign in once. The one exception is an app tunnel, which lets

Catalyst call into a process on your machine. No MCP tool opens one, so

catalyst-app-tunnels installs the Diagrid CLI and uses it for that alone. Read What works today for what is and is not available

over MCP yet.

Install

Claude Code

claude plugin marketplace add diagridio/catalyst-ai
claude plugin install catalyst-ai@diagrid

Then check it landed — both commands, not just the second:

claude plugin list                           # expect Version: 0.7.0 or later
claude plugin details catalyst-ai@diagrid    # expect 12 skills

list reports the version you actually have. details reports the version the marketplace is offering, reading the installed copy only when the two agree — so on its own it can show you 12 skills while your session loads 11. If either looks wrong, jump to If your install is behind.

Then sign in to the Catalyst MCP server

The plugin also registers the Catalyst MCP server, https://mcp.cloud.r1.diagrid.io/mcp. It stays empty until you sign in once. In Claude Code, run /mcp, pick plugin:catalyst-ai:catalyst and complete the browser sign-in. There is no API key.

If you already added the server yourself with claude mcp add, remove that entry (claude mcp remove catalyst --scope user) once the plugin is installed. Otherwise you have two copies of every Catalyst tool.

The plugin requests the scopes catalyst:read catalyst:write offlineaccess. Without offlineaccess there is no refresh token, so you sign in again each time the session expires. Write tools, such as catalyst_apply, are left out of the tool list entirely when your role is read-only or the sign-in did not grant write scope. If they are missing, sign in again and approve write access; if they are still missing, your role is read-only.

Check it worked by asking: "Who am I in Catalyst?" The answer comes from catalyst_whoami.

Connect other clients to the remote MCP server

Every client connects to the same remote server, https://mcp.cloud.r1.diagrid.io/mcp (the r1 is required), and signs in with OAuth in the browser. The authorization server has no dynamic registration, so each client uses its registered client ID: codex, copilot-cli, vscode or claude-code.

Each snippet below also sets an X-Catalyst-Plugin-Version header to the plugin version, which lets the server see which version of these instructions a client was set up from. It goes only on the MCP requests the client already makes. When you update the skills, update the header to match.

Install the skills for the client first (below), then:

Codex

codex mcp add catalyst --url https://mcp.cloud.r1.diagrid.io/mcp --oauth-client-id codex
codex mcp login catalyst

codex mcp add has no header flag, so add this to ~/.codex/config.toml under the server it just wrote:

[mcp_servers.catalyst.http_headers]
X-Catalyst-Plugin-Version = "0.7.3"

GitHub Copilot CLI

copilot mcp add has no client-ID flag, so add the server and then set oauthClientId in ~/.copilot/mcp-config.json:

Shortened. The full README is on GitHub.