Claycut

io.github.vincentzhang15Published by GitHub account vincentzhang15v1.2.4Updated Oct 26, 2026

Custom transparent PNG icons in your project's style, added by your coding agent. Free starter set.

VerifiedStreamable HTTPWeb executableDeveloper ToolsMedia & Design

Overview

AI-generated overview

Claycut lets a coding assistant find free transparent PNG icons or generate and edit custom app icons in a project's own style, returning download URLs.

What you can do
  • Find free ready-made transparent PNG icons from the Claycut catalogue, no key required
  • Generate a custom transparent PNG app icon or UI illustration in the project's style, following a CLAYCUT.md style guide
  • Look up icons the account already generated or edited so they can be reused
  • Edit a single detail of an existing icon while keeping the rest unchanged
When to use it
Useful when a coding agent needs app icons or UI illustrations for a project and should match an existing house style, or when you want to reuse an icon already in your Claycut account instead of paying for a new one.
Requirements
Remote endpoint at claycut.dev; no local install. An optional Authorization header with a bearer key from the Claycut app; the free icon set works without a key, while generating and editing icons need a paid key.
Before you install
The Authorization header carries a secret API key. Generating and editing icons require a paid key and consume paid credits, so check existing icons first. The server returns download URLs for generated assets, and the style guide file is read from the repository root.

Installation

In SourceWeft

  1. Open Claycut in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.vincentzhang15%2Fclaycut/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "claycut": {
      "type": "http",
      "url": "https://claycut.dev/mcp"
    }
  }
}

Tools

4

find_free_icon

Find a free, ready-made transparent PNG icon from the Claycut catalogue. No API key needed. The free set only comes in the clay, editorial and plush house styles, so use it when the project's CLAYCUT.md style is one of those (or the user has no key); otherwise it won't match the project. Returns download URLs for matches, or the full list of available words.

Parametersstyleconceptrequired

generate_app_icon

Generate a custom transparent PNG app icon or UI illustration of any subject, in the project's own style. Needs a paid Claycut key. Returns a download URL for the finished asset. Every icon in a project follows one style guide, CLAYCUT.md at the repo root. Before the first call: 1. If CLAYCUT.md exists, use its style line exactly as written (don't reword it) and skip to step 5. 2. Otherwise read the project's design system: design docs, Tailwind config, CSS variables and theme tokens, brand colours, fonts, existing icons and illustrations. If there is none, work out what the project is for and who uses it (README, package.json, landing copy, routes) and invent a style that suits it. 3. Write the style line (at most 300 characters): rendering technique, material, shape language, palette as colour names, lighting, level of detail. It must describe a single solid object that a background remover can cut out: no scenes, no near-white or glassy subjects, no hairline-only line art, no text. Don't mention subject, background or composition; Claycut adds those. Only use a house style (clay, editorial, plush) if it genuinely fits the project, never as a fallback. 4. Create CLAYCUT.md with: a '## Style line' section holding the exact line, why it fits (palette, material, tone and the files it came from), and an '## Icons' list. Generate one representative icon, show it to the user and adjust the line until they approve it. 5. Call with style "custom" and style_description set to that line (or the house style name if CLAYCUT.md names one), then add each icon to the '## Icons' list as concept -> file path. Check that list before generating (and find_my_icon for icons this account made in other projects), and reuse one that already exists.

Parametersstyleconceptrequiredstyle_description

find_my_icon

Find icons this Claycut account already generated or edited, so you can reuse one instead of paying for a new generation. Needs a Claycut key; free. Check here before generate_app_icon. Returns concept, style, date and download URL for matches, or the account's recent icons if nothing matches.

Parametersconcept

edit_app_icon

Change one thing about an icon that is almost right, keeping everything else as it is. Needs a paid Claycut key and costs one icon. Returns a download URL for the edited transparent PNG. Use it instead of generate_app_icon when the user likes an icon but wants a detail fixed: a new generation redraws the whole object and loses what they liked. Pass the icon's URL (a Claycut asset URL, or any public PNG) and a short instruction. Up to three changes per call; describe the end state to draw ("the grey plate behind the star becomes clear violet crystal"), not what to remove. Name what must not change if it's at risk. Always edit the original, not a previous edit, and add the result to the '## Icons' list in CLAYCUT.md.

Parametersimage_urlrequiredinstructionrequired

Version history

1
  1. v1.2.4LatestOct 20, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.