You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Support per-call server selection for OpenAPI tools
Resolve OpenAPI servers per tool call instead of baking a single base
URL at add time. Operations can declare multiple servers (document,
path, or operation level) and templated URLs with {variables}; each is
now selectable when invoking the tool.
- Each tool exposes an optional `server` input ({ url?, variables? }),
shown only when there is something to choose: `url` becomes an enum
when more than one server applies, and `variables` are drawn from the
applicable servers.
- Host resolution: a connection base URL override wins when set;
otherwise the call's chosen server (server.url or the first
applicable) is resolved with its {variables} (call values, else spec
defaults); otherwise no host is prepended.
- The connection base URL becomes an optional override (off by
default), required only when the spec declares no servers. The form
shows a combobox for multiple top-level servers and a plain input
otherwise, with the first server's resolved URL as the placeholder.
- Drop connection-level serverVariables in favor of per-call variables.
- Bindings persisted before this change keep working: a missing
`servers` field is treated as empty and falls back to the connection
base URL.
0 commit comments