AgentPixel vs Brandsystem MCP
A side-by-side look at the AgentPixel and Brandsystem MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
A
AgentPixelMarketing · Remote HTTP/SSEConsent-first website pixel for AI agents. Your agent sets up a consent bar, installs the tag, verifies it and reads contacts. Hosted remote MCP server at https://agentpixel.io/mcp?src=allmcps (Streamable HTTP). try_sample works with no account or key.53GoodAuth: oauth 2.0Verdict: choose AgentPixel for marketing work over a hosted endpoint; choose Brandsystem MCP for marketing as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
AChoose AgentPixel when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Choose Brandsystem MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You want tools like
brand_start, brand_status, brand_compile.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | A AgentPixel | |
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 53/100 · Good | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Paid service | Not declared |
| Required env vars | None listed | None listed |
Tools & capabilities
AgentPixel tools
No tool names declared yet. Check the project README from the listing page.
Brandsystem MCP tools 12
brand_startAdopt a brand into a portable .brand/ runtime from whatever source already exists: existing brand guidelines (PDF), a website URL, a Figma library, or a hosted Brandcode Studio brand. THE entry point when the user says 'use my existing brand guidelines with AI', 'I have a PDF brand guide', 'use our Figma library', 'create a brand system', 'extract brand from website', or 'set up brand guidelines'. Pass website_url, guideline_pdf, figma_file_key, or brandcode_url — or pass no source and it discovers local candidates and presents a menu with a privacy explanation. Set mode='auto' with a website_url to run the full pipeline (extract, compile DTCG tokens + design-synthesis.json + DESIGN.md + brand runtime + interaction policy, generate HTML report) in one call. If .brand/ already exists, returns current status with next steps. NOT for reading an already-compiled brand (use brand_runtime or brand_context) or for sharing an existing brand with a team (use brand_brandcode_connect).brand_statusCheck brand system progress and get next steps. Shows what has been extracted (colors, fonts, logo), confidence levels, session completion status, and what to do next. Use when resuming a previous session, checking readiness, or when the user asks 'what's the state of my brand?' If no .brand/ exists, returns a full getting-started guide with all available tools. Returns structured status data.brand_compileGenerate DTCG design tokens, design-synthesis.json, DESIGN.md, brand runtime, and interaction policy from extracted brand data. Transforms core-identity.yaml into tokens.json, brand-runtime.json (single-document brand contract for AI agents), and interaction-policy.json (enforceable rules). When Session 2+ data exists, also generates visual-identity-manifest.md and system-integration.md. Use after brand_extract_web, brand_extract_site, brand_extract_visual, or brand_extract_figma. Returns token counts, clarification items, and file list.brand_clarifyResolve an ambiguous brand value interactively. After brand_compile, some values need human confirmation — wrong primary color, unknown font, unassigned color roles. Pass the clarification item ID and the user's answer (hex color, role name, font name, or 'yes'/'no'). Supports natural language: 'the purple one is accent' or '#5544f2 is secondary'. Returns updated identity and remaining clarification count.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
AgentPixel
{
"mcpServers": {
"agentpixel": {
"url": "https://agentpixel.io/mcp?src=allmcps"
}
}
}
Brandsystem MCP
{
"mcpServers": {
"brand-system-brandsystem-mcp": {
"command": "npx",
"args": [
"-y",
"@brandsystem/mcp"
]
}
}
}
Frequently asked questions
AgentPixel is categorized under Marketing and uses a remote HTTP/SSE transport. Brandsystem MCP belongs to Marketing and uses a local stdio subprocess. Pick AgentPixel for marketing work and Brandsystem MCP for marketing.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
AgentPixel is listed as a paid service. Auth: oauth 2.0. Brandsystem MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add agentpixel and brand-system-brandsystem-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, AgentPixel has a quality signal of 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Brandsystem MCP has 65/100 (Great) with 1 views, 0 installs and 15 GitHub stars.
