Let your AI assistant work in your workspace

Connect an AI assistant — Claude Code, Claude Desktop, Cursor, or any similar tool — so it can work directly inside your workspace with a key you create and control. This lives in the Agent Access tab, and only admins and owners can set it up.

MCP is simply a standard way for AI tools to connect to the apps you use — you don’t need to know anything more about it to follow this guide.

Before you start

• You’re an admin or owner of the workspace. Only they can create or revoke keys — see team roles. If you’re a Member or Viewer, ask an owner or admin to mint one for you.
• You have an AI assistant that supports MCP connections (Claude Code, Claude Desktop, Cursor, and most modern coding and agent tools do).

What this unlocks

With a key you control, your assistant can reach into Vital Root and actually do the work — search your library, read your products and campaign performance, create library items, and start research runs. You decide exactly how much it’s allowed to touch. For example, you can ask your assistant to:

• “Draft five hooks from our best-performing angle and save them to the library.”
• “Which creative drove the most orders yesterday?”
• “Start a research run on magnesium supplement buyers.”

The first needs permission to read and write your library; the second, to read campaigns and analytics; the third, to run research. You grant those permissions when you mint the key.

Open the Agent Access tab

Go to Agent Access in your account settings. The Omnymous MCP card at the top is your workspace’s connection details, and everything below it is the list of keys you’ve created.

The card shows the connection address your assistant points at:

https://api.omnymous.com/mcp

You rarely paste this by hand — when you mint a key, the reveal screen gives you ready-to-paste setup snippets that already include it. Before you’ve created any keys, the list reads No agent keys yet. with a Mint your first key button.

Mint a key

1. Click New agent key (top right), or Mint your first key if this is your first one.
2. Give it a Key name that says which tool and team it’s for, so you recognize it later — for example, Claude — content team.
3. Pick the Scopes — the things this key is allowed to do. Each one is described in plain words:
   • library:read — Search and read Library items — knowledge, variables, assets, folders, compositions
   • library:write — Create, edit, compose, and delete Library items (same guardrails as the app)
   • products:read — Read synced store products and variants
   • campaigns:read — Read campaign structure and performance
   • analytics:read — Read store performance metrics and attribution analytics
   • research:run — Start research runs and read their status
4. Choose an Expiry — Never expires, 30 days, 90 days, or 1 year.
5. Click Mint key.

Scopes that let the assistant change things carry a badge: writes on library:write, and runs jobs on research:run. New keys start with read-only access preselected — grant only what the assistant actually needs, and add library:write or research:run only when you want it to create items or kick off research.

Copy your key — it’s shown once

The moment you mint, the key appears once. Omnymous stores only a scrambled copy, so this screen is the only time you’ll ever see the full key.

• Copy the key and store it like a password — a password manager is ideal. If you lose it, you can’t recover it; you mint a new one.
• The reveal also gives you two ready-to-paste setup snippets: a Claude Code command, and an MCP config block for Cursor, Claude Desktop, custom agents. Paste whichever matches your tool — each already contains the address and your key.
• When you’ve saved it somewhere safe, click I’ve saved my key.

Manage your keys

Every key you’ve minted is listed under Keys, each showing its name, a short prefix (like omny_ak_…), its scopes, when it was Last used, and its status — Active, Expired, or Revoked.

Revoke a key

To cut off a key immediately, click Revoke on its row and confirm. The dialog is blunt about what happens:

Agents using “Claude — content team” (omny_ak_…) lose access immediately. This cannot be undone.

Click Revoke key to confirm. Any assistant using that key stops working right away, and there’s no undo — if you still need that assistant connected, mint a fresh key for it.

Troubleshooting

My assistant says it’s unauthorized. The key was revoked or has expired, or it’s missing the scope for what you asked. Check the key still shows Active in the list. If it’s Revoked or Expired, mint a new one and update your tool. If only certain actions fail — say, saving to the library — the key likely lacks that scope; mint a new key with the scope added (for saving, library:write).

I lost my key. You can’t see a key again after the reveal — it’s shown only once. Mint a new key, update your tool with it, and Revoke the old one so nothing keeps using it.

A teammate needs a key but can’t create one. Only admins and owners can mint keys. Either an owner or admin mints one and hands it over, or they promote the teammate — see team roles.