fix: add ping keepalive configuration for HTTP stream transport to prevent SSE timeouts#94
fix: add ping keepalive configuration for HTTP stream transport to prevent SSE timeouts#94
Conversation
…event SSE timeouts
…m transport to prevent SSE timeouts
🦋 Changeset detectedLatest commit: e950f3c The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Thanks! I´m seeing the following messages: the ping failed messages appear randomly, sometimes after 1 second. I´m using the defaults (no configuration). In LibreChat I see the following Please note, in both the discogs mcp server and the amadeus mcp server I always see an initial I find that discogs logs should have timestamps, otherwise it´s hard/a guess to match the logs and the events or packet traces. I´m attaching a PCAP file next |
|
btw, is there a way to increase verbosity of logs besides PING? |
The ping failures look like a Our logs already have timestamps, but FastMCP’s don’t, which makes correlation harder. Can you try disabling ping and share the results? |
Description
When running the server in Docker with HTTP stream transport (used by LibreChat and similar clients), SSE connections time out after ~60 seconds of inactivity, causing:
Configure FastMCP's built-in ping/keepalive for HTTP stream transport. The server sends periodic keepalive messages every 30 seconds (configurable) to prevent timeouts.
Checklist
feat:,fix:,chore:,docs:, etc.pnpm changeset) if necessaryTests and linting
pnpm test.pnpm lint.pnpm format.Related Issues
Closes #93