Create Logos and Full Brand Kits Inside Claude: A Practical Guide to the Zoviz MCP Server

If you build side projects, you know the drill. The code is done, the product works, and then you lose an entire evening making a logo, an OG image, and social banners in a design tool you barely know.

The Model Context Protocol (MCP) has quietly fixed this category of problem. Since Anthropic open sourced MCP, a growing ecosystem of servers lets AI assistants talk to real services. Zoviz, an AI branding platform, now ships an MCP server that turns your assistant into a working design partner. Here is what it does and how to set it up.

What is MCP, in one minute

MCP is an open standard that connects AI assistants to external tools. Instead of copying context back and forth between apps, the assistant calls tools directly: it can query a database, read a repo, or in this case, generate brand assets. A server exposes capabilities, the client (Claude, Cursor, Windsurf, Perplexity and others) discovers them, and you just talk.

What the Zoviz MCP server can do

Once connected, your assistant gets a toolbox for branding work:

• Logo generation with SVG and PNG exports, transparent backgrounds included
• Brand identity packages: color palettes, typography, and brand guidelines
• Image generation for product shots, hero banners, and illustrations
• Image editing: refine, recolor, crop, or extend existing assets
• Social media assets sized for Instagram, LinkedIn, and X
• Ad campaign materials such as display banners and carousel cards
• SEO metadata: OG images, alt text, and schema.json
• Print ready bundles with brand guidelines

The point is not any single tool. It is that the whole flow happens in one conversation, with your project context already loaded.

Setup in Claude (about two minutes)

1. Open Settings → Connectors in Claude Desktop or claude.ai
2. Add a custom connector named Zoviz and paste the MCP URL: https://mcp.zoviz.com/mcp
3. Click Add, then Connect, and sign in with your Zoviz account

You authenticate once and the connection is reused across environments, which is handy for teams that keep MCP configuration in a repository. The server also works with Cursor, Windsurf, Perplexity, and other hosts that implement the protocol; availability varies by client and release channel, so check your client's MCP settings.

A typical workflow

You describe what you want in plain language:

Create a logo for "Vaultr": trustworthy, modern, minimal. Bold sans serif, vault door icon.

And a moment later you get real deliverables:

✓ logo.svg
✓ brand-guide.pdf
✓ og-image.png
✓ schema.json

From there you can iterate conversationally: "make the icon rounder", "give me a dark mode variant", "export a 1200x630 OG image for the landing page".

Where this fits in a developer workflow

• Shipping a landing page. Generate the logo, favicon, OG image, and schema metadata while you write the copy, without opening a design tool.
• Hackathons. A believable brand in minutes buys your demo a lot of credibility for very little time.
• Freelance and client work. Spin up brand concepts during a call, then refine the direction the client likes.
• Indie products. Keep visual consistency across your app, socials, and store listings from one brand source.

Good to know

MCP access is included in Zoviz subscriptions, which start at $29 per month, so there is no separate API bill to track. Your prompts and assets stay within the tools you already use, and teams with stricter requirements can look at enterprise deployment options.

Wrap up

MCP is turning assistants from advisors into operators, and branding is a surprisingly good fit for it. If design work is the tax you pay to ship, this setup shrinks it to a conversation.

Full setup details and pricing live on the Zoviz MCP page. If you try it, I would love to hear what you build - drop a comment below.