Anyshift for agents

Choose an interface

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.

In the selected Anyshift project, investigate this alert in read-only mode: [paste the alert, affected service and time window]. Use ask_annie with mode=rca, then get_annie_response until the investigation completes or reports a failure. Return the findings, supporting evidence and unresolved questions. Do not change infrastructure or publish messages.

Start with a task

• Review a pull request with your own coding agent using Graph MCP. The agent needs the diff; the graph supplies production context.
• Delegate an incident investigation through Annie Remote MCP. It starts a run; retrieve the result from that same investigation.

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.

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. Check timestamps and completeness signals; missing evidence is not proof of absence, and related events 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.

Let Annie investigate

• Incident Investigator examines alerts using relevant changes and service signals, then reports findings, evidence and next steps.
• Use Graph MCP with your own coding agent to review a pull request or prepare deployment checks. Your agent performs the analysis using production context from the graph.

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.

If you get stuck

Official references