Skip to main content
Connect Hermes Agent 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 to choose.

​
Before you start

  • A Graphify 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.
~/.hermes/config.yaml

​
2. Sign in

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

​
3. Choose tools

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.

Integrations overview

Every agent, hosted and local, at a glance.

Other MCP clients

Generic setup for any MCP client.