Image Tools - Background Removal, Upscaling & Face Restoration
Background removal, 4x upscaling, and face restoration via GPU
Background removal, 4x upscaling, and face restoration via GPU
https://apim-ai-apis.azure-api.net/mcp/image/mcpAdd this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"io-github-fasuizu-br-image-tools": {
"url": "https://apim-ai-apis.azure-api.net/mcp/image/mcp"
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
Image Tools - Background Removal, Upscaling & Face Restoration is an MCP server for Background removal, 4x upscaling, and face restoration via GPU. It supports HTTP transport.
Use the generated config in Install. It points your client at the advertised remote endpoint shown on this page.
Choose the Claude Desktop tab in Install, copy the config, and add it to Claude Desktop's MCP server settings. Endpoint: https://apim-ai-apis.azure-api.net/mcp/image/mcp.
Choose the Claude Code tab in Install, copy the config, and add it to Claude Code's MCP server settings. Endpoint: https://apim-ai-apis.azure-api.net/mcp/image/mcp.
Choose the Codex tab in Install, copy the config, and add it to Codex's MCP server settings. Endpoint: https://apim-ai-apis.azure-api.net/mcp/image/mcp.
Choose the Cursor or VS Code tab in Install, copy the config, and add it to Cursor or VS Code's MCP server settings. Endpoint: https://apim-ai-apis.azure-api.net/mcp/image/mcp.
Image Tools - Background Removal, Upscaling & Face Restoration uses HTTP transport. Endpoint: https://apim-ai-apis.azure-api.net/mcp/image/mcp.
Image Tools - Background Removal, Upscaling & Face Restoration inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
Image Tools - Background Removal, Upscaling & Face Restoration does not advertise a verified auth requirement. If discovery fails, it may still need provider login, an API key, a bearer token, or a session header.