Wherever your agent lives, the image tools can get there.
The server is a standard Model Context Protocol endpoint. Every guide below is the same three facts — the endpoint, your key as a header, and where that client keeps its config — written out for the client you actually use.
Claude Desktop
The chat app. Paste one JSON block, quit and reopen, and Claude can make images mid-conversation.
config claude_desktop_config.json
transport npx bridge
Claude Code
One command. The coding agent then generates assets and writes them into the repo in the same run.
config claude mcp add
transport HTTP or skill/CLI
Cursor
User scope or project scope. Composer fills the placeholder rectangles as it writes the components.
config ~/.cursor/mcp.json
transport HTTP or npx bridge
Windsurf
Cascade picks up all eleven tools with their schemas after a panel refresh.
config ~/.codeium/windsurf/mcp_config.json
transport HTTP or npx bridge
GitHub Copilot
Agent mode, with the key prompted for rather than committed — and a tools picker you can narrow.
config .vscode/mcp.json
transport HTTP
Cline
Autonomous plans, with an auto-approve policy drawn along the line between fixed and model-priced calls.
config MCP Servers panel
transport HTTP or stdio
ChatGPT & OpenAI
The endpoint and auth for connectors, the Agents SDK and the Responses API — with the honest caveats.
config Custom connector / Agents SDK
transport HTTP
Any other MCP client
Point it at the endpoint and send your key as a header. If it can only spawn processes, use the npx bridge; if it can only take a URL, append the key as a query parameter.
https://mcp.imagemcpserver.com/mcpGeneric setup docs →Every guide is the same three facts
If your client is not listed, you still have everything you need. MCP clients differ in where they keep configuration, not in what a server needs from them.
The endpoint
https://mcp.imagemcpserver.com/mcpStreamable HTTP. There is also a stdio process for clients that prefer to spawn one locally.
The credential
x-api-key: sk-img-gen-…Authorization: Bearer works too, and ?apikey= for clients that cannot send headers.
The config location
client-specificA JSON file, a CLI command or a settings panel. That is the only part that varies.
What shows up after you connect
Eleven tools, each with a full JSON schema. The agent learns the parameters, the enums and the required fields from the protocol — you never have to explain the API in a prompt.
generate_imagegenerate_transparent_imageedit_imageremove_backgroundupscale_imagetext_to_svgcompress_imageconvert_formatmulticallget_user_infolist_modelsFirst thing to ask, in any client
“How many image credits do I have left?”
It forces a real tool call, the call is free, and a real number back means the whole chain — config, transport, key, account — is working. If it answers vaguely, the server is not loaded.
You need a key before any of this works
Free account, 30 credits a month, no card. The key is issued instantly and works in every client on this page.