# How to connect Magic Patterns to Hermes Agent (no API keys)

> Connect Magic Patterns to Hermes with ClawLink in one click — 23 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.

Web version: https://claw-link.dev/hermes/magic-patterns

Most guides for giving Hermes Agent Magic Patterns access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Magic Patterns setup: pair once in the browser and your always-on Hermes agent can act on Magic Patterns for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.

## Setup

It takes three steps to connect Hermes to Magic Patterns.

1. **Install ClawLink** — add the plugin to Hermes Agent once.
2. **Connect Magic Patterns** — one-click OAuth in the ClawLink dashboard.
3. **Use it from chat** — ask Hermes Agent in plain English.

**Paste this into Hermes to set up ClawLink:**

> Set up ClawLink for Hermes and tell me when it's ready.
> 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable`
> 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait.
> 3. I'll approve it in my browser, then reply "approved".
> 4. When I say approved, finish setup: `hermes clawlink finish`
> 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready.

**Alternative for any agent (no plugin needed):** if the Hermes Agent plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead:

```bash
npx -y @useclawlink/cli login          # sign in via browser — no API key to paste
npx -y @useclawlink/cli connect magic-patterns  # connect Magic Patterns (browser OAuth)
npx -y @useclawlink/cli actions magic-patterns  # list available actions
npx -y @useclawlink/cli run magic-patterns <action> --input '<json>'  # execute (add --confirm for writes)
```

### Install by command

The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:

```bash
hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin    # prints an approval link — open it and approve
hermes clawlink finish   # after approving in the browser
hermes clawlink test
```

Then connect Magic Patterns in the [ClawLink dashboard](https://claw-link.dev/dashboard) — a one-click OAuth approval, no API keys.

Verify the connection by asking Hermes:

> Use Magic Patterns to mcp get artifact and walk me through the result in plain English.

### Using a different agent?

The Hermes plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:

```bash
npx -y @useclawlink/cli login
```

`login` opens the same browser approval and stores a credential locally. Once Magic Patterns is connected in the dashboard, that agent calls the same 23 Magic Patterns tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent).

## Magic Patterns MCP for Hermes

Looking for a Magic Patterns MCP server for Hermes Agent? ClawLink connects Magic Patterns to Hermes Agent and exposes 23 Magic Patterns tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using OpenClaw instead? The [OpenClaw Magic Patterns integration](https://claw-link.dev/openclaw/magic-patterns) works the same way.

## What the Hermes Agent Magic Patterns integration can do

23 Magic Patterns tools are ready for Hermes Agent once the account is connected.

### All 23 Magic Patterns tools for Hermes

| Tool | What it does |
|---|---|
| **Mcp get artifact** `magic_patterns_mcp_get_artifact` | Gets the active artifact for a design, including its ID and list of files |
| **Mcp get design status** `magic_patterns_mcp_get_design_status` | Gets the current status of a design: whether AI generation is active, the active artifact ID |
| **Mcp get design system** `magic_patterns_mcp_get_design_system` | Resolves a design system's active artifact and lists its files |
| **Mcp get editor ID from URL** `magic_patterns_mcp_get_editor_id_from_url` | Resolves a Magic Patterns URL to an editor ID |
| **Mcp get inspiration document** `magic_patterns_mcp_get_inspiration_document` | Loads a Magic Patterns inspiration document by its id |
| **Mcp list design systems** `magic_patterns_mcp_list_design_systems` | Lists the design systems available to the authenticated user |
| **Mcp list version history** `magic_patterns_mcp_list_version_history` | Lists the artifact version history for a design |
| **Mcp read artifact files** `magic_patterns_mcp_read_artifact_files` | Reads the contents of one or more files from an artifact |
| **Mcp read design system files** `magic_patterns_mcp_read_design_system_files` | Reads the contents of one or more files from a design system's active artifact |
| **Mcp read recent message history** `magic_patterns_mcp_read_recent_message_history` | Reads the recent chat item history for a design |
| **Mcp create design** `magic_patterns_mcp_create_design` | Creates a new Magic Patterns design |
| **Mcp create design system** `magic_patterns_mcp_create_design_system` | Creates a new, blank design system owned by you and returns its ID + editor URL |
| **Mcp create inspiration document** `magic_patterns_mcp_create_inspiration_document` | Creates a Magic Patterns inspiration document and returns a shareable |
| **Mcp create new artifact** `magic_patterns_mcp_create_new_artifact` | Creates a new artifact by cloning an existing artifact |
| **Mcp create slide deck** `magic_patterns_mcp_create_slide_deck` | Creates a new Magic Patterns slide deck and kicks off AI generation |
| **Mcp inspiration add variant** `magic_patterns_mcp_inspiration_add_variant` | Fills in one concept of an existing Magic Patterns inspiration document with its self-contained |
| **Mcp publish artifact** `magic_patterns_mcp_publish_artifact` | Compiles an artifact's source files and sets it as the active artifact for the design |
| **Mcp publish design system** `magic_patterns_mcp_publish_design_system` | Publishes the design system's active artifact as a new immutable version |
| **Mcp inspiration clear variants** `magic_patterns_mcp_inspiration_clear_variants` | Resets every concept of an existing Magic Patterns inspiration document back to an empty |
| **Mcp inspiration update variant** `magic_patterns_mcp_inspiration_update_variant` | Revises a single already-filled concept of a Magic Patterns inspiration document in place |
| **Mcp send prompt** `magic_patterns_mcp_send_prompt` | Sends a natural language prompt to the Magic Patterns AI for an existing design |
| **Mcp write artifact files** `magic_patterns_mcp_write_artifact_files` | Creates or overwrites one or more files in an artifact |
| **Mcp write design system files** `magic_patterns_mcp_write_design_system_files` | Creates or overwrites files in a design system |

## Example prompts

**Mcp Get Artifact**

> Use Magic Patterns to mcp get artifact and walk me through the result in plain English.

**Mcp Get Design Status**

> Use Magic Patterns to mcp get design status and walk me through the result in plain English.

**Mcp Get Design System**

> Use Magic Patterns to mcp get design system and walk me through the result in plain English.

**Mcp Get Editor Id From Url**

> Use Magic Patterns to mcp get editor id from url and walk me through the result in plain English.

## ClawLink vs. building it yourself

The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Magic Patterns working from chat.

| | Manual | ClawLink |
|---|---|---|
| **Connection flow** | Register a Magic Patterns app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Magic Patterns through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. |
| **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Magic Patterns. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| **Agent usability** | You still need to expose the right Magic Patterns actions to the runtime in a format your agent can reliably use. | 23 tools for Magic Patterns are already exposed through ClawLink, so the agent can read and act from chat immediately. |

## ClawLink vs. Composio

Composio also exposes Magic Patterns to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Hermes Agent users instead. You install the plugin once, connect Magic Patterns in the browser, and the 23 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison.

### Hermes paired but still can't use Magic Patterns
Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`.

### Connection succeeds but no tools appear
Reconnect Magic Patterns from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.

### "Tool schema not loaded yet" error when calling Magic Patterns tools
Magic Patterns tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Magic Patterns call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.

### Magic Patterns returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.

### OAuth finished in the browser but the account is still missing
Try reconnecting Magic Patterns and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.

### Is there a Hermes Agent Magic Patterns integration?
Yes. ClawLink is the fastest way to connect Hermes to Magic Patterns: link your Magic Patterns account once in the browser and Hermes Agent can call the Magic Patterns API through 23 ready-made tools — no custom code or token handling.

### How do I connect Magic Patterns to Hermes with ClawLink?
Install the plugin with `hermes plugins install ClawLink-HQ/hermes-plugin --enable`, then pair once: run `hermes clawlink begin`, approve the link in your browser, and run `hermes clawlink finish`. Connect Magic Patterns in the dashboard and Hermes can use it from the next message — no config files or API keys to manage.

### How long does it take to connect Magic Patterns to Hermes Agent?
About two minutes. Sign in, click Connect next to Magic Patterns in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.

### Why use ClawLink instead of wiring Magic Patterns up myself?
The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Magic Patterns working from chat.

### Hermes paired but still can't use Magic Patterns
Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`.

## Related

- [DataRobot tools](https://claw-link.dev/hermes/datarobot) — DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets.
- [Hermes Chatbotkit integration](https://claw-link.dev/hermes/chatbotkit) — ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications.
- [Just One API](https://claw-link.dev/hermes/just-one-api) — Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.