Aesthete Agent vs Codesign

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

Aesthete 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.56GoodAuth: no auth requiredCodesign logoCodesignArchitecture & Design · Local subprocess (stdio)A real design engine for your AI agent: generate designs and print-ready PDFs, over MCP.49FairAuth: not declared

Verdict: choose Aesthete Agent for architecture & design work as a local process; choose Codesign 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?

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

Codesign logoChoose Codesign when

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecAesthete Agent logoAesthete AgentCodesign logoCodesign
CategoryArchitecture & DesignArchitecture & Design
Quality signal56/100 · Good49/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars042
Directory activity 0 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Aesthete Agent tools

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

Codesign 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.

Aesthete Agent

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

Codesign

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

Frequently asked questions

Aesthete Agent is categorized under Architecture & Design and uses a local stdio subprocess. Codesign belongs to Architecture & Design and uses a local stdio subprocess. Pick Aesthete Agent for architecture & design work and Codesign 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.

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

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