Textile Designer AI

ai.textile-designerPublished by textile-designer.aiv0.1.2Updated Oct 26, 2026

Textile design AI: print-ready upscaling, seamless repeats, colourways, screen separation.

VerifiedSTDIODesktop onlyFiles & StorageMedia & Design

Overview

AI-generated overview

Runs Textile Designer AI tools on local image files from an assistant: print-ready upscaling, seamless repeats, colourways and screen separation.

What you can do
  • Upscale images to print-ready resolution and apply Super Scaler
  • Create seamless repeats in block, half brick and half drop layouts
  • Remove backgrounds and watermarks, and extract prints from garment photos
  • Generate colourways and apply colour and object layering
  • Separate designs into multichannel PSD screens and vectorize artwork
  • Apply 3D and embroidery effects, sketch-to-design, design generation and spec boards
When to use it
Useful for textile and surface-pattern designers who want an assistant to prepare print files, build repeats, recolour artwork or split designs into screens without leaving the chat. It also answers questions about which tool fits a given print workflow.
Requirements
A Textile Designer AI account with credits or a plan, signed in through a device-code browser flow. Node.js 18 or newer, since the server is started with npx from the npm package. Network access to the Textile Designer AI service for processing and result downloads.
Before you install
Processing consumes account credits and may cost money; prices are shown only when asked. The images you choose to process and their settings are sent to the vendor's service, and results are kept in your account Library. A session token is stored in a local session file; use logout to remove it. The server also reads the file list of the input image's folder and your account email, organisation, credit balance and plan.

Installation

In SourceWeft

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

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Textile Designer AI for Claude

[Textile Designer AI]

Run the Textile Designer AI design tools from Claude on the image files on your computer: print-ready upscaling, seamless repeats (block, half brick, half drop), Super Scaler, background and watermark removal, Dress to Design (extract the print from a garment photo), Colourways, Colour and Object Layering, Channeling (screen separation into a multichannel PSD), Vectorizer, 3D and Embroidery effects, Sketch to Design, Design Generation, Spec Board and more.

Results are saved as files next to your input image, and Claude shows you a preview, the file paths and the credits used.

What you need

  • A Textile Designer AI account with credits or a plan: sign up.
  • Node.js 18 or newer (the plugin starts the server with npx).

Install

Claude directory: search for Textile Designer AI and install it.

Claude Code, from this repository:

/plugin marketplace add ScientiaAI/textile-designer-ai-claude/plugin install textile-designer-ai@textile-designer-ai

Any MCP client without the plugin (Claude Desktop config, Codex, Cursor, VS Code): run npx -y @textile-designer-ai/mcp. Setup snippets for each client are in the package README.

Using it

Ask Claude in plain words, for example:

  • "Connect to Textile Designer AI."
  • "Make a half-drop repeat of C:\designs\paisley.png at 300 dpi."
  • "What would Dress to Design cost on dress.jpg with 2 outputs?"
  • "Upscale floral.png 4x, then separate it into 8 screens."

When a tool has modes or settings you have not chosen, Claude asks you, one question at a time, with the recommended option preselected. Nothing is uploaded or charged until you answer, and prices are shown only when you ask.

Ask Claude things like "which tool should I use for a screen print?" or "how is Ready to Print different from Super Scaler?": it answers from the built-in Textile Designer AI guide.

What this plugin runs and sends

  • It runs the MIT-licensed MCP server @textile-designer-ai/mcp on your computer, pinned to an exact version.
  • It sends only the images you ask it to process, and the settings for that run, to https://www.textile-designer.ai, and downloads the results from Textile Designer AI's storage. It sends nothing else and runs nothing in the background.
  • Your login is a device-code sign-in in your browser. The session token is stored in ~/.textile-designer/mcp-session.json, readable only by you, and is never shown in chat.
  • It also reads the list of image files in the input image's folder, only to count them for an optional one-time Image Search tip.
  • It reads your account's email, organisation, credit balance and plan from Textile Designer AI only to show them to you and to apply your plan's rules. Nothing is shared with anyone else.
  • Images and results you process are kept in your Textile Designer AI account Library, as described in the privacy policy below. Run logout to remove the stored session.

Links

Security

To report a security vulnerability in this plugin or the MCP server, write to us through https://www.textile-designer.ai/contact with "Security" in the subject. We acknowledge reports and fix confirmed issues in a new pinned release.

License

MIT, Copyright (c) 2026 Scientia AI Private Limited.

Source: README.md at commit 8f239bb

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestOct 7, 2026

Score

50% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts