Plugin

The plugin gives your coding agent read-only production context while it reviews code, prepares a deployment, investigates an incident, or explains architecture. It combines Graph MCP with an Agent Skill that teaches the agent how to gather and interpret that evidence.

The package follows Agent Plugins 1.0.0 and connects to Graph MCP over MCP 2026-07-28. It contains no API token, project identifier, authorization header, or database name.

Install

Choose your coding agent below. Compatible Agent Plugins clients install the package directly; clients such as Claude Code load the same Agent Skill and Graph MCP connection separately. During the first Graph MCP connection, sign in to Anyshift, select the project the agent may read, and approve access. The client stores the resulting credentials.

Codex
VS Code
Cursor
Claude Code

Update Codex CLI before installing:

codex plugin marketplace add anyshift-io/agent-plugin --ref main
codex plugin add agent-plugin@anyshift
codex mcp add agent-plugin --url https://graph.anyshift.io/mcp

The last command starts the Graph MCP OAuth flow. Sign in, select the Anyshift project the agent may read, and start a new Codex task so the skill and MCP tools load together.

Codex currently requires the explicit codex mcp add command because installing a plugin-owned remote MCP entry does not start its OAuth flow automatically.

VS Code supports the Agent Plugins 1.0.0 package directly. Update VS Code, make sure GitHub Copilot Chat is enabled, and check that chat.plugins.enabled is set to true.

Open the Command Palette:
- macOS: Shift+Command+P
- Windows and Linux: Ctrl+Shift+P
Run Chat: Install Plugin From Source.

Paste the public repository URL:

https://github.com/anyshift-io/agent-plugin

Review the source and select Install.
Follow the browser prompt when VS Code starts Graph MCP.

VS Code discovers the packaged plugin.json, mcp.json, and agent-plugin skill. You do not need to copy the skill or add the MCP endpoint separately.To verify the installation:

Run Chat: Open Customizations and confirm that agent-plugin is enabled under Plugins.
Check that agent-plugin appears under Skills.
Run MCP: List Servers and confirm that agent-plugin is running.

Invoke the skill directly in Copilot Chat when you want to force the evidence workflow:

/agent-plugin:agent-plugin

Before I deploy checkout-api, resolve the exact resource, inspect its direct
dependencies and transitive blast radius, and correlate relevant changes
from the last 24 hours. Separate graph evidence from inference.

Copilot can also select the skill automatically when a request concerns production dependencies, deployments, incidents, recent changes, or blast radius. See the VS Code Agent Plugins guide for plugin management and updates.

Cursor supports the Agent Plugins standard without package changes. Install the current package into Cursor’s local plugin directory:

git clone --depth 1 \
  https://github.com/anyshift-io/agent-plugin.git \
  ~/.cursor/plugins/local/agent-plugin

Run Developer: Reload Window, then open Customize and confirm that the plugin, agent-plugin skill, and Graph MCP server are enabled. Follow the browser prompt to authorize the Anyshift project.The package loads its skill and remote MCP configuration together. Do not also add the same Graph MCP endpoint to ~/.cursor/mcp.json, because that registers the server twice.For a centrally managed rollout, a Cursor administrator can import the same GitHub repository into a Team Marketplace and distribute it at user or project scope. See Cursor’s Plugins guide for Agent Plugin installation, management, and team distribution.

If local plugin loading is unavailable in your Cursor deployment, use the standalone Graph MCP configuration in the troubleshooting section. That fallback provides the tools but does not install the agent-plugin skill.

Claude Code loads the Agent Skill and remote MCP connection separately. Clone the current package and expose its skill to Claude Code:

git clone --depth 1 \
  https://github.com/anyshift-io/agent-plugin.git \
  ~/.claude/agent-plugin
mkdir -p ~/.claude/skills
ln -s ~/.claude/agent-plugin/skills/agent-plugin \
  ~/.claude/skills/agent-plugin

claude mcp add --transport http --scope user \
  agent-plugin https://graph.anyshift.io/mcp
claude mcp list

Start Claude Code and run /mcp to complete browser authentication. Start a new session after installation, then invoke /agent-plugin or ask a production-impact question and let Claude select the skill automatically.See Anthropic’s guides for Agent Skills and remote MCP servers.

End-to-end production verification covers Codex against the current tool surface, including exposure, and Cursor against the preceding six-tool surface. For other clients, confirm authentication, discovery of the expected tools, one authenticated read-only call, and uninstall behavior against the version your team deploys.

What the plugin gives your agent

Use the plugin to:

review a code or infrastructure change against current production dependencies;
identify direct dependencies and bounded blast radius before a deployment;
trace public-edge exposure paths, observed controls, and explicit evidence gaps;
correlate recent changes with topology during an incident;
explain how a repository fits into the current production architecture; and
produce focused post-deployment checks from observed graph evidence.

Graph MCP supplies deterministic, read-only tools for resource identity, exposure, dependencies, blast radius, recent changes, operational impact, and constrained graph queries. The packaged skill teaches the agent to choose the narrowest tool, combine topology with recent changes, and separate observed evidence from inference and unknowns. This is not an autonomous SRE agent or an incident-response loop. For Annie’s full AI SRE investigation workflow, use Annie Remote MCP.

Try it

After installation, ask the agent to combine the code in your workspace with production evidence:

Review my current changes. Identify the production resources they affect using
Anyshift, then summarize direct dependencies, bounded blast radius, recent
related changes, post-deployment checks, and explicit unknowns.

Other useful starting points:

Before I change this database schema, identify the services that currently
depend on this datastore.

Explain how this repository fits into the current production architecture:
runtime resources, direct dependencies, datastores, and evidence timestamps.

More clients

Kiro

Kiro supports Agent Skills and remote HTTP MCP servers with browser OAuth. Configure the two components separately.First, open Agent Steering & Skills in the Kiro panel, select Import a skill, choose GitHub, and paste:

https://github.com/anyshift-io/agent-plugin/tree/main/skills/agent-plugin

Then run Kiro: Open user MCP config (JSON) from the Command Palette and merge this entry into ~/.kiro/settings/mcp.json:

{
  "mcpServers": {
    "agent-plugin": {
      "url": "https://graph.anyshift.io/mcp",
      "disabled": false
    }
  }
}

Save the file. Kiro reconnects automatically and opens the Anyshift authorization page when Graph MCP requests OAuth. Verify the connection in the MCP servers panel, then invoke /agent-plugin or ask a production-impact question.See Kiro’s Agent Skills and MCP configuration guides.

Grok Build

This setup is for the xAI Grok Build coding agent, not the consumer Grok chat or bot.

grok plugin install anyshift-io/agent-plugin
grok plugin install anyshift-io/agent-plugin --trust
grok mcp add --transport http agent-plugin \
  https://graph.anyshift.io/mcp
grok inspect

Review the source and the capabilities Grok displays before using --trust. Start a new Grok session and complete browser OAuth on the first Graph MCP use. The skill is available as /agent-plugin. Run grok mcp doctor agent-plugin if the server does not connect.See the Grok Build guides for plugins and MCP servers.

GitHub Copilot CLI

Install the repository from inside a GitHub Copilot CLI session:

/plugins install anyshift-io/agent-plugin
/mcp show agent-plugin

If the server is listed as needs-auth, start the browser flow:

/mcp auth agent-plugin

If your Copilot version installs the skill but does not load the portable MCP entry, add the endpoint explicitly from your shell:

copilot mcp add --transport http agent-plugin \
  https://graph.anyshift.io/mcp

Start a new session after installation. Invoke /agent-plugin/agent-plugin, or ask Copilot to inspect production impact and let it select the skill automatically.See GitHub’s guides for Copilot plugins and MCP servers.

OpenClaw

OpenClaw loads the skill and remote MCP connection separately. Clone the current package, then install its skill for all local agents:

git clone --depth 1 \
  https://github.com/anyshift-io/agent-plugin.git
openclaw skills install \
  ./agent-plugin/skills/agent-plugin \
  --global

openclaw mcp add agent-plugin \
  --url https://graph.anyshift.io/mcp \
  --transport streamable-http \
  --auth oauth
openclaw mcp login agent-plugin
openclaw mcp doctor agent-plugin --probe

Restart the relevant agent or Gateway if it was already running. Run openclaw skills list to confirm the skill loaded, then invoke /agent-plugin or ask the agent for production evidence.See OpenClaw’s Skills and MCP guides.

Hermes

Hermes supports Agent Skills and OAuth-authenticated HTTP MCP servers, but loads the two components separately. Clone the current package into a stable location:

git clone --depth 1 \
  https://github.com/anyshift-io/agent-plugin.git \
  ~/.hermes/agent-plugin

Merge these entries into ~/.hermes/config.yaml:

skills:
  external_dirs:
    - ~/.hermes/agent-plugin/skills

mcp_servers:
  agent-plugin:
    url: "https://graph.anyshift.io/mcp"
    auth: oauth

Complete OAuth and verify the connection from a fresh terminal:

hermes mcp login agent-plugin
hermes mcp test agent-plugin

Start hermes chat and invoke /agent-plugin, or ask a production-impact question and let Hermes load the skill automatically.See Hermes’ Skills and MCP guides.

Other Agent Plugin clients

Load the public repository root in a client that supports Agent Plugins and the streamable-http MCP transport:

https://github.com/anyshift-io/agent-plugin

The client should discover plugin.json, mcp.json, and the packaged skill. Treat the client as unverified until you have tested installation, OAuth, discovery of the expected tools, one authenticated call, and uninstall behavior with the exact version you deploy.

Verify the connection

A complete installation has all four of these signals:

The agent-plugin skill is visible to the agent.
agent-plugin is connected and authenticated.
The client discovers resolve_resource, get_dependencies, get_blast_radius, get_recent_changes, get_operational_impact, and query_graph.
A read-only request returns project-scoped evidence with an evidence timestamp.

Use this focused verification prompt:

Use Anyshift to resolve checkout-api. Report the selected resource type and
evidence timestamp, then list its direct dependencies. Do not infer missing
relationships.

Manage access and updates

Use your client’s plugin manager to update or remove the package. For manual Git checkouts, run git pull --ff-only in the package directory, then restart the client.
Start a new agent session after installing or updating so the current skill and MCP tools are loaded.
Keep only one Graph MCP registration per client. Installing the package and configuring the same endpoint manually can create duplicate tools and separate OAuth state.
View or revoke authorized MCP connections from your Anyshift profile page under Authorized Apps.

Troubleshooting

OAuth callback returns 400

Start authentication again from the MCP client and use the newly generated browser page. OAuth callback URLs are tied to the active client attempt; an old page can no longer complete a later connection.

The browser does not open

Copy the fresh authorization URL shown by the client into a browser where you can sign in to Anyshift. This is common when the agent client runs over SSH or in a remote development environment. Keep the client process running until authorization completes.

The skill is installed but Graph tools are missing

Confirm that agent-plugin is enabled, complete OAuth, and start a new agent session. If the server still does not appear, use the client’s MCP diagnostics to inspect its connection state.

Graph tools appear twice

Remove the standalone MCP entry when the Agent Plugin already supplies Graph MCP. Keep the package installation if you want both the tools and the agent-plugin skill.

Cursor cannot load the local plugin

Use Cursor’s standalone Graph MCP entry as a fallback:

cursor --add-mcp '{"name":"agent-plugin","url":"https://graph.anyshift.io/mcp"}'

Complete browser OAuth and start a new Agent chat. This fallback provides the Graph tools but does not install the agent-plugin skill.

Authorize a different Anyshift project

Revoke the current connection from Authorized Apps on your Anyshift profile, then start authentication again from the client and select the intended project.

The package source, releases, validation instructions, and compatibility evidence are available in anyshift-io/agent-plugin.

Get Started

Product

Manage

Install

What the plugin gives your agent

Try it

More clients

Verify the connection

Manage access and updates

Troubleshooting

​Install

​What the plugin gives your agent

​Try it

​More clients

​Verify the connection

​Manage access and updates

​Troubleshooting

Install

What the plugin gives your agent

Try it

More clients

Verify the connection

Manage access and updates

Troubleshooting