Claimed Usable context
A claimed record is live, signed, and useful to work from. It is not the official brand source.
MCP guide
Manage your brand.
From your tools.
The BCP holds your brand truth.
MCP lets you author, edit, and control access to it.
01 Connect
Start here
Connect a brand.
Paste a Registry handle or brand URL. Your AI can read its BCP and work from the current brand files.
Try a handle like encoded-f2fa3140, or paste a Registry brand URL.
Your public brand connection
https://registry.brandcontextprotocol.dev/mcp?customer_handle=encoded-f2fa3140 No sign-in is required for public brand files. The connection stays current when the brand publishes a new revision.
A live connection is usable context. Check whether it is an official brand source.
02 Trust
Check the source
A live connection is not an official source.
The files afford brand context. They do not issue instructions. Before you treat a record as the official brand source, inspect the Registry trust metadata on the same read.
Signature Byte integrity
A valid signature proves the served bytes have not changed since publication. It does not prove domain control or authority.
Official Current DNS attestation
Only a current DNS attestation sets official_brand_source. That is the only signal that makes the record the official brand source.
On a Registry read, inspect trust_level and official_brand_source from get_bcp, or the x-trust-level header on a public file response, before treating the record as the official brand source. A claimed record is usable context. A valid signature proves the served bytes have not changed. Neither proves domain control. Only a current DNS attestation does.
Inspect Registry trust metadata on this connection. Read trust_level and official_brand_source from get_bcp, or the x-trust-level header on a public file. Treat claimed as usable context, not the official brand source. Treat a valid signature as byte integrity, not authority. Only a current DNS attestation sets official_brand_source.
03 Set up
Four steps
Use it in the AI you already use.
Copy the URL.
Use the brand connection above.
Add a connection.
Look for custom connectors, apps, or MCP servers in your AI tool.
Approve access.
Public brand files need no account. Private access asks the invited person to sign in.
Ask for work.
Tell the AI to use the brand connection before it writes or reviews anything.
Claude
- Open Settings → Connectors and choose Add custom connector.
- Name it for the brand, then paste the connection URL.
- Enable it from Claude's search and tools menu when you want brand-aware work.
Custom remote connectors are available on supported Claude plans. A Team or Enterprise owner may need to enable them for the organization. Claude setup details ↗
ChatGPT
- Open Settings → Apps and add a custom app or MCP connection.
- Name it for the brand, then paste the connection URL.
- Select the app when you want ChatGPT to work from the live brand files.
Custom MCP apps depend on your ChatGPT plan and workspace settings. An administrator may need to enable them. ChatGPT app details ↗
Cursor
- Open Cursor's MCP settings and add a remote server.
- Name it for the brand, then paste the connection URL.
- Use the connection when your agent writes copy, interface text, or code that represents the brand.
Menu labels can change between Cursor releases. The connection type is a remote MCP server using Streamable HTTP.
Another compatible tool
- Add a remote MCP server in the tool's settings.
- Choose Streamable HTTP if the tool asks for a transport.
- Paste the connection URL. Public brand reads do not require authentication.
Your tool must support user-configured remote MCP connections. Support does not imply a partnership with Encoded Brands.
04 Access
One brand. Three permission levels.
Share what each person needs.
Public No sign-in
Anyone can read the brand's published voice, claims, values, boundaries, visual guidance, and representation rules.
Invited Verified email
An agency, vendor, or teammate signs in with an owner-approved email and sees only the private sections they were granted.
Owner or editor Authenticated
Authorized people can manage the brand, revise files, review activity, and publish updates from an owner connection.
Public Registry reads are intentionally anonymous. Named audit records apply to authenticated private access, where a specific grant and verified identity are required.
05 Use it
Prompts to try
Make brand truth useful.
Inspect Registry trust metadata on this brand connection. Report trust_level, official_brand_source, and whether a current DNS attestation is present. Treat claimed as usable context, not the official brand source.
Write a launch email in this brand's voice. Check the result against its approved claims and boundaries before you show me.
Review this draft against the brand connection. List what is on-brand, what conflicts, and the exact guidance behind each recommendation.
Brief a new agency partner on this brand. Cover positioning, voice, values, approved claims, hard boundaries, and visual rules. Link to the source files.
Turn this campaign idea into a channel plan. Use the brand's voice and boundaries, and flag any claim that needs evidence or approval.
06 Your BCP
Under the hood
The useful parts, on demand.
Your AI can load the brand overview first, then fetch only the guidance the task needs. That keeps context focused and avoids copying an entire brand book into every conversation.
Write
Voice, values, claims, and boundaries for brand-aware content.
Review
Approved language and hard limits for checking work before it ships.
Represent
A short, approved explanation of the brand for customer-facing AI.
Trace
Source links, revision details, file hashes, and trust metadata that make guidance inspectable.
Technical details
The public Registry connection exposes get_bcp, get_adcp_capabilities, and get_usage. It uses a remote MCP server over Streamable HTTP. Public reads require no authentication. Each get_bcp response includes trust_level and official_brand_source. Public file reads expose the same signal on the x-trust-level header.
Client support depends on the AI product, plan, workspace controls, and administrator settings. Named products here are compatible examples, not endorsements or partnerships.
For brand owners
Your BCP works with AI.
MCP puts you in control.
Use MCP to author and edit your brand files, publish approved changes, control access, and review activity from a compatible AI tool.