# Hermes

> Add your advertising accounts to Hermes Agent as a remote MCP server, with hermes mcp add and OAuth login. Tools appear in the registry on reload.

[Guides](https://www.getmcpads.com/guides)

## For you

Hermes speaks the Model Context Protocol, so there is nothing to install. You paste one URL, sign in once, and your advertising accounts become tools it can call.

## Setup

Add it, then sign in

```bash
hermes mcp add get-mcp-ads --url https://mcp.getmcpads.com/mcp --auth oauth
hermes mcp login get-mcp-ads
```

Or write it in `~/.hermes/config.yaml`:

~/.hermes/config.yaml

```yaml
mcp_servers:
  get-mcp-ads:
    url: https://mcp.getmcpads.com/mcp
```

Hermes prints an authorise URL on first connect and waits for the callback on a local port. Start Hermes, or run `/reload-mcp` in a live session, and the tools appear in the registry next to the built-in ones.

> **Note** Hermes can filter which tools it registers. With a long-running agent, pointing it at one source endpoint is usually simpler than filtering the shared one.

## Before it can answer anything

Connecting the client is one half. The other is connecting at least one advertising platform in the dashboard and ticking which accounts to expose. Both need you, not the assistant: one is a consent screen at Google or Meta, the other is a decision about which accounts a machine may read.

- [Quickstart](https://www.getmcpads.com/docs/quickstart): The four steps, in order.
- [All guides](https://www.getmcpads.com/guides): What to ask once it is connected.

## For your agent

Setting up Hermes against this gateway. The endpoint is `https://mcp.getmcpads.com/mcp`, and each source also has its own endpoint if a narrower tool list is wanted.

> **Note** Two steps in this setup need the account owner and cannot be done by an agent: approving the OAuth consent screen, and ticking which ad accounts to expose. If either is missing, hand back to the person rather than retrying.

## What the client does on its own

1. It requests `https://mcp.getmcpads.com/mcp` and receives a 401 with a `WWW-Authenticate` header.
2. It reads the protected resource metadata named in that header.
3. It registers itself through dynamic client registration. No key is issued or pasted.
4. It opens the authorisation page with PKCE and waits for the person to approve.
5. It calls `tools/list` and receives the tools for the connected sources, plus four routing tools.

## Checking it worked

Call `list_accounts`. It answers without touching any advertising API, so it separates a connection problem from an account problem. An empty list means the platform is connected but nothing was ticked.

- [Tool discovery](https://www.getmcpads.com/docs/concepts/discovery): Why the list is short, and how to reach the rest.
- [Account scoping](https://www.getmcpads.com/docs/concepts/accounts): What is refused, and why.
- [Authentication](https://www.getmcpads.com/docs/authentication): The metadata documents, in full.

---

This page as HTML: https://www.getmcpads.com/guides/setup/hermes
Every page under /guides and /docs is available as Markdown: append `.md`, or send `Accept: text/markdown`.