Skip to main content
Glama
holocode-ai

Rembg MCP Server

by holocode-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

rembg-p

Process entire folders of images to remove backgrounds automatically. Supports various AI models for precise segmentation with options like alpha matting and mask-only output.

Instructions

Remove backgrounds from all images in a folder

Input Schema

TableJSON 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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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.

Deploy Server

Other Tools