Skip to main content
Glama

Rembg MCP Server

An MCP (Model Context Protocol) server for the rembg background removal library. Remove image backgrounds using AI models through Claude Code, Claude Desktop, Cursor, and other MCP-compatible tools.

šŸŽÆ Features

  • šŸ–¼ļø Image Processing: Remove backgrounds from single images or batch process folders

  • šŸ¤– Multiple AI Models: u2net, birefnet, isnet, sam, and more specialized models

  • ⚔ Performance Optimized: Model session reuse for efficient batch processing

  • šŸŽØ Advanced Options: Alpha matting, mask-only output, custom backgrounds

  • šŸŒ Cross-Platform: Support for Windows, macOS, and Linux

  • šŸ”§ Easy Integration: Works with Claude Desktop, Claude Code CLI, Cursor IDE

Related MCP server: Poof Background Removal MCP Server

šŸ“¦ Quick Start

šŸš€ One-Click Installation

Linux/macOS

git clone <repository-url>
cd rembg-mcp
./setup.sh

Windows

git clone <repository-url>
cd rembg-mcp
setup.bat

The setup scripts will automatically:

  • Check Python 3.10+ requirement

  • Create virtual environment

  • Install all dependencies

  • Configure MCP server

  • Test the installation

  • Guide you through AI model downloads

šŸ”§ Manual Installation

If you prefer manual installation or need custom configuration:

  1. Create virtual environment:

python3 -m venv rembg
source rembg/bin/activate  # Linux/macOS
# or
rembg\Scripts\activate.bat  # Windows
  1. Install dependencies:

pip install --upgrade pip
pip install mcp "rembg[cpu,cli]" pillow
pip install -e .
  1. Test installation:

python test_server.py
python validate_setup.py
  1. Download AI models:

./download_models.sh     # Linux/macOS
# or
python download_models.py  # Windows (from activated venv)
  1. For GPU support:

pip install -e ".[gpu]"

šŸ”§ MCP Configuration

Claude Desktop Setup

  1. Find your Claude Desktop config file:

    • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

    • Windows: %APPDATA%\Claude\claude_desktop_config.json

    • Linux: ~/.config/Claude/claude_desktop_config.json

  2. Add the rembg server configuration:

{
  "mcpServers": {
    "rembg": {
      "command": "/path/to/rembg-mcp/start_server.sh",
      "cwd": "/path/to/rembg-mcp",
      "env": {
        "REMBG_HOME": "~/.u2net",
        "OMP_NUM_THREADS": "4"
      }
    }
  }
}
  1. Replace /path/to/rembg-mcp with your actual project path

  2. Restart Claude Desktop

Testing Your Setup

After configuration, test your MCP server:

  1. Start the server manually:

./start_server.sh  # Linux/macOS
# or
start_server.bat   # Windows
  1. Verify MCP connection in Claude Desktop:

    • Look for the rembg tools in your Claude conversation

    • Try a simple command: "List available MCP tools"

  2. Test with a sample image:

    • Ask Claude: "Use rembg-i to remove the background from test.jpg"

    • The server will process your request and return results

Claude Code CLI Setup

Add to your Claude Code settings:

{
  "mcpServers": {
    "rembg": {
      "command": "/path/to/rembg-mcp/start_server.sh",
      "cwd": "/path/to/rembg-mcp",
      "env": {
        "REMBG_HOME": "~/.u2net",
        "OMP_NUM_THREADS": "4"
      }
    }
  }
}

Cursor IDE Setup

Add to your Cursor settings or workspace .cursor/settings.json:

{
  "mcp.servers": {
    "rembg": {
      "command": "/path/to/rembg-mcp/start_server.sh",
      "args": [],
      "cwd": "/path/to/rembg-mcp"
    }
  }
}

Windows Configuration

For Windows users, use start_server.bat instead:

{
  "mcpServers": {
    "rembg": {
      "command": "C:\\path\\to\\rembg-mcp\\start_server.bat",
      "cwd": "C:\\path\\to\\rembg-mcp"
    }
  }
}

šŸš€ How to Use

Once configured, you can use the rembg tools directly in your MCP-compatible application:

Basic Usage Examples

Single Image Processing:

Remove the background from my photo.jpg and save it as photo_nobg.png

Batch Processing:

Process all images in my Photos folder and remove their backgrounds

Advanced Processing:

Use the birefnet-portrait model to remove backgrounds from all portrait photos in my folder, apply alpha matting for better edges, and save them to a new folder

šŸ› ļø Available MCP Tools

rembg-i - Single Image Background Removal

Removes background from a single image file with high precision.

Required Parameters:

  • input_path: Path to the source image file

  • output_path: Where to save the processed image

Optional Parameters:

  • model: AI model to use (default: "u2net")

  • alpha_matting: Improve edge quality (default: false)

  • only_mask: Output black/white mask only (default: false)

Supported formats: JPG, PNG, BMP, TIFF, WebP

rembg-p - Batch Folder Processing

Processes all images in a folder automatically.

Required Parameters:

  • input_folder: Source folder containing images

  • output_folder: Destination folder for processed images

Optional Parameters:

  • model: AI model to use (default: "u2net")

  • alpha_matting: Improve edge quality (default: false)

  • only_mask: Output masks only (default: false)

  • file_extensions: File types to process (default: common image formats)

Features:

  • Automatically finds all supported images

  • Preserves original filenames with .out.png suffix

  • Detailed progress reporting

  • Error handling for individual files

šŸ¤– Supported AI Models

Model

Use Case

Size

Quality

u2net

General purpose (default)

Medium

Good

u2netp

Lightweight version

Small

Good

u2net_human_seg

Human subjects

Medium

Good

u2net_cloth_seg

Clothing segmentation

Medium

Good

silueta

Lightweight general

Small

Good

isnet-general-use

High quality general

Large

Excellent

isnet-anime

Anime characters

Large

Excellent

birefnet-general

High accuracy general

Large

Excellent

birefnet-portrait

Portrait photos

Large

Excellent

birefnet-massive

Massive dataset trained

X-Large

Best

sam

Segment Anything (prompt-based)

Large

Variable

šŸŽÆ Model Recommendations

For beginners: Start with u2net (default) - good balance of speed and quality

For best quality: Use birefnet-general or birefnet-massive

For portraits: Use birefnet-portrait - specialized for human subjects

For anime/cartoons: Use isnet-anime - optimized for animated content

For speed: Use u2netp or silueta - faster processing for batch jobs

šŸ“„ Downloading Models

Models are downloaded automatically when first used, but you can pre-download them:

# Interactive selection (recommended)
./download_models.sh              # Linux/macOS

# Download specific models
./download_models.sh u2net birefnet-portrait

# Download all models
./download_models.sh all

# Windows (from activated virtual environment)
python download_models.py         # Interactive
python download_models.py u2net birefnet-portrait

Models are cached in ~/.u2net/ and only need to be downloaded once.

šŸ”§ Configuration

Environment Variables

  • REMBG_HOME: Model storage directory (default: ~/.u2net)

  • OMP_NUM_THREADS: Number of CPU threads for processing (default: 4)

  • MODEL_CHECKSUM_DISABLED: Skip model checksum verification

Advanced Options

  • Alpha Matting: Improves edge quality but increases processing time

  • Mask Only: Returns black/white mask instead of transparent cutout

  • Custom Background Colors: Replace transparent areas with solid colors

  • Batch Processing: Automatically reuses model sessions for efficiency

šŸ“ Project Structure

rembg-mcp/
ā”œā”€ā”€ rembg_mcp/
│   ā”œā”€ā”€ __init__.py
│   └── server.py                      # Main MCP server implementation
ā”œā”€ā”€ rembg/                             # Virtual environment (git-ignored)
ā”œā”€ā”€ setup.sh                           # Linux/macOS setup script
ā”œā”€ā”€ setup.bat                          # Windows setup script
ā”œā”€ā”€ start_server.sh                    # Linux/macOS server startup
ā”œā”€ā”€ start_server.bat                   # Windows server startup (generated)
ā”œā”€ā”€ pyproject.toml                     # Python package configuration
ā”œā”€ā”€ claude_desktop_config.json         # Claude Desktop config (Linux/macOS)
ā”œā”€ā”€ claude_desktop_config_windows.json # Claude Desktop config (Windows)
ā”œā”€ā”€ test_server.py                     # Installation test
ā”œā”€ā”€ validate_setup.py                  # Comprehensive setup validation
ā”œā”€ā”€ download_models.py                 # AI model download utility (Python)
ā”œā”€ā”€ download_models.sh                 # AI model download script (Linux/macOS)
ā”œā”€ā”€ example_usage.py                   # Usage examples
ā”œā”€ā”€ README.md                          # This file
ā”œā”€ā”€ USAGE_CN.md                       # Chinese documentation
└── CLAUDE.md                         # Claude Code context file

🚨 Troubleshooting

Common Issues

MCP Server Not Found

  • Verify the command path in your MCP configuration

  • Ensure the script is executable: chmod +x start_server.sh

  • Check that the virtual environment exists: ls rembg/

Python Version Issues

python --version  # Must be 3.10+
# If wrong version, install Python 3.10+ and recreate venv

Model Download Problems

# Clear model cache and re-download
rm -rf ~/.u2net

# Re-download models manually
./download_models.sh              # Linux/macOS
python download_models.py         # Windows

# Download a specific model
./download_models.sh u2net        # Linux/macOS
python download_models.py u2net   # Windows

Memory or Performance Issues

# Reduce CPU threads
export OMP_NUM_THREADS=2

# Use lighter models (u2netp, silueta) instead of large ones

Installation Problems

# Clean reinstall
rm -rf rembg/
./setup.sh  # Or setup.bat on Windows

Getting Help

  • Run python validate_setup.py for detailed diagnostics

  • Check server logs when starting manually

  • Ensure your MCP client supports the latest protocol version

šŸ“š Additional Resources

šŸ¤ Contributing

  1. Fork the repository

  2. Create your feature branch (git checkout -b feature/amazing-feature)

  3. Commit your changes (git commit -m 'Add amazing feature')

  4. Push to the branch (git push origin feature/amazing-feature)

  5. Open a Pull Request

šŸ“„ License

This project is licensed under the MIT License - see the LICENSE file for details.

šŸ™ Acknowledgments

  • danielgatis/rembg - The excellent background removal library

  • Anthropic - For the MCP protocol and Claude

  • The open source community for the various AI models

Available Tools

2 tools
rembg-iC

Remove background from a single image file

ParametersJSON Schema
NameRequiredDescriptionDefault
input_pathYesPath to the input image file
output_pathYesPath for the output image file
modelNoModel to use for background removal. Each model is optimized for different use cases.u2net
alpha_mattingNoApply alpha matting for better edge quality
only_maskNoReturn only the mask instead of the cutout

TDQS

C2.8/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description should disclose behavioral traits like file creation, side effects, or performance. It only states the operation without mentioning that it writes to output_path or any other behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence, but it is slightly under-informative. It could benefit from additional context without being verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of an output schema and annotations, the description is incomplete. It does not explain the output format, any return values, or how the tool interacts with files beyond the operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema coverage is 100% with detailed descriptions, especially for the model parameter. The description does not add extra meaning, but the baseline of 3 applies as the schema already provides sufficient semantic context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (remove background) and the resource (single image file). It distinguishes from the sibling `rembg-p` only by name, not explicitly, but the purpose is specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus the sibling `rembg-p` or any other alternatives. No context about prerequisites or ideal use cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

rembg-pB

Remove backgrounds from all images in a folder

ParametersJSON Schema
NameRequiredDescriptionDefault
input_folderYesPath to the input folder containing images
output_folderYesPath to the output folder for processed images
modelNoModel to use for background removal. Each model is optimized for different use cases.u2net
alpha_mattingNoApply alpha matting for better edge quality
only_maskNoReturn only masks instead of cutouts
file_extensionsNoFile extensions to process

TDQS

B3.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden but only states the basic action; lacks disclosure of side effects, error handling, or performance traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence is concise and to the point, though could include a bit more context without being verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Missing output specification, error handling, and file processing details; for a batch tool, users need more context on behavior and results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with detailed parameter descriptions, so the tool description adds no extra semantic value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states 'Remove backgrounds from all images in a folder', using specific verb and resource, which distinguishes it from the sibling rembg-i tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No mention of when to use this tool versus alternatives (e.g., rembg-i for single images), nor any exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

TDQS

B3.2/5.0
Disambiguation5/5

The two tools are clearly distinct: one processes a single image, the other processes all images in a folder. No overlap or ambiguity.

Naming Consistency4/5

Both tools share the prefix 'rembg-' but use different suffixes ('-i' and '-p'). The pattern is somewhat consistent, but the suffixes are not fully explanatory without context.

Tool Count3/5

With only two tools, the server is minimal but covers the basic use cases. The scope is narrow, so the count is borderline appropriate, but lacks additional options like different models or output formats.

Completeness3/5

The server covers single and batch background removal, which are the core operations. However, it lacks other potentially useful features like processing remote URLs, preview, or customizing output, leaving minor gaps.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/holocode-ai/rembg-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server