# Production context for your agent

Anyshift connects infrastructure, code and observability data in a production graph. Query that graph with your own agent, or ask Annie to investigate an incident.

Source: https://anyshift.io/for-agents/product/context

## When does the Graph help?

- Use Graph MCP when your agent repeatedly joins resources and changes across infrastructure, code and monitoring. Start with direct source MCPs when one tool already contains the evidence your task needs.

- Anyshift’s cross-system benchmark measured 83.1% fewer model tokens and 46.7% less time with prepared Graph queries. It covered ten tasks in one synthetic environment; it does not measure setup costs or guarantee savings on other tasks.

[Compare Graph with direct MCPs](https://anyshift.io/for-agents/use-cases/connect-production-context)

[Benchmark and methodology (Markdown)](https://anyshift.io/markdown/blog/mcp-vs-graph-cross-domain-benchmark-v2.md)

## Connect Graph MCP

- Read topology, dependencies and change events with your own agent.

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

- Reuse an existing connection. For a new connection in Codex, run these commands, sign in through browser OAuth, then confirm the intended project with list_projects.

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

[Connect Graph MCP](https://docs.anyshift.io/pages/product/integration/graph_mcp)

## Other MCP clients

- Your client must support Streamable HTTP and browser OAuth. Add this remote server, sign in to Anyshift and select the intended project. The configuration format varies by client; reuse an existing plugin or server connection.

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

## Connect to your project

- Reuse your existing Anyshift integrations and MCP connection. If you already installed the plugin, Graph MCP is included; do not register it twice.

- For a new connection, follow the setup guide for your client, sign in through browser OAuth and select your project. Both endpoints use Streamable HTTP; no API token belongs in the MCP configuration.

- No Anyshift project yet? Create one and connect the data sources needed for your task. An existing project only needs additional integrations when the required evidence is missing.

[Install the plugin](https://docs.anyshift.io/pages/product/integration/production_intelligence_agent_plugin)

[SDK](https://docs.anyshift.io/pages/product/integration/sdk)

[Graph API](https://docs.anyshift.io/pages/product/graph-api/overview)

[CLI](https://docs.anyshift.io/pages/product/integration/cli)

[Create a project](https://app.anyshift.io/sign-up)

[Project setup](https://docs.anyshift.io/pages/onboarding/quick_start)

## Make a first read

- A successful read returns resource identities from the intended project. An empty result confirms that the request completed, not that your infrastructure is empty.

```text
Use the existing Anyshift Graph MCP connection. Call describe_schema, then list_projects and confirm the bound project is the one I intend to query. If the project cannot be confirmed, stop before reading resources. Choose a non-secret resource kind from the schema and use find_resources to list at most 5 resources. Return their names, kinds, scopes and hashedIDs. If none match, report the empty result; do not invent resources or switch projects.
```

## Work with graph evidence

- Call describe_schema first to discover the selected project's resource types, relationships and events.

- Use find_resources to resolve a resource, then use its hashedID to inspect relationships and time-bounded changes. Names may repeat across clusters and namespaces.

- Graph MCP is read-only. Inspect returned timestamps, page limits and get_related completeness signals. A truncated or filtered result is not a complete dependency map; missing evidence is not proof of absence.

- The graph keeps three days of history by default; longer history depends on your plan. Check that the incident window is actually covered. Current health cannot establish past health, and related events alone do not establish a root cause.

- Use Cypher only with Graph MCP's query_graph tool. The Graph SDK, API and CLI have their own Graph Query Language; queries are not interchangeable.

[Graph tools and examples](https://docs.anyshift.io/pages/product/integration/graph_mcp#tools)

[Graph Query Language](https://docs.anyshift.io/pages/product/integration/graph_query_language)

[Data history](https://docs.anyshift.io/pages/overview)

## Try a task

[Review Kubernetes permissions before merge](https://anyshift.io/for-agents/use-cases/review-kubernetes-permissions)

[Give your agent production context across tools](https://anyshift.io/for-agents/use-cases/connect-production-context)

## 83% fewer model tokens in our cross-system benchmark

- Across ten tasks spanning AWS, Kubernetes, Datadog, GitHub and PagerDuty, prepared Graph queries used 83.1% fewer cumulative model tokens and took 46.7% less time on average than native MCPs.

- Anyshift’s September 2026 benchmark used one synthetic environment, the same model and time limit, and one selected pair per task, including incomplete answers. The Graph agent received prepared queries; native MCP agents chose their calls. This measures retrieval and answer generation, not installation or collection costs. Token reduction is not an equivalent reduction in spend.

[Read the benchmark and methodology (Markdown)](https://anyshift.io/markdown/blog/mcp-vs-graph-cross-domain-benchmark-v2.md)

## Queries and runs are different

- A Graph query is a request for data from your Anyshift graph. Use the plugin, Graph MCP, SDK, API or CLI: all share the same query allowance.

- Anyshift agents use a separate run allowance. When you use your own AI provider to query the graph, you pay that provider separately. See pricing for current plan limits.

[Pricing](https://anyshift.io/for-agents/pricing)