Ecosyste.ms: Timeline
Browse the timeline of events for every public repo on GitHub. Data updated hourly from GH Archive.
jspahrsummers created a review on a pull request on modelcontextprotocol/python-sdk
Broadly looks good. Do we need to update everything to _require_ using `RequestResponder` as a context manager? e.g., MCP client code, docs, …? And should it be an error to use `RequestResponder...
jspahrsummers created a comment on an issue on modelcontextprotocol/typescript-sdk
I'm afraid I'm not very familiar with bun. Do you have a reproducible example project?
jspahrsummers created a comment on an issue on modelcontextprotocol/typescript-sdk
This could always be rolled by hand too. Nothing in the SSE transport implementation from the SDK is special in any way, and could easily be replicated in a custom class.
jspahrsummers created a comment on an issue on modelcontextprotocol/typescript-sdk
tbh we should probably remove the WS transport that's there. It's useful to demonstrate that others are _possible_ (e.g., in isolated use cases), but we don't want a proliferation of transports, be...
jspahrsummers created a review comment on a pull request on modelcontextprotocol/python-sdk
I'm quite allergic to actually sleeping in tests, due to the flakiness and slowness. Is there any other way we can exercise these? Would a timeout of 0 work? Or a timeout in the past vs. a timeout ...
jspahrsummers created a review on a pull request on modelcontextprotocol/python-sdk
Broadly looks good. Do we need to update everything to _require_ using `RequestResponder` as a context manager? e.g., MCP client code, docs, …? And should it be an error to use `RequestResponder...
jspahrsummers created a review on a pull request on modelcontextprotocol/python-sdk
Broadly looks good. Do we need to update everything to _require_ using `RequestResponder` as a context manager? e.g., MCP client code, docs, …? And should it be an error to use `RequestResponder...
jspahrsummers opened an issue on modelcontextprotocol/python-sdk
Better CORS defaults for SSE transport
It's likely that _most_ MCP servers accessible over SSE should be contactable by frontend web applications, which means the right CORS headers need to be set. The SDK should likely opt-in to this b...
jspahrsummers opened an issue on modelcontextprotocol/typescript-sdk
Better CORS defaults for SSE transport
It's likely that _most_ MCP servers accessible over SSE should be contactable by frontend web applications, which means the right CORS headers need to be set. The SDK should likely opt-in to this b...
jspahrsummers created a review on a pull request on modelcontextprotocol/specification
Please remove the transport upgrade spec (to be discussed separately), and then I think this is ready to go. 🙏 Thanks for all the hard work putting this together!
jspahrsummers created a review on a pull request on modelcontextprotocol/specification
Please remove the transport upgrade spec (to be discussed separately), and then I think this is ready to go. 🙏 Thanks for all the hard work putting this together!
jspahrsummers pushed 24 commits to main modelcontextprotocol/inspector
- Bump SDK 2b53a83
- Pre-emptively bump npm package versions Before I forget! 60b8892
- Server doesn't need to inject `eventsource` anymore c1e06c4
- Pass through `Authorization` headers sent to inspector server e7697eb
- Clarify inspector-server error logging 14db05c
- Report SSE 401 errors to the client 8bb5308
- Use new `SseError` class from SDK 8a20f77
- Redirect into OAuth flow upon receiving 401 1c4ad60
- OAuth callback handler (not yet attached) 16cb596
- Implement OAuth callback 23f89e4
- Extract session storage keys into constants 02cfb47
- Fix React import e470eb5
- Token exchange body needs to be JSON 874320e
- Set Authorization header from client af88770
- Fix Authorization header passthrough Node.js headers are lowercase 731ee58
- Bump SDK version a6d22cf
- Fix Vite config 3bc776f
- Fix error state being briefly shown before OAuth 99d7592
- Remember last selected transport and SSE URL c22f918
- Auto-reconnect after OAuth 0648ba4
- and 4 more ...
jspahrsummers closed a pull request on modelcontextprotocol/inspector
OAuth support for SSE
Implemented according to https://github.com/modelcontextprotocol/specification/pull/133.
jspahrsummers created a review comment on a pull request on modelcontextprotocol/specification
```suggestion need for users to provide endpoints manually or for fallback to the defined defaults. ```
jspahrsummers created a review comment on a pull request on modelcontextprotocol/specification
```suggestion We strongly recommend that all clients implement metadata discovery. This reduces the ```
jspahrsummers created a review comment on a pull request on modelcontextprotocol/specification
```suggestion We strongly recommend that local clients implement OAuth 2.1 as a public client: ```
jspahrsummers created a review comment on a pull request on modelcontextprotocol/specification
```suggestion M->>C: Access Token (+ Refresh Token) ```
jspahrsummers created a review comment on a pull request on modelcontextprotocol/specification
I'm still confused by this bullet. What does it mean that "clients must not require client secrets?"
jspahrsummers created a review comment on a pull request on modelcontextprotocol/specification
```suggestion Note that it is not required to support Dynamic Client Registration. MCP clients that do ```
jspahrsummers created a review comment on a pull request on modelcontextprotocol/specification
```suggestion - MCP servers with localhost redirect URIs **MAY** support Dynamic Client ``` (nit for grammar—alternatively, "may optionally")
jspahrsummers created a review comment on a pull request on modelcontextprotocol/specification
```suggestion Server Metadata Discovery to allow the MCP server to respond based on the MCP protocol version. ```
jspahrsummers created a review comment on a pull request on modelcontextprotocol/specification
```suggestion _MUST_ support fallback URLs. ```
jspahrsummers created a review comment on a pull request on modelcontextprotocol/specification
```suggestion - MCP server _SHOULD_ follow the OAuth 2.0 Authorization Server Metadata ```
jspahrsummers created a review comment on a pull request on modelcontextprotocol/specification
```suggestion When authorization is required and not yet proven by the client, servers **MUST** ```
jspahrsummers created a review on a pull request on modelcontextprotocol/specification
Please remove the transport upgrade spec (to be discussed separately), and then I think this is ready to go. 🙏 Thanks for all the hard work putting this together!
jspahrsummers created a review on a pull request on modelcontextprotocol/specification
Please remove the transport upgrade spec (to be discussed separately), and then I think this is ready to go. 🙏 Thanks for all the hard work putting this together!