> ## Documentation Index
> Fetch the complete documentation index at: https://marrow-docs.hologrow.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Using Hermes Agent

# Using Hermes Agent with Marrow

[Hermes Agent](https://hermes-agent.nousresearch.com) is an open-source, self-hosted agent from [Nous Research](https://nousresearch.com). Use it when you want a local agent (desktop, CLI, or TUI) that can call Marrow MCP as its data layer for synced store and ad data.

## Prerequisites

* At least one data source connected in [Integrations](../Marrow%20Basics/Features/Integrations.md) and syncing in [Data Explorer](../Marrow%20Basics/Features/Data%20Explorer.md)
* Hermes Agent installed ([hermes-agent.nousresearch.com](https://hermes-agent.nousresearch.com))
* An LLM provider configured in Hermes (for example Anthropic via `hermes model`)
* An MCP key from [AI Platforms](../Marrow%20Basics/Features/AI%20Platforms.md)

## Step 1: Get Marrow credentials

From **AI Hub → AI Platforms**:

* MCP server URL: `https://mcp.marrow.ai/mcp/v1`
* Create an **MCP key** and copy it (shown only once)

See also: [MCP overview](./MCP.md)

## Step 2: Add Marrow to Hermes MCP config

Hermes reads MCP servers from `~/.hermes/config.yaml`. Remote HTTP servers use a `url` plus optional `headers`.

1. Open `~/.hermes/config.yaml`.
2. Add or extend `mcp_servers`:

```yaml theme={null}
mcp_servers:
  marrow:
    url: "https://mcp.marrow.ai/mcp/v1"
    headers:
      Authorization: "Bearer YOUR_MCP_KEY"
```

Replace `YOUR_MCP_KEY` with your key from AI Platforms.

3. Save the file and restart Hermes (or run `/reload-mcp` in an active session if your Hermes build supports it).

### Quick reference

| Item        | Value                                  |
| ----------- | -------------------------------------- |
| Config file | `~/.hermes/config.yaml`                |
| Section     | `mcp_servers.marrow`                   |
| URL         | `https://mcp.marrow.ai/mcp/v1`         |
| Auth        | `Authorization: Bearer <YOUR_MCP_KEY>` |

## Step 3: Verify the connection

Open a new Hermes chat (desktop UI or `hermes chat`) and ask:

```
What Marrow tools do you have access to?
```

Hermes should list Marrow MCP tools. If nothing appears, check YAML indentation, that the key is active, and that Hermes was restarted after the edit.

## Step 4: Run a data prompt

```
Show me my Amazon Seller sales for the last 7 days.
```

If Hermes returns real numbers from your synced accounts, Marrow is connected.

## Notes

* Desktop UI and CLI share the same `config.yaml` and MCP setup.
* Prefer keeping the key out of version control; treat it like a password.
* Hermes MCP docs evolve quickly — if native `url` auth fails on your build, check the current [Hermes MCP guide](https://hermes-agent.nousresearch.com/docs/guides/use-mcp-with-hermes) for your version.

## Security

* Marrow is **read-only** — it never posts or changes store/ad settings.
* Rotate or revoke MCP keys from AI Platforms anytime.

## Related

* [MCP overview](./MCP.md)
* [AI Platforms](../Marrow%20Basics/Features/AI%20Platforms.md)
* [Skills](../Marrow%20Basics/Features/Skills.md)
* [Hermes MCP config reference](https://hermes-agent.nousresearch.com/docs/reference/mcp-config-reference)