> ## 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.
> Choose the surface before you open a page. Local (Graphify Local) is the graphifyy package on the machine: the skill, the CLI, and the ten-tool MCP. Its pages are the Open Source tab (/open-source/) and the Graphify Local tab on each Integrations page. Graphify is the hosted workspace and https://api.graphify.com/mcp (Streamable HTTP, OAuth, no API key). Its pages are the Graphify tab (/platform/, /concepts/) and the Graphify (hosted) tab on each Integrations page. Prefer Graphify unless the user asks for a local or offline setup. Cookbooks (/cookbooks/) and /mcp/docs-search apply to both. Each page's source frontmatter records this as surface: local, cloud, or both. Buildkite is the CI integration.
> In llms.txt, tell the surface from the page path. Graphify: /platform/ and /concepts/. Local: /open-source/. Most /integrations/ pages cover both, with a Graphify (hosted) tab and a Graphify Local tab. Everything else applies to both.
> graphifyy release notes are published at https://github.com/Graphify-Labs/graphify/releases and https://graphify.com/changelog. The current package version is on PyPI (https://pypi.org/project/graphifyy/).
> 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 JetBrains, ChatGPT, Codex, and Dots, and Vercel pages use the hosted server, not the ten-tool list. On pages with tabs, the Graphify (hosted) tab uses the hosted server and the Graphify Local tab uses the local skill or the ten-tool server.
> 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.

# Connect cloud coding agents to hosted MCP

> Connect Claude Code, Codex, Cursor or VS Code to Graphify's hosted MCP server, sign in with OAuth, and let your agent query indexed repositories.

Graphify, the hosted product, builds and stores the graph of your repositories and serves it over MCP at `https://api.graphify.com/mcp`. Point your coding agent at that URL, sign in once in the browser, and the agent asks the graph instead of re-reading files every session. There's nothing to install or run.

## What you'll build

* An indexed repository in Graphify.
* An agent connected to the hosted MCP server over Streamable HTTP with OAuth.
* A working first query, and prompts for everyday use.

## Setup

* An account at [app.graphify.com](https://app.graphify.com). It's free for up to 3 repositories, no card required.
* At least one repository with the status **Indexed**. The [quickstart](https://docs.graphify.com/platform/quickstart.md) walks through connecting GitHub and switching on **Indexing** from a repository's **…** menu.

## Step 1: Open the MCP connector

In the console, go to **Connectors → MCP**. Setup has three steps: **Choose agent**, **Connect** and **Try a query**. Pick your agent, or open **Browse all agents**.

To let the agent do the setup, choose **Copy quick-start prompt** and paste it into your agent.

## Step 2: Add the server to your agent

**Claude Code** (run in a terminal, not inside a session):

```bash theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}}
claude mcp add --transport http --scope user graphify https://api.graphify.com/mcp
```

**Cursor, Claude Desktop and other `mcpServers` clients:**

```json theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}}
{
  "mcpServers": {
    "graphify": { "url": "https://api.graphify.com/mcp" }
  }
}
```

**VS Code** (`.vscode/mcp.json`):

```json theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}}
{
  "servers": {
    "graphify": { "type": "http", "url": "https://api.graphify.com/mcp" }
  }
}
```

The server is also listed in the MCP registry as `io.github.Graphify-Labs/graphify`. Per-agent details are on [Cloud MCP](https://docs.graphify.com/integrations/overview.md).

## Step 3: Sign in

On first use the agent opens a browser window. In Claude Code, run `/mcp`, pick **graphify** and choose to authenticate. Sign in to Graphify and approve access. There's no API key to paste or store.

## Step 4: Check the connection

Paste the test prompt from **Try a query**, or ask:

```text theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}}
Use Graphify's list_repositories tool and show the repositories I can access.
```

The list should match your workspace. If you belong to more than one, ask the agent to use `list_workspaces` and `set_workspace` first.

## Step 5: Ask about your code

Name the symbol, file or area you care about:

* `Who calls the function that validates a session token?`
* `What would break if I changed this module's public interface?`
* `Which tests cover the billing webhook handler?`
* `Trace how a request reaches the billing service.`

The agent picks tools such as `graphify_find`, `graphify_callers`, `graphify_impact`, `graphify_tests_for` and `graphify_trace`. You don't call them by hand.

## Step 6: Give the agent memory

Ask the agent to record decisions as it works:

```text theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}}
Remember that payments retries are capped at 3 because of the provider's rate limit.
```

The agent stores this with `remember` and finds it later with `recall`. Inspect and remove entries on the [Memory](https://docs.graphify.com/platform/memory.md) page.

## When it goes wrong

**No browser window opens.** Some agents need a restart after you add a server. Restart it, then run a tool again.

**`list_repositories` returns nothing.** The repository isn't indexed yet, or the agent is in another workspace. Check the status in **Repositories**, then use `set_workspace`.

**The agent answers without Graphify.** Name the tool or say "use Graphify" in the prompt. Some agents only call MCP tools when asked.

## Production patterns

* Add the server at project scope (`.mcp.json` or `.vscode/mcp.json`) and commit it, so teammates connect with one sign-in.
* Check pull requests your agent opens on the [Reviews](https://docs.graphify.com/platform/reviews.md) page.
* Open the [Graphs](https://docs.graphify.com/platform/graphs.md) and [Wiki](https://docs.graphify.com/platform/wiki.md) pages when an answer needs a closer look.
* To keep everything on your own machine, use the open-source CLI instead: [Give Claude Code a graph of your monorepo](https://docs.graphify.com/cookbooks/claude-code-monorepo.md).

## Complete example

```bash theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}}
# 1. Index a repository at app.graphify.com
# 2. Connect Claude Code
claude mcp add --transport http --scope user graphify https://api.graphify.com/mcp
# 3. In Claude Code, run /mcp and finish the browser sign-in, then ask:
#    "Use Graphify's list_repositories tool and show my repositories."
```

## What you built

Your agent queries a graph we build and host. It answers questions about callers, impact and tests from indexed repositories, and remembers decisions across sessions.

## Next steps

> **[Cloud MCP](https://docs.graphify.com/integrations/cloud.md)**
>
> Per-agent setup for the hosted MCP server.

> **[Plan a refactor](https://docs.graphify.com/cookbooks/plan-a-refactor.md)**
>
> Ask your agent what a change will reach.

> **[Try it in Graphify](https://docs.graphify.com/platform/quickstart.md)**
>
> We build and host the graph for you. Start with a 14-day Pro trial, then keep up to 3 repositories on Free. No card required.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.