Add an agent-facing update tool for MCP servers

[RhysSullivan]

mcp.addServer has an agent-facing counterpart for remove (integrations.remove, #1600), but updates still require the HTTP API or UI (POST /mcp/servers/:slug/config and /auth, plus the edit flows from #1775/#1821). There is no agent-facing mcp.updateServer / configureAuth tool, and a remote addServer without authenticationTemplate still defaults to auth none.

Split from #1330 (part 2 residual). This is an API-surface decision, not a bug — the remove+re-add path works today.

[Adityakk9031]

Looking into this! Tracing the MCP server configuration and auth endpoints to add an agent-facing update tool (e.g. \mcp.updateServer\ / \configureAuth) that complements \mcp.addServer\ and \integrations.remove.

[Adityakk9031]

Opened PR with the implementation: #1856

[The-AarushiSingh]

@RhysSullivan , Looks like #1856 added a new updateServer that merges config via integrations.update, plus configureAuth. configureServer / configureAuth already exist on the SDK/HTTP side.
Before another PR: do you want thin tool() wrappers around those two functions (same as #1600), or is the new merge-in-plugin.ts the intended design?