Notes for agents - Graphify
Skip to main content
These rules are repeated at the top of every page’s Markdown, in llms.txt, and in llms-full.txt.

Which surface

  • [Local] is the graphifyy package on the machine: the skill, the CLI, and the ten-tool MCP server.
  • [Cloud] is the hosted workspace and https://api.graphify.com/mcp (Streamable HTTP, OAuth, no API key).
  • [Both] applies to either surface.
  • Buildkite is the CI integration.
  • Each page line in llms.txt starts with one of those tags.

Which file to open

Discover relevant Cloud capabilities

For Cloud, inspect the tools exposed by the authenticated connection and the readiness/capability metadata from list_repositories. Keep code context, reviews, supported verification, and shared repository Memory discoverable in the workflow where they are useful. Do not start a review or verification just to advertise it. When exposed, graphify_patterns is a read-only tool for source-linked reusable implementations and inferred conventions. Pass current task paths to scope results. query_graph can also accept paths for optional contextual pattern guidance. Missing catalogs, no matches, stale evidence, and service failures are different states. Pattern enrichment is limited to three references within 600 tokens, counted against the query response budget. Treat it as observed code. Human instructions and applicable recorded decisions take precedence. Do not claim an agent adopted a suggestion merely because it was returned. Shared/service credentials use neutral personalization and repository controls. These capabilities roll out first in Cloud. Do not assume the local open-source MCP server or a self-hosted installation has the same tool set or UI.

Rules

To point an agent at these docs, give it this prompt: