Give your first agent the right brand context.

Create a client and its brand.

A client is the organization you work with. A brand is the business, product, or property with its own positioning, voice, and accounts.

In the app, open Clients → New client. Leave Create a first brand selected for a typical single-brand client. Give the brand a different name if needed. For a parent company whose brands you will add later, clear that option.

Start with one brand you know well. You can add more when you have checked the first workflow.

Add the context you want reused.

Open the brand and find Brand Knowledge → Add knowledge. Write a short brief in the editor, then choose Save knowledge. You can use plain text or Markdown.

Use the full brand brief template if you need more structure. Brand Knowledge is one maintained document per brand; saving a change creates a new version.

Add a Playbook when you have a recurring process to document. Use Platforms for account and asset identifiers, relationships, and brand assignments. Registering those details does not connect the external provider.

Decide whether the agent should write.

Every active MCP key can read the whole workspace, including every client and brand. Choose a connection you trust with that scope.

Owners and admins can still edit through the app. Allowed memory changes apply directly; there is no approval queue. A write setting controls Agency Memory records, not advertising permissions or spending.

Create a named MCP key.

Open Agent access → Create MCP Key. Enter the user’s name, an optional email, and a label that identifies the connection, such as “Alex — laptop agent.” In Agency mode, check whether Can edit memory should be enabled before creating it.

Copy the full key when it is shown. The saved key record keeps a hash and an identifying prefix; it cannot reveal the original secret later. Store it privately. Create a separate key for each person or connection so you can identify and revoke it independently.

If you leave the screen and no longer have the secret, create a new key for the connection and revoke the superseded key after updating your agent.

Choose your agent and check the connection.

In Agent access, choose Claude Desktop, Claude Code, Codex, Cursor, or Other. Select an active MCP key created during your current visit, then choose Copy prompt. The prompt includes the full key: share it only with the agent you intend to connect.

The app supplies the MCP URL and the client-specific instructions. Follow them, preserve any existing server configuration, and restart or reload your agent when prompted.

Compatibility depends on the client supporting the required transport and authorization header. A web chat that only supports OAuth is not interchangeable with this connection.

An empty list can be a valid result for an empty workspace. Saved settings or a discovered tool list alone do not prove that a request succeeded.

Use the brief in one real task.

Once the connection works, ask your agent to retrieve the brand you prepared and draft something you already know how to review.

Check the brand, offer, claims, and tone against the brief you saved. Keep the setup focused on one useful output before adding more clients or tools.

Your first milestone is a successful context retrieval used in real work. The next is being able to repeat it in a fresh conversation without rebuilding the brief.