image-generation-mcp

MCPcommunity
v1.12.1io.github.pvliesdonkUnknownUpdated 1mo agoGitHub

MCP server for AI image generation via OpenAI, Stable Diffusion (SD WebUI), or placeholders.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1GitHub stars
1mo agoLast update
Reads these credentials
  • IMAGE_GENERATION_MCP_OPENAI_API_KEYAPI keyoptional

    OpenAI API key. Enables the OpenAI provider (gpt-image-2, gpt-image-1.5, dall-e-3) when set.

  • IMAGE_GENERATION_MCP_GOOGLE_API_KEYAPI keyoptional

    Google API key. Enables the Gemini provider (gemini-3.1-flash-image and others) when set. Get a key at https://aistudio.google.com/apikey.

  • IMAGE_GENERATION_MCP_BEARER_TOKENAPI keyoptional

    Single shared bearer token; enables bearer auth unless `bearer_tokens_file` is set, which takes precedence.

  • IMAGE_GENERATION_MCP_OIDC_CLIENT_SECRETOAuth appoptional

    OIDC client secret registered with the provider.

  • IMAGE_GENERATION_MCP_OIDC_JWT_SIGNING_KEYAPI keyoptional

    Signing key for issued JWTs; used in oidc-proxy mode only. When unset, the key is derived deterministically from `oidc_client_secret`, so tokens survive a restart — but rotating that secret…

  • IMAGE_GENERATION_MCP_OIDC_VERIFY_ACCESS_TOKENAPI keyoptional

    Validate the access token instead of the id token.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.pvliesdonk
LicenseUnknown
Version1.12.1
Sourcemcp-registry
GitHubpvliesdonk/image-generation-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scan✓ Cleanv1.12.0 · 1mo agoHow well does this scan work?
EvalsNone
IndexedJun 18, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

No tool declarations found in the source1mo ago

Forge read 2 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

MCP server for AI image generation via OpenAI, Stable Diffusion (SD WebUI), or placeholders.

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.

Topics

Related in images, video & audio