modelcontextprotocol / modelcontextprotocol/go-sdk
Proposal: add ErrorHandler to ServerOptions
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.1k
- Forks
- 543
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 37
Description
At various points in the serving infrastructure, an error is produced out-of-band of any particular client RPC or API call. We should add an ErrorHandler to allow users of the SDK to receive these errors.
Open question: should this be scoped to the Server, or to the Session? Probably it should be scoped to the session, in which case this belongs on something like the SessionOptions being discussed in #148.
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 reviewing the serving infrastructure and the ServerOptions API described in the issue. Compare the proposed server scope with the SessionOptions discussion in #148 before deciding where the handler belongs. Done means the scope and public API are agreed and users can receive out-of-band serving errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100