modelcontextprotocol / modelcontextprotocol/servers
Issues with streamable http everying example:
Open
Nobody has claimed this yet.
bug
- Dominant language
- TypeScript
- Stars
- 90.5k
- Forks
- 11.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 5
Description
The following issues with https://github.com/modelcontextprotocol/servers/blob/main/src/everything/transports/streamableHttp.ts
- The documentation for
EventStore["replayEventsAfter"]implies that we should be returning thestreamIdassociated with theeventIdbut the code calls thatlastIdand then assigns it initially toeventId. - The
InMemoryEventStoreerroneously will replay all events, even those for different streams - Unlike the python API, the tying of
EventStore["replayEventsAfter"]does not allow for returningundefined(as opposed to Python'sNone) when theeventIdis unknown.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading src/everything/transports/streamableHttp.ts, focusing on EventStore["replayEventsAfter"] and InMemoryEventStore. Check the TypeScript behavior against the documented contract and the Python API mentioned in the issue. Done means the stream identifier, stream filtering, and unknown-event return behavior all match the stated expectations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 76/100