Repository navigation
feat: make the Claude gateway URL configurable - #63
teallarson wants to merge 2 commits into
Conversation
…gateway Both Claude manifests (plugin/ with hooks, clients/claude/ without) now get the gateway_url setting. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit a1adeaa. Configure here.
| }; | ||
| // Claude uses "http" for the "streamable-http" transport in mcp.json. | ||
| const claudeMcpServers = { arcade: { type: "http", url } }; | ||
| const claudeMcpServers = { arcade: { type: "http", url: "${user_config.gateway_url}" } }; |
There was a problem hiding this comment.
Chat ignores configurable gateway URL
High Severity
Both Claude manifests now set mcpServers.arcade.url to ${user_config.gateway_url}. Claude's platform support ignores plugin MCP servers in Chat when the URL contains ${user_config.*}, so Desktop and claude.ai installs lose the Arcade gateway. Only Claude Code prompts for the setting.
Reviewed by Cursor Bugbot for commit a1adeaa. Configure here.
There was a problem hiding this comment.
@cursoragent but Claude lets you configure this in the UI.... The UX is quite odd.
There was a problem hiding this comment.
The Bugbot finding is accurate, and your reply doesn't resolve it. I didn't change anything or reply on the PR.
- Claude's platform table (claude.com/docs/plugins/platform-support) says an MCP server whose URL contains
${user_config.*}is ignored in Chat. In Cowork it's ignored when the referenced option has no default. Claude Code loads it and prompts for the value. This PR gives the option a default, so Cowork should load the default URL. Chat is the problem. - The UI point is partly right. Claude Code's
/configis the UI for this setting, and Chat users can add a custom connector under Settings → Connectors. The "Tools only" section ofdocs/install/claude-desktop.mdalready describes that. But it doesn't cover the plugin's tools in Chat. Those servers are dropped silently, anddocs/install/claude-desktop.mdstill says "Chat gets tools and skills." - Desktop Code has a related issue. Claude's tracker has an open bug ([BUG] Desktop Code: cannot sign in to a plugin MCP server whose URL uses
${user_config.*}anthropics/claude-code#108574) where sign-in fails for plugin MCP servers whose URL uses${user_config.*}.
You need to pick a trade-off, because one plugin manifest can't both substitute the setting in Claude Code and keep a literal URL for Chat:
- Keep the setting and document the gap. Claude Code gets
/config. Chat users add the connector by hand, and the Desktop docs say the plugin's tools aren't available in Chat. - Use a literal default URL in the Claude manifest. Chat, Cowork, and Desktop Code all load the gateway. The
/configsetting goes away, and a custom gateway in Claude Code needs another path.
I'd lean toward option 2 unless custom gateways in Claude Code are a hard requirement. Tell me which you want and I'll make the change, update the docs and tests, and push to this branch.
There was a problem hiding this comment.
Yes but you can set it in the plugin under "Connector" in Claude Desktop.




What/why
Claude Code users can set Arcade gateway URL in
/configto connect the plugin to their own Arcade gateway. Leaving the setting unset useshttps://api.arcade.dev/mcp/arcade. A failed custom connection does not silently switch to the default.Codebase changes
userConfig.gateway_urlsetting with its default fromplugin/mcp.json.Additional notes
Based on #62.
Measured validation:
npm run verify: 217 tests passed, 2 skipped; Claude, Cursor, Codex, and Copilot checks passed.— Strider 🐦⬛, Teal's agent
Note
Medium Risk
Changes how Claude connects to MCP (user-supplied HTTPS endpoints) and tightens manifest/validation around those defaults; other clients and core app code are largely unaffected but misconfiguration could break the gateway connection.
Overview
Claude Code can point the plugin at a custom Arcade MCP gateway via a new
Arcade gateway URLsetting in/config, while the public default stayshttps://api.arcade.dev/mcp/arcade.Manifest generation now adds
userConfig.gateway_url(default taken fromplugin/mcp.json) and wires Claude’smcpServers.arcade.urlto${user_config.gateway_url}; Cursor and the portablemcp.jsonkeep the literal endpoint. Docs and regenerated routing text tell agents to use the configured endpoint when set, and the README notes that a bad custom URL does not fall back to the default.Directory policy, install verification, and tests resolve
${user_config.*}URLs throughdefaultMcpUrland require an HTTPS default for directory submission.Reviewed by Cursor Bugbot for commit a1adeaa. Bugbot is set up for automated code reviews on this repo. Configure here.