remove.bg integration for AI agents.
remove.bg integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves remove.bg tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.
Real remove.bg actions, managed and audited.
Your user connects remove.bg once; your agent can then secure AI-agent actions — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.
- 1
Your user grants remove.bg access once (OAuth) — the token lands in the vault.
- 2
Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.
- 3
Every routed call appends a hash-chained audit record — nothing leaves your infra.
Supported remove.bg tools.
3 tools are generated from the published remove.bg catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.
Showing 3 tools. All published catalog entries are included in this page's server-rendered HTML.
- Fetch credit balance and free API calls.
- Get the current credit balance and number of free API calls. Notes: * Balance changes may be delayed by several seconds. To locally keep track of your credit balance, you should therefore only call this endpoint initially (or e.g. when the user manually triggers a refresh), then use the `X-Credits-Charged` response header returned with each image processing response to adjust the local balance. * The "*sizes*" field is always "all", is deprecated and will soon be removed.
- Fetch account info
- Post Improve
- Submit an image to the remove.bg Improvement program * Contribute an image that remove.bg is currently not able to remove the background from properly * Help us make remove.bg better * Get better results for similiar images in the future Notes: * By submitting images through the API you agree to the <a target="_blank" rel="noopener" href="/ipc">Improvement Program Conditions</a> * File size: up to 22MB * Input resolution: up to 50 megapixels * up to 100 files per day. <br> Higher rate limits are only available to high-volume solution users; get in touch <a href="/enterprise/contact">here</a>. Requires either an API Key to be provided in the `X-API-Key` request header or an OAuth 2.0 access token to be provided in the `Authorization` request header. Please note that submissions are used on a best-effort basis and the extent of expected improvement varies depending on many factors, including the number of provided images, their complexity and visual similarity. Improvements usually take several weeks to become effective.
- Improvement Program
- Remove the background of an image
- Removes the background of a JPG/PNG/WebP image. * File size: up to 22 MB * Input resolution: up to 50 megapixels * Image source: File upload (binary or as base64 encoded string) or download from URL * Image Content: Any photo with a foreground [(e.g. people, products, animals, cars, etc.)](/supported-images) * Output resolutions available: Preview (up to 0.25 megapixels), Full (up to 25 megapixels), 50MP (up to 50 megapixels) Requires either an API Key to be provided in the `X-API-Key` request header or an OAuth 2.0 access token to be provided in the `Authorization` request header.
- Background Removal
remove.bg integration, answered
- How do AI agents use remove.bg through Open Connector?
- Your user connects remove.bg once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes remove.bg tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
- Is this a remove.bg MCP server?
- Yes. Open Connector can serve remove.bg as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call remove.bg actions with credentials injected server-side.
- Where do remove.bg credentials live?
- In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.
Give your agents remove.bg — keep the keys.
Open source, self-hostable, with remove.bg credentials that never leave your infrastructure. Run it from source today.