MCP docs Launch Installer Button not working with env variables

[protoss70]

Describe the bug

Note: Please check the common issues on https://block.github.io/goose/docs/troubleshooting before filing a report

I am having a hard time Launch Installer button work. I am integrating Apify MCP into Goose MCP registry. For Apify MCP the user needs to provide an env variable APIFY_TOKEN. But the Launch Installer button doesn't seem to work with env variables.

To Reproduce

1. Go to /goose/docs/mcp/asana-mcp
2. Click on the Launch Installer button
3. See that it doesn't install the mcp correctly
4. Go to /goose/docs/mcp/netlify-mcp
5. Press the Launch Installer button again
6. It works, the only difference is that asana MCP has env variable in its launch installer link while netlify doesn't have it

Expected behavior
I expect the Launch Installer button to handle the env variables correctly and prompt the user to retrieve their token

Please provide following information:

• I am using the latest version as of writing this, Goose v1.9.1

Additional context
We are trying to integrate Apify MCP into Goose MCP docs. I am unable to make the Launch Installer button work.

[DOsinga]

/cc @amed-xyz do we expect this to work now or is the config on our site wrong?

[alexhancock]

I see a similar experience once goose opens for these two extensions with goose 1.12.0. Both bring up the form to fill in the API keys needed by each extension.

Feel free to re-open if not addressed for you somehow.