Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.brivvy.io/llms.txt

Use this file to discover all available pages before exploring further.

Claude offers the most seamless integration with Brivvy’s MCP Server across multiple environments. Teams using Claude for content generation can access brand voice guidelines, template instructions and glossary terms without leaving their workflow. The integration works identically in Claude’s web interface and desktop application, ensuring consistent brand application regardless of where content is created. Claude’s web interface and desktop application share the same MCP configuration. Settings configured in one location apply to both environments.
If you prefer video tutorials, check out our YouTube page.

​
Setup

Before your team can use Brivvy, a Claude admin must add it as a custom connector from Organization settings. This makes the connector available for team members to connect their own accounts.
  1. In Claude, click your profile or workspace name and navigate to Organization settings > Connectors.
  2. Scroll to the bottom of the Connectors section and click Add custom connector.
  3. Fill in the following fields:
    FieldValue
    NameBrivvy
    MCP server URLhttps://mcp.brivvy.io
  4. Click Add to save. The Brivvy connector will now appear in your organization’s connector list, ready for team members to connect their own accounts.
  5. Navigate to your individual Settings > Connectors, find Brivvy in the list and click Connect. Complete the OAuth authentication flow to authorize access for your own account.

​
How to know it worked

Send a prompt that requires brand voice context, for example: “Using Brivvy, get the brand voice rules and write a two-sentence product update.” Claude will call the appropriate Brivvy tool and return a response shaped by your brand voice rules rather than a generic output.