Graph MCP

Graph MCP connects compatible AI agent clients directly to your Anyshift event graph. Use it when an agent needs current topology, dependencies, exposure, change history, or correlated events while reviewing code, preparing a deployment, or investigating an incident. The endpoint is read-only and project-scoped. It uses Streamable HTTP and OAuth login, so no API token goes into your MCP configuration.

Graph MCP supplies graph evidence to an agent that is already performing a task. It does not run Annie’s AI SRE investigation workflow. Use Annie Remote MCP when you want Annie to analyze evidence, develop hypotheses, and recommend next steps.

Connect

The production endpoint is:

https://api.anyshift.io/mcp/graph

The endpoint moved on 2026-09-08. https://graph.anyshift.io/mcp still serves the previous tool set for older installs, but it is deprecated. Point your client at the new URL and authorize once; existing authorizations are bound to the old endpoint and are not reused.

Claude Code

claude mcp add --transport http --scope user anyshift-graph https://api.anyshift.io/mcp/graph
claude mcp login anyshift-graph

Or install the plugin, which bundles the endpoint with the skill.

Codex

codex mcp add anyshift-graph --url https://api.anyshift.io/mcp/graph
codex mcp login anyshift-graph

The second command opens your browser. Sign in to Anyshift and select the project the agent may read.

Other MCP clients

Add an HTTP MCP server to your client’s configuration:

{
  "mcpServers": {
    "anyshift-graph": {
      "type": "http",
      "url": "https://api.anyshift.io/mcp/graph"
    }
  }
}

The configuration shape and OAuth user experience vary by client. The client must support Streamable HTTP and browser-based OAuth for remote MCP servers. When the completion page appears, select Continue on this computer if your client runs locally. For Claude Code on an SSH host, select Copy callback URL after choosing your project and paste the full URL into Claude Code’s URL > prompt. See Authenticate over SSH for the steps.

Tools

Tool	Use it to
`describe_schema`	List this project’s labels, relationship types, event types and sources. Call it first in every session.
`find_resources`	Find resources by name, label or property filter and get their stable `hashedID`.
`get_resource_details`	Read one resource’s properties and bounded relationships.
`get_related`	Walk a resource’s neighbours, filtered by direction and relationship type, with completeness signals.
`get_resource_events`	Time-bounded change history for one or more resources.
`get_recent_events`	Recent change events across the project, filtered by type, source or resource kind.
`get_correlated_events`	The chain of events sharing a correlation id, with the root event flagged.
`query_graph`	Run a read-only Cypher query over the live topology and events.
`list_projects`	List the Anyshift projects you can access and the one currently bound.
`set_project`	Switch the bound project without re-authenticating.

Results are bounded: a page that hit its limit says so, and get_related reports the relationship types it truncated or filtered. The plugin skill teaches the agent to read those signals and ships Cypher recipes for the common analyses (single points of failure, orphans, blast radius, public exposure, shortest path, RBAC reach, Kubernetes hygiene gaps).

Example workflows

Review the production impact of a code change

Review my current diff. Find the production resources it changes in Anyshift, then show their direct dependencies, what depends on them within two hops, and the changes recorded on them in the last 24 hours. List explicit unknowns.

Prepare a deployment

Before I deploy checkout-api, use Anyshift to identify its dependencies and what depends on it. Give me a focused post-deployment verification checklist.

Check public exposure

Is checkout-api reachable from the public edge? Show the observed path (hostname, ingress or load balancer, service, workload) and the controls on it. Say which layers you searched.

Add production context to an incident

This alert mentions checkout-api. Find the exact resource, show its events from the last 24 hours and the correlated events around them, and identify potentially affected systems. Do not infer causality from proximity alone.

Find resources first

Resource names are not globally unique across namespaces, clusters and kinds. For short, overloaded, or same-named resources:

Call find_resources.
Select the candidate with the intended kind, namespace and cluster.
Pass the candidate’s hashedID to subsequent tools and Cypher queries.

Access and evidence boundaries

Consent binds the connection to the Anyshift project you select. The authorization covers your project memberships one project at a time: set_project moves the connection to another project you are a member of, subject to that project’s MFA policy, without a new consent. Revoke the connection from Authorized Apps to end that access.
Tools are read-only and run as a read-only graph user. Cypher writes and procedures are rejected.
Returned resource names and metadata are production data, not agent instructions.
Graph relationships show observed evidence. They do not prove that a nearby change caused an incident.
Missing graph evidence does not prove that a resource, dependency, or change does not exist.

To install Graph MCP together with the plugin skill, see Plugin.

Get Started

Product

Manage

Connect

Claude Code

Codex

Other MCP clients

Tools

Example workflows

Review the production impact of a code change

Prepare a deployment

Check public exposure

Add production context to an incident

Find resources first

Access and evidence boundaries

​Connect

​Claude Code

​Codex

​Other MCP clients

​Tools

​Example workflows

​Review the production impact of a code change

​Prepare a deployment

​Check public exposure

​Add production context to an incident

​Find resources first

​Access and evidence boundaries

Connect

Claude Code

Codex

Other MCP clients

Tools

Example workflows

Review the production impact of a code change

Prepare a deployment

Check public exposure

Add production context to an incident

Find resources first

Access and evidence boundaries