> ## Documentation Index > Fetch the complete documentation index at: https://docs.graphify.com/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > The PyPI package is graphifyy, with two y's. The command is graphify. > /graphify . is typed in an assistant chat, not in a shell. > Use only commands, flags, and endpoints shown on these pages. Do not invent one. > Check the current version on PyPI (https://pypi.org/project/graphifyy/) or in https://docs.graphify.com/changelog.md before you describe what shipped. > The official site is https://graphify.com. These docs are https://docs.graphify.com. > The local MCP server is the ten tools in the MCP tool reference and reads a graph on the machine. The hosted server is https://api.graphify.com/mcp (Streamable HTTP, OAuth, no API key). The VS Code, JetBrains, ChatGPT, and OpenClaw pages use the hosted server, not the ten-tool list. > Read https://docs.graphify.com/llms.txt, then open one page's .md link. Use https://docs.graphify.com/llms-full.txt only when one page is not enough. # Graphify MCP for OpenClaw > Connect OpenClaw to your indexed repositories through Graphify's hosted MCP server. The **Graphify MCP** plugin connects OpenClaw to Graphify's hosted MCP server at `https://api.graphify.com/mcp`. MCP is the connection. The plugin is the package OpenClaw installs from [ClawHub](https://clawhub.ai/graphify-labs/plugins/graphify-mcp). Once connected, OpenClaw can search the repositories you have indexed in [Graphify Cloud](https://app.graphify.com), follow callers and dependencies, and judge what a change reaches. There is no API key to paste and no graph to build on your computer. This is the same hosted server as [Graphify MCP for VS Code](/integrations/vscode), [Graphify MCP for JetBrains](/integrations/jetbrains), and [Graphify for ChatGPT](/integrations/chatgpt). Graphify Labs publishes the package. OpenClaw has not marked it as an official OpenClaw plugin. `graphify install --platform claw` on [Other coding assistants](/integrations/other-assistants) installs the local skill for a graph on your machine. This page connects OpenClaw to Graphify Cloud. ## Before you start * OpenClaw with remote MCP, OAuth, and Claude-format bundle support. The package was prepared for OpenClaw **2026.9.8**. Older releases may differ. See [OpenClaw's plugin install guide](https://docs.openclaw.ai/cli/plugins/install). * A model enabled in OpenClaw, with permission to call tools. That access is separate from your Graphify plan. * A repository indexed in your Graphify workspace. Sign in at [app.graphify.com](https://app.graphify.com), connect a repository, and wait for its status to reach **Indexed**. See [Repositories and builds](/platform/repositories). ## 1. Install the plugin [Open Graphify MCP on ClawHub](https://clawhub.ai/graphify-labs/plugins/graphify-mcp) Install the published package, then confirm OpenClaw sees it: ```bash theme={null} openclaw plugins install clawhub:@graphify-labs/graphify-mcp openclaw plugins inspect graphify-mcp ``` If you already cloned [graphify-mcp](https://github.com/Graphify-Labs/graphify-mcp), the same bundle is in `integrations/openclaw`: ```bash theme={null} openclaw plugins install ./integrations/openclaw openclaw plugins inspect graphify-mcp ``` Installing the plugin does not sign you in by itself. ## 2. Sign in Register the hosted server, then complete Graphify sign-in in the browser: ```bash theme={null} openclaw mcp set graphify '{"url":"https://api.graphify.com/mcp","transport":"streamable-http","auth":"oauth"}' openclaw mcp login graphify openclaw mcp doctor graphify --probe ``` If a server named `graphify` already exists, run `openclaw mcp show graphify` first and keep any settings you meant to keep. The same connection, merged into your OpenClaw configuration: ```json theme={null} { "mcp": { "servers": { "graphify": { "url": "https://api.graphify.com/mcp", "transport": "streamable-http", "auth": "oauth" } } } } ``` Use one connection named `graphify`. A second name for the same URL shows the tools twice. Do not put a password or token in the configuration. OpenClaw stores the OAuth credentials. Start a new agent session after this. If OpenClaw prints a restart instruction, follow that instruction. ## 3. Ask a question Ask OpenClaw to list what the connection can see: ```text theme={null} List my Graphify workspaces and repositories. ``` Pick a repository from the answer, then ask: * `In my selected repository, find the function that handles authentication.` * `Show its callers and the linked tests, with file paths as evidence.` A connection check includes a repository lookup. Tool discovery alone does not show that the index is reachable. Results come from the repositories indexed in your workspace. Open the source an answer cites before you rely on it. Static results do not run the code or the tests. Some tools save repository notes or change the selected workspace. Read each tool request and approve it only when that is what you meant. ## If something fails | What you see | What to do | | - | - | | The install stops and asks you to accept capabilities | Review the Graphify MCP server on that screen and accept it. On a noninteractive install, run the same install command again with `--accept-capabilities`. | | Graphify tools are hidden | Check that the plugin is enabled and that your tool policy allows it. A `bundle-mcp` denial hides these tools. | | Sign-in fails | Run `openclaw mcp doctor graphify --probe`, then `openclaw mcp login graphify` again. | | No repositories, or empty answers | That repository is not indexed yet, or it is in a different workspace. Check its status in [Repositories and builds](/platform/repositories), then ask OpenClaw to list repositories again. | | Two copies of the Graphify tools | Keep a single server named `graphify`. Remove the extra connection to the same URL. | ## Related Connect ChatGPT, Codex, and Dots to the same hosted server. Connect VS Code agents to the same hosted server.