Plugin

​

Install

codex plugin marketplace add anyshift-io/agent-plugin --ref v0.3.0
codex plugin add agent-plugin@anyshift
codex mcp add agent-plugin --url https://api.anyshift.io/mcp/graph
codex mcp login agent-plugin

/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.

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

/plugin marketplace add anyshift-io/agent-plugin
/plugin install anyshift-graph@anyshift

​

What the plugin gives your agent

• 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.

​

Try it

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.

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

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

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

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

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

/mcp auth agent-plugin

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

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://api.anyshift.io/mcp/graph \
  --transport streamable-http \
  --auth oauth
openclaw mcp login agent-plugin
openclaw mcp doctor agent-plugin --probe

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

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

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

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

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

​

Verify the connection

1. The agent-plugin skill is visible to the agent.
2. agent-plugin is connected and authenticated.
3. The client discovers the ten tools: describe_schema, find_resources, get_resource_details, get_related, get_resource_events, get_recent_events, get_correlated_events, query_graph, list_projects, and set_project.
4. A read-only request returns project-scoped evidence with an evidence timestamp.

Use Anyshift to find checkout-api. Report the selected resource kind, namespace
and cluster, then list its direct relationships with their types and observation
timestamps. Do not infer missing relationships.

​

Manage access and updates

• Update with your client’s plugin manager: Codex codex plugin marketplace add anyshift-io/agent-plugin --ref <version> then codex plugin add agent-plugin@anyshift; Claude Code /plugin update anyshift-graph@anyshift; VS Code from Chat: Open Customizations. For manual Git checkouts (Cursor, Kiro, OpenClaw, Hermes), run git pull --ff-only in the package directory, then restart the client.
• A release that changes the MCP endpoint (such as v0.3.0) is a new MCP entry: authorize once after updating. Your previous authorization stays listed under Authorized Apps and can be revoked there.
• The installed version is the version field of the package’s plugin.json; releases are listed at anyshift-io/agent-plugin.
• 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

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