get_onbrand_skillLABSCO SUMMARY
Brand rules an agent reads, rather than a PDF nobody opens.
Assets never travel through the conversation: materialize_brand_kit_assets hands back S3 commands and the agent fetches the files itself, which keeps a logo out of the context window. This is a service you run — Postgres, a bucket and an OAuth provider are part of the deal.
What it is
OnBrand by SlideSpeak: an MCP service and dashboard holding governed brand knowledge. It is a standalone service you deploy yourself against an OAuth provider, Postgres and an S3 bucket.
What you get
- Seven tools
- The OnBrand skill, explaining what the service holds and how to use the rest — get_onbrand_skill
- Brand Guides listed, and one fetched with its Brand Kit tokens, asset handles and Presentation Kit guidance — list_brand_guides, get_brand_guide
- S3 download commands for Brand Kit assets such as logos and decorative files — materialize_brand_kit_assets
- The authoring skill for a new guide, and upload commands for new logo and decorative files — get_brand_guide_writer_skill, prepare_brand_guide_asset_uploads
- A Brand Guide created or replaced from uploaded asset references and design guidance — write_brand_guide
- A dashboard at /dashboard on the same origin as the MCP endpoint
Requirements
Bun, Docker Compose, an OAuth provider issuing JWT access tokens for the OnBrand resource, Postgres and an S3-compatible bucket. DATABASE_URL, BASE_URL, OAUTH_ISSUER, OAUTH_JWKS_URL, OAUTH_AUTHORIZATION_ENDPOINT, OAUTH_TOKEN_ENDPOINT, OAUTH_DASHBOARD_CLIENT_ID, DASHBOARD_SESSION_SECRET, AWS_S3_BUCKET_BRAND_KIT_ASSETS, AWS_REGION and AWS credentials are all required. Read tools want the onbrand:read scope, writes want onbrand:write.
Setup effort
One command plus a key — claude mcp add --transport http onbrand http://localhost:8080/mcp, then supply credentials
USE CASES
Making a deck that matches the brand
Load the guide with its colour tokens, typography and Presentation Kit guidance before anything is designed, so the constraints are inputs rather than corrections.
Getting the logo files themselves
The tool returns S3 download commands, so the agent pulls the assets directly instead of passing binaries through the chat.
Writing a brand guide from scratch
Read the authoring skill, get upload commands for the logo and decorative files, then create the guide from those references.
Orienting an agent that has never seen the service
One tool returns the skill describing what OnBrand holds and how the other tools fit together, which saves a round of exploratory calls.
7 tools
Listed in project docs. Your client may show a different list.
list_brand_guidesget_brand_guidematerialize_brand_kit_assetsget_brand_guide_writer_skillprepare_brand_guide_asset_uploadswrite_brand_guideBEFORE YOU INSTALL
What to know first
Tools you get
7 tools named in the project's documentation. A token with only onbrand:read cannot use write_brand_guide or prepare_brand_guide_asset_uploads.
Requires
- OAUTH_DASHBOARD_CLIENT_ID in your environment
- AWS_ACCESS_KEY_ID in your environment
- AWS_SECRET_ACCESS_KEY in your environment
INSTALLATION
Connect your client
Server setup
cp .env.example .envEdit .env with your local OAuth provider and S3 credentials.
docker compose up --build
claude mcp add --transport http onbrand http://localhost:8080/mcpOr: codex mcp add onbrand --url http://localhost:8080/mcp && codex mcp login onbrand.
MCP Clients
Claude Code
claude mcp add --transport http onbrand http://localhost:8080/mcpThe configuration on this page does not set OAUTH_DASHBOARD_CLIENT_ID, AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY; the project's instructions put them in a .env file. Check which folder the server reads that file from before you rely on it.
Codex
codex mcp add onbrand --url http://localhost:8080/mcp
codex mcp login onbrandThe configuration on this page does not set OAUTH_DASHBOARD_CLIENT_ID, AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY; the project's instructions put them in a .env file. Check which folder the server reads that file from before you rely on it.