Codesign vs Aesthete Agent

A side-by-side look at the Codesign and Aesthete Agent MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Codesign logoCodesignArchitecture & Design · Local subprocess (stdio)A real design engine for your AI agent: generate designs and print-ready PDFs, over MCP.49FairAuth: not declaredAesthete Agent logoAesthete AgentArchitecture & Design · Local subprocess (stdio)Mechanically validated frontend aesthetics for coding agents: an evidence-ranked palette library, OKLCH harmony generation, WCAG 2.2 + APCA contrast gates, color-blind simulation and AI-slop detection; installable as an agent skill or MCP server via uvx.51GoodAuth: no auth required

Verdict: choose Codesign for architecture & design work as a local process; choose Aesthete Agent for architecture & design as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Codesign logoChoose Codesign when

  • You need dedicated capabilities in the Architecture & Design domain.
  • You prefer a local stdio subprocess transport.
Explore Codesign

Aesthete Agent logoChoose Aesthete Agent when

  • You need dedicated capabilities in the Architecture & Design domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
Explore Aesthete Agent

Feature & specification comparison

Rows where the two servers differ are marked.

SpecCodesign logoCodesignAesthete Agent logoAesthete Agent
CategoryArchitecture & DesignArchitecture & Design
Quality signal49/100 · Fair51/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingFreeFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars420
Directory activity 1 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Codesign tools

No tool names declared yet. Check the project README from the listing page.

Aesthete Agent tools

No tool names declared yet. Check the project README from the listing page.

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.

Codesign

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "codesign": {
      "command": "npx",
      "args": [
        "-y",
        "@imgly/codesign-mcp@0.5.1"
      ]
    }
  }
}

Aesthete Agent

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "docsor1212-aesthete-agent": {
      "command": "npx",
      "args": [
        "-y",
        "clawhub"
      ]
    }
  }
}

Frequently asked questions

Codesign is categorized under Architecture & Design and uses a local stdio subprocess. Aesthete Agent belongs to Architecture & Design and uses a local stdio subprocess. Pick Codesign for architecture & design work and Aesthete Agent for architecture & design.

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.

Codesign is listed as free. Aesthete Agent is listed as free. Auth: no auth required. 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 codesign and docsor1212-aesthete-agent as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Codesign has a quality signal of 49/100 (Fair) with 1 views, 0 installs and 42 GitHub stars. Aesthete Agent has 51/100 (Good) with 0 views, 0 installs and 0 GitHub stars.