Skip to main content
Hugo Torres
Participant
August 10, 2026
Question

Adobe Connector for Chat GPT can't generate images

  • August 10, 2026
  • 8 replies
  • 214 views

The Adobe Firefly connector in Codex is repeatedly failing with:

HTTP 403 Forbidden — “MCP streamable transport probe failed”

Endpoint: https://photoshop-mcp-service.adobe.io/v3-creativity-b8f2a/mcp

The connector worked briefly and successfully generated images, but then began returning this error again. It occurs before Firefly receives the prompt, even when generating one image at a time. Disconnecting, reconnecting and restarting the app have not resolved it. Please investigate the connector’s authentication/transport authorization.

    8 replies

    Melodic_discoverer24d3
    Participant
    August 25, 2026

    Hello ​@Sameer K , hope you are doing well. Could you please share whether there has been any progress or an updated ETA for a fix?

    I have been experiencing this exact HTTP 403 / “MCP streamable transport probe failed” issue intermittently for roughly a month—not only since this thread was opened. It has occurred many times across repeated attempts. Disconnecting/reconnecting the Adobe connector, restarting ChatGPT/Codex Desktop, reinstalling the connector, and signing in again have not provided a stable fix. Sometimes it works briefly, then the same 403 returns.

    The same Adobe account and images work in Photoshop on the web, while the official Adobe connector fails before image processing begins. This is blocking an ongoing batch image-editing workflow.

    Is this still an active known incident? Has the expected resolution window changed, and is there a ticket or status page we can follow? Thank you.

      c.pfaffenbichler
      Community Expert
      c.pfaffenbichlerCommunity Expert
      Community Expert
      August 15, 2026

      Though I have to admit that 

      Endpoint: https://photoshop-mcp-service.adobe.io/v3-creativity-b8f2a/mcp

      makes it seem likely that Photoshop is involved.

      I just don’t think that most of the Photoshop users who are active on this Forum would be able to help with this issue because they are (largely) working with Photoshop itself.

       

      ​@Sameer K , please forgive the importunity but do you have insights into this issue? 

       

      Sameer K
      Community Manager
      Sameer KCommunity Manager
      Community Manager
      August 17, 2026

      ​

      ​@c.pfaffenbichler - No worries, thanks for the tag.


      ​Hey, ​@Hugo Torres - Welcome to the Photoshop Community. 

      While I am not the correct contact for this issue, I have conducted some research and discovered that this is a known temporary problem, with a potential resolution expected in the coming week(s). I've added the ticket details to the thread for moderators.

       

      Currently, this is not considered a bug but a main thread where we will consolidate any other reports indicating the same failure.


      Thanks!
      Sameer K
      (Type '@' and type my name to mention me when you reply)

        c.pfaffenbichler
        Community Expert
        c.pfaffenbichlerCommunity Expert
        Community Expert
        August 17, 2026

        Thank you for looking into this issue, ​@Sameer K !

        c.pfaffenbichler
        Community Expert
        c.pfaffenbichlerCommunity Expert
        Community Expert
        August 15, 2026

        Is this problem connected to Photoshop in any way? 

        Hugo TorresAuthor
        Participant
        August 15, 2026

        That’s the Adobe Connector for GPT. I raised the question using Firefly link to the community. 

        c.pfaffenbichler
        Community Expert
        c.pfaffenbichlerCommunity Expert
        Community Expert
        August 15, 2026

        This is the Photoshop Forum, if the task does not involve Photoshop itself maybe you should post on the Firefly Forum. 

        https://community.adobe.com/adobe-firefly-396

          Hugo TorresAuthor
          Participant
          August 10, 2026

          Adobe Firefly connector in Codex Desktop intermittently fails with HTTP 403

          I have reproduced an intermittent failure when attempting to generate an image through the Adobe Firefly connector in Codex Desktop.

          Test request:

          • One image

          • Simple prompt: “A red ceramic mug on a plain white background”

          • 1MP

          • PNG output

          Timestamp:
          10 August 2026, approximately 16:01:38 BST (UTC+01:00, Europe/London)

          Complete error:

          McpServerError: MCP streamable transport probe failed with HTTP 403 from adobe.io

          Structured error details:

          Environment:

          • Codex Desktop 26.803.41515, build 6321

          • macOS 26.5.2

          • Apple Silicon / arm64

          • Adobe plugin package 7.0.0

          The failure occurs during the MCP transport probe, before Firefly receives or processes the image prompt. The connector has worked successfully on previous attempts, so the issue appears intermittent.

          Disconnecting and reconnecting the Adobe connector and restarting Codex have not consistently resolved it.

          A screenshot of the reproduced error is attached. No Adobe-issued request ID or trace ID was exposed in the response or visible application diagnostics

           

          Terms & ConditionsAccessibility statement
          Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices