Gimp Mcp Server

Created By
Maora year ago
This project enables non-technical users to edit images with GIMP through simple conversational commands, bridging the gap between GIMP's powerful capabilities and natural language interaction. It also allows professionals to execute complex multi-step workflows faster than traditional point-and-click methods. Users can describe what they want to achieve - from basic photo adjustments to sophisticated artistic modifications. For example, "brighten the background and add a vintage filter" or "remove the red-eye and sharpen the subject" - and the system translates these requests into precise GIMP operations. The project is functional and exposes all GIMP features via MCP. The main development focus is creating comprehensive AI-readable documentation to help AI agents use GIMP efficiently.
Overview

What is Gimp Mcp Server?

Gimp Mcp Server is a project that allows non-technical users to edit images using GIMP through simple conversational commands, making GIMP's powerful features accessible via natural language. It also enables professionals to perform complex workflows more efficiently than traditional methods.

How to use Gimp Mcp Server?

To use Gimp Mcp Server, install the GIMP plugin, configure your MCP client (like Claude Desktop or Gemini CLI), and start the MCP server from the GIMP interface. You can then issue commands to edit images, such as 'brighten the background' or 'remove red-eye'.

Key features of Gimp Mcp Server?

  • Conversational command interface for image editing
  • Access to all GIMP features via MCP
  • Support for complex multi-step workflows
  • AI-readable documentation for efficient use

Use cases of Gimp Mcp Server?

  1. Non-technical users can perform basic photo edits without learning GIMP.
  2. Professionals can execute intricate editing tasks quickly.
  3. AI agents can automate image editing processes using natural language commands.

FAQ from Gimp Mcp Server?

  • What versions of GIMP are supported?

Gimp Mcp Server is developed for GIMP 3.0 and above.

  • Is there a specific AI client required?

Yes, it works with MCP-compatible clients like Claude Desktop and Gemini CLI.

  • Can I contribute to the project?

Yes! Contributions are welcome, including bug fixes and new features.

Server Config

{
  "mcpServers": {
    "gimp": {
      "command": "uv",
      "args": [
        "run",
        "--directory",
        "your/path/to/gimp-mcp-server",
        "server.py"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Maor
Star
-
Language
-
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago