ImageToLayers

io.github.jamesknightzhou-archPublished by GitHub account jamesknightzhou-archv1.0.0Updated Oct 25, 2026

Split images into editable layers (PSD/PNG), outpaint images, and generate clean vector SVGs.

The publisher's own server: Layers — workspace for AI agents

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

A remote MCP server that lets an assistant split images into editable layers, outpaint images, and generate clean vector SVGs.

What you can do
Split an image into editable layers, delivered as PSD or PNG files. Outpaint images to extend them beyond their original frame. Generate clean vector SVGs from images. The manifest lists no individual tools, so exact operations are not documented.
When to use it
Useful when an assistant needs to turn a flat image into layered, editable artwork, extend an image's canvas, or convert artwork into vector form for design or print work.
Requirements
A remote endpoint at the provider's site, reached over streamable HTTP. OAuth authentication is required, so the user must sign in to the provider's account. No packages, environment variables or headers are declared.
Before you install
Images are uploaded to a third-party service for processing, so avoid sending confidential or sensitive artwork. OAuth grants the server access tied to your account; review the scopes requested. Outputs such as PSD, PNG and SVG files are generated on the provider's side.

Installation

In SourceWeft

  1. Open ImageToLayers in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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.jamesknightzhou-arch%2Fimage-to-layers/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "imagetolayers": {
      "type": "http",
      "url": "https://www.imagetolayers.com/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 25, 2026

Score

60% 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 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

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

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Layers integrations