Agent Plugins Overview

CloudPeek publishes one Agent Plugin, Vulnerability Intelligence, for anonymous CVE and CWE lookup. Its portable package connects an external AI client, such as Claude Code, Cursor, GitHub Copilot or Codex, to the public service and supplies three workflow skills.

For incident triage and investigation in your tenant, connect the client directly to your own CloudPeek installation's MCP gateway. That gateway supplies the CloudPeek tools and two incident skills; the old shared-hosted CloudPeek plugin is retired.

The Vulnerability Intelligence package lives in the public Cloud-Peek/agent-plugin repository.

Note

Agent Plugins are for connecting an existing client to CloudPeek. If instead you want to build an agent that runs inside CloudPeek, with its own tools and approval gates, start with the Agent SDK Overview.

Choose a connection

Your CloudPeek installationVulnerability Intelligence
JobTriage and investigate incidents in your own tenantLook up CVEs and CWEs from a public indexed corpus
Published pluginRetired — connect to your own installationYes
Endpoint<your-installation-origin>/mcphttps://mcp.cloudpeek.ai/vulnerability/mcp
AccessSign in to your CloudPeek tenantAnonymous, no account
Sees your dataYes, scoped to your CloudPeek userNo
Needs a CloudPeek subscriptionYesNo
Skills2, served by your installation's gateway3, bundled with the plugin

The shared hosted CloudPeek endpoint has been retired: a published plugin manifest can only name one address, and your installation's address is yours. The MCP gateway and both of its skills still ship with every installation — see Connect an MCP client in the installation guide for connection and origin enrolment instructions.

The two connections can be used together: install Vulnerability Intelligence to understand a CVE, then connect to your CloudPeek installation to investigate its impact on your estate. There is no second published plugin to install.

The Vulnerability Intelligence page provides plugin installation instructions. The installation guide explains the installation-specific endpoint and origin enrolment.

What a plugin actually contains

The published plugin root is a portable Agent Plugins 1.0.0 package:

  • plugin.json — the manifest: name, version, description, author, licence.
  • mcp.json — the MCP server the plugin connects to, over Streamable HTTP. Exactly one server per plugin, defined in exactly one place.
  • skills/ — Markdown workflow instructions the agent loads on demand.

There is no build step and nothing to compile. Your client reads mcp.json, connects to the hosted endpoint, and loads the skills when a request matches one.

Tools come from the server, skills come from the package

This split is worth understanding, because it explains what changes when.

The tools live on the hosted MCP endpoint. When CloudPeek adds or changes a tool, your client picks it up on its next connection: there is nothing to reinstall.

The skills ship inside the plugin package. They are the workflow knowledge, which order to call tools in, what counts as enough evidence, what a useful answer looks like. Updating those means refreshing the plugin from the marketplace.

Compatible clients

Every client on the compatible clients list can load the Vulnerability Intelligence plugin as-is: GitHub Copilot, VS Code, Cursor, ChatGPT and Codex, Kiro, Grok Bot, OpenClaw, NanoClaw and Hermes Agent, alongside Claude Code.

Some clients also read a catalogue manifest for presentation, giving them a display name, an icon and starter prompts. Those are shipped alongside the portable package as additions rather than replacements, so a client that reads none of them still installs the plugin from the root manifest. Every one of them points at the single mcp.json.

Any other MCP client works too, as long as it speaks the Streamable HTTP transport. The linked service pages give the raw configuration for that case.

Authentication, in one paragraph

The Vulnerability Intelligence plugin is anonymous: no account, no sign-in and no token to manage. Your CloudPeek installation's MCP gateway reaches real tenant incident data, so it requires sign-in; what the agent can see and do is scoped to your CloudPeek user and enforced server-side. Each linked page explains its access model.

Important

The published plugin package contains no credentials. Nothing you install from the repository carries a secret, and nothing you configure should put one in a file you commit.

Where to go next

© 2026 CloudPeek. Agentic AI for high-consequence security operations.