Breaking change: API key in URL no longer works after PR #7

[niravpatel27]

Description
After PR #7 was merged on Jan 14, 2026, direct connections to https://websetsmcp.exa.ai/mcp?exaApiKey=API_KEY no longer work.
Error
json{"error":"invalid_token","error_description":"Configuration required"}
What Was Working (Before Jan 14)
yaml# LibreChat librechat.yaml
mcpServers:
websets:
type: streamable-http
url: "https://websetsmcp.exa.ai/mcp?exaApiKey=MY_API_KEY"
Connection was established successfully and all tools worked.
What Broke
The same configuration now fails with invalid_token error. The API key is valid — it works in Claude Code with type: http.
Root Cause
PR #7 migrated to Smithery's Cloudflare Workers runtime and updated @smithery/cli from ^1.4.4 to ^3.1.6. This appears to have changed the authentication flow to require Smithery's infrastructure rather than accepting direct API key authentication.
Impact

LibreChat users cannot use Websets MCP via direct URL
Any MCP client using streamable-http or sse transport is affected
Only Claude Code with type: http seems to work

Request
Please restore backward compatibility for direct HTTP connections with API key in URL, or document the new required authentication method for non-Smithery clients.
Environment

LibreChat v0.8.2-rc2
Transport: streamable-http
Endpoint: https://websetsmcp.exa.ai/mcp