fix: point gateway-setup deep link at /mcp-gateways/new#40
Merged
Conversation
The dashboard moved gateway creation to a dedicated /mcp-gateways/new page and dropped the list route's ?create / ?tools params (ArcadeAI/monorepo#1904). Update the post-scaffold 'create your MCP gateway' link to /mcp-gateways/new?tools=…; the JSON-encoded tools param is unchanged and parses on the new route.
teallarson
approved these changes
Jul 7, 2026
teallarson
left a comment
teallarson
left a comment
Collaborator
There was a problem hiding this comment.
can you bump the version, too?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
The post-scaffold "Click here to create your MCP gateway" link builds:
The dashboard moved gateway creation to a dedicated
/mcp-gateways/newpage and removed the list route's legacy?create/?toolsparams (ArcadeAI/monorepo#1904). With that shipped, the old link lands on the gateways list with no prefill and no create flow — everynpx @arcadeai/create-agentrun that shows the gateway setup step is affected.This updates the link to:
Why it's safe / keeps working
encodeURIComponent(JSON.stringify([...])). The new route validatestoolswith the exact samez.array(z.string())schema the list route used, so the JSON-array param parses and pre-fills the picker identically (it's literally what the old list→/newredirect forwarded).app.arcade.dev/mcp-gatewayslinks (list page) are untouched and still valid.tsc --noEmit,eslint,prettier --check, andtscbuild all pass.Ordering
Should merge with or shortly after ArcadeAI/monorepo#1904 reaches production (the
/mcp-gateways/newroute must exist). Until then the current?create=truelink still resolves via the compatibility redirect on the old build.