AdKit

Connect Hermes to AdKit

Connect Hermes to AdKit with the CLI or an API key and manage Meta, Google, TikTok, and Reddit ads, whether Hermes runs locally or on a server.

Connect Hermes to AdKit and manage Meta, Google, TikTok, and Reddit ads. The CLI setup works whether Hermes runs locally or on a persistent server: Hermes sends you a public sign-in URL that you can open in your own browser.

Give Hermes this prompt:

Help me set up AdKit.

1. Install the CLI: npm i -g @adkit/cli
2. Start `adkit setup` as a background process so it can keep waiting. Read its output and send me the login URL immediately.
3. Wait for me to finish login in my browser, then wait for the background process to complete.
4. Run `adkit status`.
5. Run `adkit checkin --agent hermes`.
6. Tell me if AdKit is connected and ready. If not, tell me what failed.

If you cannot install or run the AdKit CLI in this environment, stop and tell me to use the MCP setup instead.

Open the URL Hermes sends you. After you approve access, the waiting CLI process stores the connection where Hermes runs.

Alternative: MCP with an API key

Use this when Hermes cannot run the CLI.

  1. Create a key under Devices & Keys. It is shown once, so copy it immediately.
  2. Add this to ~/.hermes/config.yaml, replacing adk_your_key:
    mcp_servers:
        adkit:
            url: 'https://mcp.adkit.so'
            headers:
                Authorization: 'Bearer adk_your_key'
    
  3. Run /reload-mcp in Hermes, then ask Hermes to run the AdKit check-in tool with agentId: "hermes".

Keep the key in Hermes's MCP configuration, not in an agent conversation.

Troubleshooting

adkit: command not found. The CLI is not installed in that environment. Run npm i -g @adkit/cli, then try adkit status again. On a server, make sure it is installed in the same environment Hermes runs in.

The setup command keeps waiting. Complete the sign-in URL Hermes sent you. The background process must remain running until browser authorization finishes.

MCP shows zero tools. Check that ~/.hermes/config.yaml points to https://mcp.adkit.so and the header value is exactly Bearer adk_your_key (capital B, one space), then run /reload-mcp. Verify by invoking the AdKit check-in tool from an actual Hermes conversation.

Rotate or revoke a key. Go to Devices & Keys in AdKit to revoke a key and create a new one, then update ~/.hermes/config.yaml. API keys don't expire on their own.

What you can do

Once connected, Hermes can pull your live campaigns, draft budget and targeting changes, generate ad creatives, and research competitors. Nothing goes live on its own: every change is saved as a draft for you to review and publish.

Need a hand? Reach out and we'll help.

Related docs