Claude Code plugin and channel

With the DoiT channel for Claude Code, Claude tells you about a new cost anomaly or cloud provider incident while you work, in the session you already have open. You do not have to watch a dashboard or switch tools: the event arrives in the conversation, and you can ask Claude to find out what drove the cost, which resources are responsible, or whether an incident affects the services you run. Claude answers with your Cloud Intelligence data through the MCP server tools.

This is useful when you want to:

• Learn about a cost spike while you are still working on the code or infrastructure that may have caused it.

• Go from an alert to its cause in one place, without copying an anomaly ID between tools.

• Know about a cloud provider incident before you start debugging a problem that is not yours.

Note

Channels are a Claude Code research preview. The channel may change as the preview evolves. See Channels in the Claude Code documentation.

How it works

The setup has two parts, and you need both:

• DoiT tools: The DoiT Cloud Intelligence plugin, or the remote connector, gives Claude the MCP server tools. You sign in with your DoiT account in the browser.

• DoiT channel: The DoiT Cloud Intelligence Channel plugin runs a small local process that checks Cloud Intelligence for new cost anomalies and active cloud incidents, and sends Claude a short event for each new one. It adds no tools of its own.

An event contains a fixed sentence and identifiers only, such as the anomaly or incident ID, severity, platform, and service. Titles, descriptions, and other free text stay in Cloud Intelligence until Claude fetches them with a tool.

Required permissions

• The tools run with the permissions of the DoiT account you sign in with. See Required permissions.

• The channel uses a personal API token and can see the anomalies and incidents that token can read.

• To start the channel without the development flag on a Claude Team or Enterprise plan, an organization owner must allow the channel.

Prerequisites

• Claude Code installed and signed in with a claude.ai account. Channels are not available when Claude Code is signed in with an API key or through a cloud provider.

• Node.js 20 or later. The channel plugin uses npx to run @doitintl/doit-mcp-server and pins the package version for you.

Set up the tools and the channel

Step 1: Create an API token

In the DoiT console, create a personal API token as described in API tokens, and copy it. You enter it in step 4. Create a token for this purpose so that you can revoke it without affecting other integrations.

Step 2: Install the DoiT tools

If Claude Code already lists the DoiT MCP server tools, for example because you added the remote connector, skip this step.

1. In a terminal, add the marketplace and install the plugin:

   claude plugin marketplace add doitintl/doit-mcp-skills
   claude plugin install doit-mcp@doit-mcp-skills

   The plugin is also listed in the Claude plugin directory as DoiT Cloud Intelligence.

2. Start Claude Code, run /mcp, select the DoiT server, and authorize it with your DoiT account in the browser.

3. To check the tools, ask a question such as Show me this month's cost anomalies.

Step 3: Install the channel plugin

In a terminal, add the marketplace and install the channel plugin:

claude plugin marketplace add doitintl/doit-mcp-server
claude plugin install doit@doitintl

By default the plugin is installed for your user and loads in every Claude Code session on your machine. To limit it to one project, run the install command from that project's folder and add --scope project.

Step 4: Configure the channel

1. In Claude Code, run /plugin configure doit@doitintl.

2. Set the options:

   • DoiT API key: The personal API token from step 1. Claude Code stores it in your operating system's credential store.

   • Events: The event kinds to send to the session, as a comma-separated list of anomalies and incidents. The default is both.

   • Poll interval (seconds): How often the plugin checks for new events. The default is 300 and the minimum is 60.

3. Exit Claude Code so that the next session starts the channel with these values.

Step 5: Start a session with the channel

Events arrive only in sessions that you start with the channel. Which command you use depends on whether your organization has allowed the channel:

• If your organization has allowed the channel, start Claude Code with:

  claude --channels plugin:doit@doitintl

• Otherwise, use the development flag. Claude Code asks you to confirm each time you start a session this way:

  claude --dangerously-load-development-channels plugin:doit@doitintl

Step 6: Check that it works

1. When the session starts, Claude Code shows a notice that channel messages from plugin:doit@doitintl are enabled for the session.

2. Run /mcp. The list shows plugin:doit:doit as connected, with no tools, and the DoiT tools from the plugin or connector you set up in step 2.

3. Leave the session open. When a new anomaly or incident appears in Cloud Intelligence, Claude receives an event such as DoiT detected a new cost anomaly and can look it up. Then ask, for example:

   • What drove this anomaly, and which resources are responsible?

   • Is this incident affecting any of the services we use?

The channel reports only what appears after the session starts, so a new session stays quiet until something new happens.

Allow the channel in your organization

The channel plugin is not on Anthropic's default channel allowlist. On Claude Team and Enterprise plans, an organization owner enables channels and lists the plugin in the managed settings:

{
  "channelsEnabled": true,
  "allowedChannelPlugins": [{ "marketplace": "doitintl", "plugin": "doit" }]
}

allowedChannelPlugins replaces the default list, so include any other channel plugins your organization uses. See Enterprise controls in the Claude Code documentation for where to set these values.

Update, pause, or remove the channel

• To get a newer version, run claude plugin update doit@doitintl.

• To pause the channel without removing it, run claude plugin disable doit@doitintl, and claude plugin enable doit@doitintl to turn it back on. A session started without the channel flag receives no events, but the plugin still checks for them while it is enabled.

• To remove it, run claude plugin uninstall doit@doitintl, and revoke the API token in the DoiT console if you no longer need it.

Limitations

• Events arrive only while a Claude Code session is open. Anomalies and incidents that appear while no session is running are not replayed later; use anomaly notifications for alerts that must always reach you.

• Only new items produce an event. Changes to an existing anomaly or incident, such as a status update, do not.

• The channel plugin checks for events by polling the DoiT API at the poll interval, in every session the plugin is loaded into. An event can therefore arrive up to one interval after the item appears.

• The channel runs as a local process in Claude Code. Claude on the web, desktop, and mobile do not support it.

Troubleshooting

• No tools appear: Run /mcp in Claude Code and authorize the DoiT server.

• Tools work but no events arrive: The channel plugin is not installed or its API key is not set, the session was not started with one of the commands in step 5, or nothing new has appeared since the session started.

• Claude Code says the channel is not allowed: Your organization has not allowed the channel. Use the development flag, or ask an organization owner to allow it.

• Events arrive but Claude cannot look them up: The channel plugin has no tools. Install the DoiT Cloud Intelligence plugin or add the remote connector, and sign in.

• Tools appear twice: The MCP server is configured more than once, for example as both the plugin and the remote connector. Disable one of them.

For other issues with the MCP server, see Troubleshooting.