Gemini configure

Skill 2901were/gemini-creative-plugin/skills/gemini-configure

This skill should be used when the user asks to "configure the Gemini API key", "set up GEMINI_API_KEY", "troubleshoot Gemini authentication", "fix MCP not configured errors", "check Gemini API key status", "the API key isn't working", or otherwise needs API-key setup or auth troubleshooting specifically for the gemini-creative-plugin. Covers the three configuration methods (env var, config file, configure_gemini_token tool), priority order, and diagnostic checks via get_configuration_status.From its SKILL.md

Install

npx -y skills add 2901were/gemini-creative-plugin --skill gemini-configure

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.5 KB, as published. Nobody here has run it

Gemini MCP Configuration Guide

Set up the Gemini Creative Plugin from scratch or troubleshoot configuration issues.

Step 1: Check Current Status

Always start here:

get_configuration_status()

Returns one of:

✅ Configured via environment variable — best option, nothing to do
✅ Configured via config file — working, but less secure
❌ Not configured — follow setup below

Configuration Methods (Priority Order)

The server checks these in order — highest priority wins:

1. Environment Variable (Recommended)

Most secure. Set once, works across all projects.

# Add to ~/.zshrc or ~/.bashrc
export GEMINI_API_KEY="your-key-here"

# Reload shell
source ~/.zshrc

Then restart Claude Code / the MCP server.

2. Config File (Persistent, less secure)

Saved to .gemini-creative-config.json in the MCP directory. Good for project-specific keys.

configure_gemini_token({ apiKey: "your-key-here" })

Note: This file should be in .gitignore — never commit API keys.

3. Manual (Session only)

Use the same configure_gemini_token tool. Configuration is lost when the MCP server restarts. Only use for temporary testing.

Getting an API Key

Go to Google AI Studio
Sign in with your Google account
Click Create API Key
Copy the key — store it securely

Free tier: Check current pricing — limits vary by model.

Troubleshooting

"API key not configured" → Run get_configuration_status() to confirm the issue, then use one of the 3 methods above.

"No previous image found" → continue_editing and get_last_image_info require at least one image generated in the current server session. Generate one first with generate_image.

Images not appearing / generation failing → Check that GEMINI_API_KEY is set in the environment Claude Code was launched from (not just your terminal). Restart Claude Code after setting the env var.

"Maximum sessions (5) reached" → Run get_session_info() to list active sessions, then end_creative_session({ sessionId: "sess_xxx" }) to free slots.

Wrong output directory → Images default to ~/gemini-creative-images/ (macOS/Linux) or ~/Documents/gemini-creative-images/ (Windows). Use outputDirectory in start_creative_session to redirect to a project folder.

Session expired mid-project → Sessions auto-expire after 30 minutes of inactivity. Start a new session and resume — previous images are still on disk.

Auto-Session Behavior

Calling generate_image, edit_image, or continue_editing without an active session automatically creates a temporary session (isTemporary: true). This session:

Is reused by subsequent standalone tool calls
Is replaced if you manually start a session with start_creative_session
Counts toward the 5-session limit
Shows in get_session_info() with its origin noted