GPT Image Playground MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_BRIDGE_PORT | No | 本机 Bridge 端口；扩展地址需要与它一致。 | 8787 |
| MCP_BRIDGE_TOKEN | No | 高级部署可指定固定本机连接值；普通安装无需设置。默认自动生成。 | |
| MCP_ACTIVE_STALE_MS | No | 可选的任务心跳失联处理；不会自动重复生成。 | 0 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_imageA | 通过已打开的 GPT Image Playground 页面生成图片，可先注入本地参考图。请求会被浏览器桥接扩展串行处理，直到页面报告完成或失败；没有 20 秒固定上限。 |
| get_task_statusB | 查询 Playground 页面中某个生成任务的状态。 |
| download_imageB | 把已完成任务中的图片从 Playground 页面保存到 MCP 主机的本地绝对路径。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool handles a distinct phase of the image generation workflow: generating, checking status, and downloading. There is no overlap in their purposes, making it clear which tool to use at each step.
All three tool names follow a consistent verb_noun pattern (generate_image, get_task_status, download_image), using snake_case and clear action-first naming. The pattern is uniform across the set.
With only 3 tools, the server is tightly scoped to a single workflow (generate, track, download). This is appropriate for a focused purpose and each tool is necessary for the complete flow.
The workflow covers the essential lifecycle: generation initiation, status polling, and downloading results. A minor gap is the lack of a cancellation or listing tool, but agents can work around this by waiting or using status checks.