Rembg MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REMBG_HOME | No | Model storage directory | ~/.u2net |
| OMP_NUM_THREADS | No | Number of CPU threads for processing | 4 |
| MODEL_CHECKSUM_DISABLED | No | Skip model checksum verification |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rembg-iC | Remove background from a single image file |
| rembg-pB | Remove backgrounds from all images in a folder |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools are clearly distinct: one processes a single image, the other processes all images in a folder. No overlap or ambiguity.
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.
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.
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.