Problem
When the BTP ABAP session expires and cookies are refreshed externally
(e.g. via vsp --browser-auth --cookie-save cookies.txt as a separate
process), the already-running MCP server (vsp --cookie-file cookies.txt --mode focused --keepalive 60s) continues returning HTML IAS redirect
responses for all tool calls — even after cookies.txt is updated on disk.
The MCP server loads cookies once at startup and never reloads from --cookie-file.
Steps to reproduce
- Start vsp as MCP server with --cookie-file
- Wait for BTP session to expire (tools return HTML IAS redirect)
- Refresh:
vsp --url <btp-url> --browser-auth --cookie-save cookies.txt --keepalive 0s
- Browser login completes, cookies.txt updated
- Call any MCP tool → still returns HTML (stale in-memory cookies)
Expected behavior
MCP server detects expired session (ICMENOSESSION / HTML redirect) and
reloads cookies from --cookie-file automatically, without requiring restart.
Workaround
Restart the Claude Code session (restarts MCP server process).
Environment
- BTP ABAP Cloud eu10, IAS SSO
- Windows 11, Claude Code desktop app
Problem
When the BTP ABAP session expires and cookies are refreshed externally
(e.g. via
vsp --browser-auth --cookie-save cookies.txtas a separateprocess), the already-running MCP server (
vsp --cookie-file cookies.txt --mode focused --keepalive 60s) continues returning HTML IAS redirectresponses for all tool calls — even after cookies.txt is updated on disk.
The MCP server loads cookies once at startup and never reloads from --cookie-file.
Steps to reproduce
vsp --url <btp-url> --browser-auth --cookie-save cookies.txt --keepalive 0sExpected behavior
MCP server detects expired session (ICMENOSESSION / HTML redirect) and
reloads cookies from --cookie-file automatically, without requiring restart.
Workaround
Restart the Claude Code session (restarts MCP server process).
Environment