Mcp Image

io.github.infoinlet-marketplacePublished by GitHub account infoinlet-marketplacev0.1.1Updated Oct 24, 2026

Image generation & editing for AI agents (Runware) — text-to-image, bg removal, upscale.

VerifiedSTDIODesktop onlyMedia & Design

Overview

AI-generated overview

A local MCP server that gives AI assistants image generation and editing through Runware: text-to-image, background removal and upscaling.

What you can do
Generate images from text prompts via Runware text-to-image models. Remove the background from existing images. Upscale images to a higher resolution. All three capabilities are described as image generation and editing for AI agents; no individual tool list is published.
When to use it
Useful when an assistant should produce images from prompts or clean up existing images — cutting out backgrounds or enlarging them — without leaving the chat. Worth adding if your workflow already relies on Runware for image generation.
Requirements
Runs as a local process installed from the npm package @infoinlet/mcp-image over stdio, so Node.js and npm are needed. Desktop only; not executable in a web context. No authentication, environment variables or headers are declared, but Runware image generation normally requires an API key, so expect to supply one.
Before you install
Image generation through Runware is typically billed per operation, so prompts and edits may incur costs. No credentials are declared in the manifest, yet a Runware API key will likely be needed; keep it out of shared configuration. Images you submit for background removal or upscaling are sent to a third-party service.

Installation

In SourceWeft

  1. Open Mcp Image in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.