> ## 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.

# Graphify for Hermes Agent

> Connect Nous Research's Hermes Agent to Graphify's hosted MCP server with browser OAuth, or install the Graphify Local skill for Hermes.

Connect [Hermes Agent](https://hermes-agent.nousresearch.com/docs/user-guide/features/mcp/) to Graphify in one of two ways. **Graphify (hosted)** uses Hermes's native remote MCP and OAuth support. No API key, wrapper, or local server is needed. **Graphify Local** installs the open-source skill. See [Graphify vs Local](https://docs.graphify.com/platform/graphify-vs-local.md) to choose.

**Graphify (hosted)**

### Before you start

* A [Graphify](https://app.graphify.com) account with a workspace and at least one repository that has finished indexing.
* A current Hermes release with native MCP OAuth support.

### 1. Add the server

Merge this entry into your active Hermes profile's `config.yaml`, normally `~/.hermes/config.yaml`. Keep your existing configuration and other MCP servers.

```yaml ~/.hermes/config.yaml theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}}
mcp_servers:
  graphify:
    url: https://api.graphify.com/mcp
    auth: oauth
```

### 2. Sign in

```bash theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}}
hermes mcp login graphify
```

Complete the authorization in your browser. Hermes stores and manages the OAuth credentials.

### 3. Choose tools

```bash theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}}
hermes mcp configure graphify
```

Pick the Graphify tools you want Hermes to use, then restart the Hermes session. Some tools write: they can record query trails, save or change memory, and switch the active workspace. Leave those off if you want read-only use.

### 4. Ask a question

Ask Hermes to list your Graphify workspaces and repositories, select a repository, and look up a function you know. Check that the file paths it returns match the repository.

### If something fails

* **Sign-in does not open.** Update Hermes to a release with MCP OAuth support, then run `hermes mcp login graphify` again.
* **No repositories.** Wait until the repository shows **Indexed** in **Repositories**, and check that you signed in to the right workspace.
* **An answer looks stale.** The graph follows the default branch. Results can lag behind a push until the next index finishes.

**Graphify Local**

```bash theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}}
uv tool install graphifyy
graphify install --platform hermes
```

The installer copies the Graphify skill and adds a Graphify section to `AGENTS.md`, so Hermes checks the graph before it reads source. Add `--project` to install into the current repository instead of your profile. Then ask Hermes to map the repository with the Graphify skill.

## Related

> **[Integrations overview](https://docs.graphify.com/integrations/overview.md)**
>
> Every agent, hosted and local, at a glance.

> **[Other MCP clients](https://docs.graphify.com/integrations/other-agents.md)**
>
> Generic setup for any MCP client.

[PreviousGraphify MCP for OpenClaw](https://docs.graphify.com/integrations/openclaw.md)
[NextOther MCP clients](https://docs.graphify.com/integrations/other-agents.md)


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