Connect brandOS MCP · Snyder brandOS

One endpoint · six harnesses · zero credentials

Connect with the client you already use.

brandOS exposes a stateless Streamable HTTP MCP endpoint. Public discovery needs no API key, bearer token, OAuth flow, custom header, local server process, or package installer.

Endpoint: https://brand.snyder.tech/mcp
Transport: Streamable HTTP
Authentication: None
Authority: Public read-only discovery

01 · Harness setup

Copy the configuration for your client

Use the exact HTTPS endpoint. Do not add authorization headers to these public configurations.

Codex

CLI · app · IDE extension

No auth

Configuration ~/.codex/config.toml

codex mcp add brandos --url https://brand.snyder.tech/mcp
codex mcp list

Open /mcp and confirm brandos is enabled.

OpenAI MCP documentation

Claude Code

CLI · project scope

No auth

Configuration .mcp.json

claude mcp add --transport http --scope project brandos https://brand.snyder.tech/mcp
claude mcp get brandos

Open /mcp and inspect the connected tools.

Claude Code MCP documentation

Cursor

Editor · project scope

No auth

Configuration .cursor/mcp.json

{
  "mcpServers": {
    "brandos": {
      "url": "https://brand.snyder.tech/mcp"
    }
  }
}

Open Cursor Settings → MCP and confirm the server and tools.

Cursor MCP documentation

VS Code

GitHub Copilot agent mode

No auth

Configuration .vscode/mcp.json

{
  "servers": {
    "brandos": {
      "type": "http",
      "url": "https://brand.snyder.tech/mcp"
    }
  }
}

Run MCP: List Servers from the Command Palette.

VS Code MCP documentation

GitHub Copilot CLI

Terminal agent

No auth

Configuration ~/.copilot/mcp-config.json

copilot mcp add --transport http brandos https://brand.snyder.tech/mcp
copilot mcp get brandos

Confirm the remote server and its available tools.

GitHub Copilot CLI MCP documentation

Gemini CLI

Terminal agent · project scope

No auth

Configuration .gemini/settings.json

gemini mcp add --transport http --scope project brandos https://brand.snyder.tech/mcp
gemini mcp list

Confirm brandos reports Connected over HTTP.

Gemini CLI MCP documentation

02 · Generic clients

Use the standard transport contract

For any other MCP-compatible agent, choose Streamable HTTP, name the server brandos, and set its URL to https://brand.snyder.tech/mcp. Leave token, OAuth, headers, command, and arguments empty.

{
  "name": "brandos",
  "transport": "streamable-http",
  "url": "https://brand.snyder.tech/mcp"
}

Expected capabilities

JSON-RPC over HTTPS
Tools and resources
No sessions or client-side writes
No inline Office binaries

MCP transport specification

03 · Verify before use

Confirm the narrow public surface

List the connected server and confirm the URL is exactly https://brand.snyder.tech/mcp.

Inspect tools. The server exposes the two Brand CDN tools and only the independently approved Office or presentation discovery subsets below.

Keep per-tool approval enabled. “Read-only” describes the server contract, not your client policy.

Resolve an exact resource and version before downloading any skill, schema, layout, profile, or Office artifact.

brand_cdn_list_brandsbrand_cdn_assetsbrandos_skills_listbrandos_skills_describebrandos_skills_resolvebrandos_skills_install_instructionsbrandos_presentation_resources_listbrandos_presentation_resources_describebrandos_presentation_resources_resolve

04 · Install the portable skill

MCP discovers. Your local harness installs.

Call brandos_skills_resolve for an exact public brand slug.
Review the returned version, immutable URL, byte size, SHA-256, and unsigned status.
Download exactly one inert SKILL.md into a temporary directory.
Verify its byte size and SHA-256, then read the complete file.
Copy it atomically into one local skill root and reload the harness.

Never use curl | sh, npx, source, executable hooks, or a server-returned install command. MCP has no client-filesystem authority.

Read the full Office Artifact Kit and skill integrity contract.

05 · Presentation resources

Discover exact metadata; keep execution local.

Presentation catalog 2.0.0 is independently versioned from Office kits and currently remains staging-only. Its stable identifiers areskill://presentation-authoring/<version>,schema://presentation-deck-ir/<version>,layout://presentation-core/<version>, andbrand://<brand-slug>/<version>. The contract-onlypresentation-manifest://{deckId}/{immutableVersion} template is reserved for separately approved public immutable manifests.

Once one atomic package has approved catalog bytes, an exact readiness marker and manifest, verified file MIME/size/SHA-256 evidence, approved rights and visual review, and trusted publisher signatures, three read-only tools may list, describe, and resolve the inert skill, Deck IR schema, layout catalog, and visual-only profiles. Local staging does not make any body or URL live. MCP never installs, generates, edits, uploads, publishes, mints, or writes these resources.