Remove.bg

@Remove.bg check my account balance and let me know how many credits I have left for background removal this month.

Your Remove.bg account currently has 47 credits remaining. Your plan renews on the 15th of next month with 50 credits. Based on your current usage pattern (averaging 8 removals per week), you should have enough credits to last through the renewal date without needing to purchase additional credits.

This example shows the Get Account tool paired with AI reasoning to contextualize your credit balance. Requires a valid API key with account read permissions. The MCP returns raw credit counts; the AI interprets usage trends based on your Space's history.

@Remove.bg remove the background from the product photo I just uploaded (coffee-mug-hero.jpg) and save it as a PNG with transparency.

Background removed successfully from coffee-mug-hero.jpg. The processed image has been saved as coffee-mug-hero-nobg.png with full transparency. The original image was 2400×1800px; the output maintains the same resolution. This removal consumed 1 credit from your account (46 credits remaining).

This demonstrates the core Remove Background tool. Each removal consumes one API credit regardless of image size. The MCP requires the image to be accessible via URL or base64-encoded; file handling depends on your Switchy Space's file upload capabilities. Output format defaults to PNG with alpha channel.

@Remove.bg process all five product images in the /assets folder, remove backgrounds, and tell me which ones had complex edges that might need manual cleanup.

Processed 5 images from /assets (consumed 5 credits, 41 remaining). All backgrounds removed successfully. Two images flagged for review: sneaker-side-angle.jpg has fine mesh texture along the toe that may show slight edge artifacts under close inspection, and plant-pot-ceramic.jpg has a glossy surface with reflections that created minor halos. The other three images (lamp-base.jpg, book-stack.jpg, mug-handle.jpg) have clean, high-confidence edges suitable for direct use in your product catalog.

This example combines batch processing with AI quality assessment. The MCP performs removals sequentially; the AI analyzes confidence scores or edge complexity from the API response to surface potential issues. Useful for e-commerce workflows where edge quality matters. Be aware that batch operations consume credits quickly.

When Remove.bg beats manual editing for product catalogs

A 3-person Shopify store team uploads 40-60 product photos per week and needs clean white backgrounds for consistency. Remove.bg's MCP wins here because the AI agent can batch-process uploads during a Slack thread review without opening Photoshop. The account-info tool lets the agent check credit balance before running a large batch, preventing mid-job failures. This setup works until you hit photos with complex edges (lace, hair, glass) where the auto-removal creates artifacts—at that threshold, you're back to manual touch-up. If 80% of your catalog is solid objects on simple backgrounds, route the workflow through Switchy and let the MCP handle first-pass background removal.

Why this MCP is overkill for one-off graphics

A solo content marketer needs a transparent-background headshot for an Instagram carousel once every two weeks. Remove.bg's MCP doesn't justify the setup cost here—the web UI is faster for single images, and the API key adds auth overhead Switchy can't amortize across infrequent use. The MCP makes sense when the marketer scales to a 5-person team running weekly campaigns with 15-20 images per drop, where the agent can pull images from a shared folder, strip backgrounds in parallel, and hand off PNGs to the design tool. Below that volume, the manual workflow is simpler and the credit spend is easier to track outside an AI agent.

When batch background removal scales new-hire workflows

An 8-person HR team onboards 12-20 employees per month and needs uniform headshots for the internal directory and Slack. Remove.bg's MCP integrates into Switchy so the agent can process a batch of submitted photos during onboarding review, apply a consistent background color, and output files named by employee ID. The account tool prevents the workflow from stalling mid-batch when credits run low. This breaks down if your company requires specific brand guidelines for background gradients or lighting—Remove.bg outputs solid colors or transparency, not custom composites. If your onboarding cadence is under 5 people per month, the per-image web workflow is less brittle than maintaining the MCP connection.