Brivvy MCP

io.github.brivvyHQPublished by GitHub account brivvyHQv0.1.0Updated Oct 24, 2026

Brivvy MCP (OAuth): on-brand AI content, voice rules, templates, glossary.

VerifiedStreamable HTTPWeb executableProductivity & Workflow Knowledge & Memory

Server details

Identifier: io.github.brivvyHQ/mcp
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account brivvyHQ for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.brivvyHQ%2Fmcp.svg)](https://sourceweft.com/mcp/io.github.brivvyHQ%2Fmcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Brivvy MCP is a remote, OAuth-protected server that gives an assistant access to your Brivvy workspace's brand voices, tone rules and content templates.

What you can do: List published voices in your workspace and read the tone and style rules of the default or a chosen voice. List content templates saved in your workspace and fetch the full prompt and instructions for a selected template. Browse public templates from the Brivvy community catalog. The server exposes only these read-style lookups; content generation itself is not listed as a tool.
When to use it: Useful when you want an assistant to write or adapt content in a consistent brand voice, or to pull your saved and community templates into a drafting workflow without copying prompts by hand.
Requirements: A remote Streamable HTTP endpoint reached over the network; no local package. A Brivvy account with workspace access, and an OAuth sign-in completed in the browser (PKCE flow, discovery via well-known metadata). Access tokens are short-lived and refreshed with a refresh token valid for 90 days.

Before you install

OAuth grants the server access to your Brivvy workspace; only one workspace is used at a time, and the last workspace picked on the consent screen applies to every MCP client on the account until you reauthorize. Reconnect when tokens expire rather than reusing old session tokens. Your workspace voices and templates are read by the assistant.

Installation

In SourceWeft

Open Brivvy MCP in the dashboard and add it to a workspace.
Connect the required credentials. They are stored privately and never shown on public pages.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.brivvyHQ%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "brivvy": {
      "type": "http",
      "url": "https://mcp.brivvy.io/"
    }
  }
}

README

Brivvy AI

This repo is your public entry point for Brivvy AI integrations. You get MCP server metadata, install steps, client connection profiles, and release notes.

The implementation stays private. Everything here is safe to publish.

What you connect to

Server type: Remote MCP (Streamable HTTP).
Production URL: https://mcp.brivvy.io.
Auth: OAuth 2.1-style flow with PKCE.
Discovery: Use these before you call the JSON-RPC endpoint:
- https://mcp.brivvy.io/.well-known/oauth-protected-resource.
- https://mcp.brivvy.io/.well-known/oauth-authorization-server.

Tools you can rely on

These tool names are the public contract. Short descriptions match what the hosted server exposes today (see MCP Server for connection guides, security notes, and FAQs).

Area	Tool	What it does
Voices	`list_voices`	Lists published voices in your workspace.
Voices	`get_voice`	Returns tone and style rules for the default or a chosen voice.
Templates	`list_templates`	Lists content templates saved in your workspace.
Templates	`list_discover_templates`	Lists public templates from the Brivvy community catalog.
Templates	`get_template`	Returns the full prompt and instructions for a template you select.

Quick start

Cursor

Add Brivvy as a remote MCP server:

Connect once, then finish OAuth in the browser when the client asks you to.

Claude

Point your MCP connector at:

URL: https://mcp.brivvy.io.
Transport: Streamable HTTP.
Auth: OAuth.

Claude reads .well-known metadata and walks you through consent.

Workspace scope

Your Brivvy account uses one workspace at a time for MCP. The workspace you last picked on the OAuth screen applies to every MCP client until you authorize again and choose a different one. If you run Cursor and Claude side by side, they do not keep separate workspace picks today.

Sessions and reconnection

Your access token stays short-lived. The client should refresh it with your refresh token. Refresh tokens last 90 days (Amazon Cognito). When that window ends, connect again and run through OAuth.

When something breaks

401 on POST /: Normal before OAuth. Your client should follow the WWW-Authenticate hint and complete discovery.
Disconnects right after consent: Check the callback URL, try once more, and make sure you finished the OAuth popup.
Token errors: Reconnect so you get a fresh bearer token. Do not reuse an old web session token.
No tools listed: Your MCP consent or workspace access may be missing or expired.
Wrong workspace: Reconnect and pick the workspace you want on the OAuth screen. That choice applies across all MCP clients on your account.

What lives here

mcp/server.json, registry metadata.
mcp/install/, Cursor and Claude profiles.
VERSIONING.md, how we version this public metadata.
CHANGELOG.md, release notes.
SECURITY.md, how to report issues.

Internal release and directory workflows stay in the private Brivvy MCP repo.

How to reach us

Support: [email protected].
Security: [email protected].

Source: README.md at commit f864d99

Tools

This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

v0.1.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts