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.
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.
- 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
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.
One command plus a key — claude mcp add --transport http onbrand http://localhost:8080/mcp, then supply credentials