Pixel Bridge MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_image | Generate an image via a logged-in web provider (ChatGPT web or Gemini web) and save it locally. Waits inline up to wait_seconds; if generation is still running, returns a job_id to poll with get_generation_status. The MCP does NOT judge quality — after completion, you (the caller) should view the saved file and decide whether to keep it or regenerate with a better prompt. |
| edit_image | Edit an existing local image via a logged-in web provider: uploads the image, sends the edit instructions, and saves the edited result locally. Same job semantics as generate_image. |
| generate_with_both | Generate the same concept with BOTH providers (ChatGPT web + Gemini web) in parallel and save both images locally, so you can visually compare them and pick the winner. Each provider can succeed or fail independently. |
| get_generation_statusA | Check a generation/edit job started by generate_image, edit_image or generate_with_both. Returns status, saved file paths when finished, error details on failure, and recent job logs. |
| download_generated_image | Copy a completed job's image(s) to an additional location. Note: jobs already save their output to the originally requested path automatically — use this only to place an extra copy somewhere else. |
| check_provider_session | Check whether the persistent browser session for a provider is authenticated and usable. Never enters credentials — if not authenticated, it tells you to run provider_login so the user can log in manually. |
| provider_loginA | Open the provider's website in the (headed) persistent browser and WAIT for the user to log in manually — including any CAPTCHA or MFA, which are never automated. Ask the user to complete the login in the opened window; returns once login is detected or the wait times out. Requires the server to run with PIXEL_BRIDGE_HEADLESS unset/false. |
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 2 tools
The two tools have distinct purposes: one for authentication and one for checking job status. No overlap in functionality, making them easily distinguishable.
Tool names follow different patterns: 'get_generation_status' uses verb_noun, while 'provider_login' uses noun_verb. This inconsistency is confusing despite having only two tools.
With only two tools, the server feels under-scoped for image generation. The typical range for a well-scoped server is 3-15 tools, and this falls short.
The server lacks essential tools like generate_image or edit_image, which are critical for its domain. The presence of only login and status checking leaves major gaps.