Skip to main content
Glama
Brandcode-Studio

brandsystem-mcp

by Brandcode-Studio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Connect to Brandcode Studio

brand_brandcode_connect

Connect a local .brand directory to Brandcode Studio to pull a hosted brand by URL/slug or save and share the local brand with your team.

Instructions

Connect a local .brand/ to Brandcode Studio. Two modes: "pull" (default) downloads an existing hosted brand by URL/slug. "save" uploads the local .brand/ to Studio (requires prior auth via brand_brandcode_auth). THE tool when the user says "make our brand available to my whole team", "share our brand with the team", "connect to Brandcode", "pull from Studio", "save brand to Studio", or "upload my brand". Returns brand name, slug, sync token, and connection details.

Input Schema

NameRequiredDescriptionDefault
urlNoBrandcode Studio brand URL or slug. Required for mode="pull". Examples: "https://brandcode.studio/start/brands/pendium", "pendium"
modeNo"pull" connects to an existing hosted brand and downloads it. "save" uploads the local .brand/ to Studio (requires auth via brand_brandcode_auth).pull
share_tokenNoShare token for protected brands (x-brand-share-token)

Output Schema

NameRequiredDescriptionDefault
_metadataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.17.0
  2. Removedv0.13.4
  3. Changed1 schema field changedv0.11.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "_metadata": {
+      "additionalProperties": true,
+      "properties": {
+        "next_steps": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "what_happened": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "what_happened",
+        "next_steps"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "_metadata"
+  ],
+  "type": "object"
+}
  4. Changed3 schema fields changedv0.9.2
    • addedInput schema / properties / mode
      Added value: +{
+  "default": "pull",
+  "description": "\"pull\" connects to an existing hosted brand and downloads it. \"save\" uploads the local .brand/ to Studio (requires auth via brand_brandcode_auth).",
+  "enum": [
+    "pull",
+    "save"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / url / description
      Previous value: -"Brandcode Studio brand URL or slug. Examples: \"https://brandcode.studio/start/brands/pendium\", \"pendium\""New value: +"Brandcode Studio brand URL or slug. Required for mode=\"pull\". Examples: \"https://brandcode.studio/start/brands/pendium\", \"pendium\""
    • removedInput schema / required
      Removed value: -[
-  "url"
-]
  5. First observedv0.5.0

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare it is not read-only, is open-world, and is destructive=false. The description adds useful behavior beyond annotations: pull downloads an existing hosted brand, save uploads the local .brand/ to Studio, save requires prior auth, and it returns brand name, slug, sync token, and connection details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core action and modes, then provides trigger phrases and return information. The sentences are dense but each adds useful selection or invocation context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter tool with an output schema and annotations, the description covers the important gaps: mode behavior, default mode, auth prerequisite for save, trigger phrases, and return fields. Nothing critical is missing for an agent to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents url, mode, and share_token in detail. The description reinforces the mode semantics and the url requirement for pull, but mostly repeats structured schema information and does not add much about share_token.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: connect a local .brand/ to Brandcode Studio. It clearly distinguishes the two modes and names the related auth sibling, so an agent can distinguish this from general brand tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit user-language triggers such as 'connect to Brandcode', 'pull from Studio', and 'save brand to Studio', and notes that save mode requires prior auth via brand_brandcode_auth. It does not specify when-not to use it or name an alternative connect tool, so it is strong but not fully exhaustive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools