An MCP server for Cursor to generate, store, and reuse images using Google Nano Banana Pro (better than Antigravity's image tool)
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"gemini-image": {
"env": {
"GEMINI_API_KEY": "your-api-key-here"
},
"args": [
"/path/to/gemini-image-mcp/dist/server.js"
],
"command": "node"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
An MCP (Model Context Protocol) server optimized for web development that enables AI assistants to generate and edit images using Google's Gemini API.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
Packing does not respect root-level ignore files in workspaces
### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up
Incorrect Permission Assignment for Critical Resource in NPM
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
Local Privilege Escalation in npm
Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.
npm CLI exposing sensitive information through logs
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.
npm Vulnerable to Global node_modules Binary Overwrite
Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in ai-ml / design
Persistent memory using a knowledge graph
MCP server for accessing Figma plugin console logs and screenshots via Cloudflare Workers or local mode
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
Official Miro MCP server - Supports context to code and creating diagrams, docs, and data tables.
MCP Security Weekly
Get CVE alerts and security updates for Gemini Image Mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
An MCP (Model Context Protocol) server optimized for web development that enables AI assistants to generate and edit images using Google's Gemini API.
After adding the MCP server to Cursor, just prompt the AI to generate or edit images for you - the agent will do the rest.
git clone https://github.com/yourusername/gemini-image-mcp.git
cd gemini-image-mcp
npm install
npm run build
| Variable | Required | Default | Description |
|---|---|---|---|
GEMINI_API_KEY | Yes | - | Your Google Gemini API key |
GEMINI_IMAGE_MODEL | No | gemini-3-pro-image-preview | Gemini image model to use. Use gemini-2.5-flash-image for the GA model. |
PORT | No | 3001 | Port for the Express static file server |
Add to your ~/.cursor/mcp.json:
{
"mcpServers": {
"gemini-image": {
"command": "node",
"args": ["/path/to/gemini-image-mcp/dist/server.js"],
"env": {
"GEMINI_API_KEY": "your-api-key-here"
}
}
}
}
Add to your MCP server configuration:
{
"gemini-image": {
"command": "node",
"args": ["/path/to/gemini-image-mcp/dist/server.js"],
"env": {
"GEMINI_API_KEY": "your-api-key-here"
}
}
}
Add to your claude_desktop_config.json:
{
"mcpServers": {
"gemini-image": {
"command": "node",
"args": ["/path/to/gemini-image-mcp/dist/server.js"],
"env": {
"GEMINI_API_KEY": "your-api-key-here"
}
}
}
}
Use the MCP Inspector to test and debug your server:
npm run inspect
This will:
Make sure your .env file is set up with GEMINI_API_KEY before running the inspector.
generate_imageGenerate an image from a text prompt, optionally using reference images to guide the style or composition. The AI must determine the correct output path in your project before calling this tool.
| Parameter | Type | Required | Description |
|---|---|---|---|
prompt | string | Yes | Text description of the image to generate |
outputPath | string | Yes | Absolute path where the image should be saved (e.g., /Users/you/project/public/images/hero.png) |
referenceImages | string[] | No | Array of absolute paths to reference images for style/composition guidance |
aspectRatio | string | No | Preset: hero (16:9), square (1:1), portrait (3:4), landscape (4:3), banner (21:9), mobile (9: |