# How do you connect Hermes Agent to Super Artifacts?

> Connect Artifacts and Mail in the Super Belt dashboard tab with one approval and separate product keys.

By Azim Ahmed, Founder · Published October 20, 2026 · Updated November 15, 2026 · [Playbooks](https://pr-2198-stg.superartifacts.app/blog/category/playbooks.md) · ~2 min

Topics: MCP

## In short

- The Super Belt tab connects Artifacts and Mail with one approval and separate keys.
- Compare the code before allowing access; choose your workspace and Mail access.
- Hermes may ask for another approval to reload tools.
- Disconnect removes local keys; revoke them in each product’s Agents page.

Hermes can publish a page and read back what visitors submit. It can also read and send screened mail. Those are separate products with separate keys; connecting them should make that boundary visible.

## What do you need before you start?

Use Hermes 0.23.0 or later and a Super Artifacts account. Install the [Super Belt package](https://github.com/Superbelt/plugins/tree/main/hermes#readme) in the Hermes profile you want to connect. Remove an older `super-artifacts` plugin or native MCP entry first so it cannot shadow the new package.

## How do you connect it?

Open **Super Belt** in `hermes dashboard`. Choose **Artifacts**, **Mail**, or both, then **Connect**. Open the displayed link on any device. Compare the code before allowing access, choose the workspace and Mail access, and approve.

One approval creates a key for each selected product. Keys stay in that Hermes profile. A failure for Mail keeps a successful Artifacts connection; use **Retry** on the affected row. Graph appears as early access and is not offered yet.

Hermes may require one more approval to reload tools. If tools are missing, run `/reload-mcp` in chat and approve it. A dashboard check does not prove an existing chat has reloaded.

## What should you ask first?

Ask for a private page explicitly. New artifacts otherwise use the workspace default.

**Check the connection**

```prompt
Name the Super Artifacts account and the Super Agent Mail account you are connected to. Do not publish or send anything.
```

Then ask Hermes to publish something small with private access and open its returned link. See [Connect your agent](https://pr-2198-stg.superartifacts.app/docs/connect.md) for the current connection guide and [Access and sharing](https://pr-2198-stg.superartifacts.app/docs/access-and-sharing.md) for who can open it.

## What about webhooks?

The Super Belt tab configures Artifacts mentions, human comments and read-only publish summaries through an existing public HTTPS listener. Mail webhooks say **Not available yet**: the shared endpoint is pending. A successful test means Hermes accepted it, not that an agent completed a task. See [Webhooks](https://pr-2198-stg.superartifacts.app/docs/webhooks.md).

## How do you disconnect it?

Use **Disconnect** on a product row or **Disconnect all**. Local removal does not revoke keys already loaded in another session. Revoke each key in that product’s Agents page.

## Keep reading

- [The Build Factory: see what your coding agents actually shipped](https://pr-2198-stg.superartifacts.app/blog/the-build-factory.md): Run coding agents like a factory you can see into: a proof page on every pull request, a changelog every day, both read on a phone. (October 19, 2026)
