modelcontextprotocol / modelcontextprotocol/servers

Issues with streamable http everying example:

Open
#4,087 0 comments 0 reactions 0 assignees View on GitHub

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

  1. The documentation for EventStore["replayEventsAfter"] implies that we should be returning the streamId associated with the eventId but the code calls that lastId and then assigns it initially to eventId.
  2. The InMemoryEventStore erroneously will replay all events, even those for different streams
  3. Unlike the python API, the tying of EventStore["replayEventsAfter"] does not allow for returning undefined (as opposed to Python's None) when the eventId is unknown.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.