> ## Documentation Index
> Fetch the complete documentation index at: https://metatronscribe.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Hermes Agent

> Connect Hermes Agent to the public Metatron documentation MCP through the mcp_servers configuration. Searches published docs only.

<Warning>
  This connects Hermes Agent to the **public documentation-search MCP**. It does not connect Hermes to any private Metatron tool, file, or inbox. See [Security model](/security-model).
</Warning>

**Syntax source:** the public Hermes Agent MCP documentation (`user-guide/features/mcp.md` and `reference/mcp-config-reference.md` in the NousResearch/hermes-agent repository, retrieved 2026-10-10). **Live connection: NOT TESTED**, because the published endpoint is not deployed yet.

## Prerequisites

* Hermes Agent installed and running.
* The published site at `https://docs.metatronscribe.com` returns its index at `/llms.txt`.

## 1. Add the server

Add an `mcp_servers` entry to Hermes's configuration file (`config.yaml`). This is the public HTTP form from the Hermes reference:

```yaml theme={null}
mcp_servers:
  metatron_docs:
    url: "https://docs.metatronscribe.com/mcp"
    enabled: true
    timeout: 120
    connect_timeout: 60
```

No `headers` block is needed, because public pages need no credentials. Do not add a token to this file.

## 2. Restrict the tools (recommended)

Hermes registers every discovered tool unless you filter it. The public reference documents `tools.include`, `tools.exclude`, `tools.resources`, and `tools.prompts`:

```yaml theme={null}
mcp_servers:
  metatron_docs:
    url: "https://docs.metatronscribe.com/mcp"
    enabled: true
    timeout: 120
    connect_timeout: 60
    tools:
      include:
        - "<search-tool-name>"
      resources: false
      prompts: false
```

Rules from the public reference:

* Entries without `*`, `?`, or `[` match names exactly.
* `include` wins when both `include` and `exclude` are set.
* `resources: false` and `prompts: false` turn off the utility wrappers Hermes adds for those surfaces.

Replace `<search-tool-name>` with a name your session reports. The placeholder must be changed before this configuration is used.

## 3. Verify the connection

```bash theme={null}
hermes mcp test metatron_docs
```

The test reports what the server answered. A passing test shows the discovered tools. Use `hermes mcp configure metatron_docs` to review the tool selection.

## 4. Reload after changes

Run `/reload-mcp` inside a Hermes session, or start a new session. The public docs describe both options.

## 5. Ask a question

In a session, ask something the documentation answers, such as "What are Metatron's three interfaces?" A correct answer names the local MCP, the public documentation-search MCP, and the future authenticated service.

## Troubleshooting

| Symptom | Likely cause | Fix |
| - | - | - |
| `hermes mcp test` fails to connect | Site not deployed, DNS not propagated, or the URL is wrong | Open `https://docs.metatronscribe.com/llms.txt` in a browser. |
| Connection timeout | Slow response | Raise `connect_timeout`. |
| An empty tool list after filtering | `include` matches no discovered name | Check the names from `hermes mcp test` and correct the list. |

## Remove

Delete the `metatron_docs` block from `mcp_servers`, then run `/reload-mcp`. The public Hermes documentation does not list a remove subcommand.

## What this integration cannot do

* Read Metatron's governance files, inbox, or seed-target files.
* Call any operational Metatron tool.
* Write to the documentation or to any system.


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