Ecosyste.ms: Timeline
Browse the timeline of events for every public repo on GitHub. Data updated hourly from GH Archive.
jspahrsummers closed a pull request on modelcontextprotocol/specification
docs: update README links
<!-- Provide a brief summary of your changes --> ## Motivation and Context I noticed the links to `schema.ts` and `schema.json` were pointing to out-of-date locations in the repo. I pointed t...
jspahrsummers created a review on a pull request on modelcontextprotocol/specification
Thanks! I think this is good for now, as long as we remember to update it with protocol revs.
jspahrsummers pushed 4 commits to main modelcontextprotocol/specification
- fix: incorrect link for "Specification (Draft)" on nav bar 4ba0da6
- fix: update draft page reference and add alias for better navigation 8e98e65
- Merge branch 'main' into fix-nav-link c34e867
- Merge pull request #137 from imfing/fix-nav-link fix: incorrect link for "Specification (Draft)" on nav bar c4001aa
jspahrsummers closed a pull request on modelcontextprotocol/specification
fix: incorrect link for "Specification (Draft)" on nav bar
<!-- Provide a brief summary of your changes --> Fix a link that redirects to 404 ## Motivation and Context <!-- Why is this change needed? What problem does it solve? --> After clicking ...
jspahrsummers pushed 1 commit to justin/fix-multiple-registrations modelcontextprotocol/typescript-sdk
- Preemptively bump package version 38c361a
jspahrsummers opened a draft pull request on modelcontextprotocol/typescript-sdk
Fix registering multiple tools/resources/prompts
Request handlers were being re-registered every time a new tool/resource/prompt was added, which would fail since the handlers were already registered. Now we track whether handlers have been initi...
jspahrsummers created a comment on an issue on modelcontextprotocol/typescript-sdk
Thanks, absolutely right. I mistakenly didn't update the README examples after the API changed. 😥
jspahrsummers opened a pull request on modelcontextprotocol/typescript-sdk
Fix README examples not using `ResourceTemplate` class
Resolves #123.
jspahrsummers created a branch on modelcontextprotocol/typescript-sdk
justin/fix-quickstart - The official Typescript SDK for Model Context Protocol servers and clients
jspahrsummers published a release on modelcontextprotocol/typescript-sdk
1.3.0
## What's Changed This release introduces a [simplified, Express-like API](https://github.com/modelcontextprotocol/typescript-sdk/pull/117), somewhat similar to the FastMCP API of the [Python SD...
jspahrsummers created a tag on modelcontextprotocol/typescript-sdk
1.3.0 - The official Typescript SDK for Model Context Protocol servers and clients
jspahrsummers pushed 34 commits to main modelcontextprotocol/typescript-sdk
- Server.tool() convenience API f8f5686
- Assert tool request handlers do not already exist 4bf5c53
- Allow capabilities to be dynamically registered after initialization 1506bd1
- Automatically register `tools` capability 7ac5a5f
- Tests for `mergeCapabilities` c14a5d4
- Fix string type check b538731
- Tests for Server.tool ff22f25
- Errors invoking tools should be erroneous tool results, not McpErrors aac1959
- Minor tweak to make test code more idiomatic bb28c9b
- URI Template parser and matcher 7f0cf73
- More thorough handling of edge cases/pathologies dc77d9c
- Add method to determine if a URI is a template or not 1e040e9
- Add UriTemplate.toString e4b3820
- Add simplified API for registering resources and resource templates 098266a
- Method documentation 1970509
- Add a test for listCallback 3f9acec
- Make `Variables` non-optional with resource template URIs 45f99e6
- Create `ResourceTemplate` class and move `listCallback` into it 8356cb9
- Move `Server` helper definitions to bottom of file f090c93
- Add `extra` to resource request handlers 5ddfa0a
- and 14 more ...
jspahrsummers closed a pull request on modelcontextprotocol/typescript-sdk
Simplified, Express-like API
Inspired by https://github.com/modelcontextprotocol/typescript-sdk/issues/116 and some of the MCP SDK wrappers that have popped up in the ecosystem, this is an attempt to bring a more [Express](htt...
jspahrsummers pushed 4 commits to justin/simplified-api modelcontextprotocol/typescript-sdk
jspahrsummers created a comment on an issue on modelcontextprotocol/typescript-sdk
Done! Released as [1.2.0](https://github.com/modelcontextprotocol/typescript-sdk/releases/tag/1.2.0).
jspahrsummers published a release on modelcontextprotocol/typescript-sdk
1.2.0
## What's Changed * fix: add cjs format support by @ycjcl868 in https://github.com/modelcontextprotocol/typescript-sdk/pull/110 * feat: add optional instructions field to server _oninitialize by ...
jspahrsummers created a tag on modelcontextprotocol/typescript-sdk
1.2.0 - The official Typescript SDK for Model Context Protocol servers and clients
jspahrsummers created a comment on a pull request on modelcontextprotocol/typescript-sdk
> how do progress notifications / resource update notifications fit into this nicely? perhaps this could be added to `RequestHandlerExtra` in the future? From what I see we can add that after this ...
jspahrsummers created a review comment on a pull request on modelcontextprotocol/specification
As above, should we defer this to a separate proposal?
jspahrsummers created a review comment on a pull request on modelcontextprotocol/specification
What happened to the existing "transports" page? Is it still there?
jspahrsummers created a review comment on a pull request on modelcontextprotocol/specification
Should we follow up with this separately? We can just focus auth on HTTP for now, and get into the weeds of stdio -> HTTP upgrade later.
jspahrsummers created a review comment on a pull request on modelcontextprotocol/specification
Is there any reason to not just require the `Authorization` header? I don't think we have a reason to support the form-encoded content variant.
jspahrsummers created a review on a pull request on modelcontextprotocol/specification
Mostly requesting discussion on the specifics around what we want to _require_ versus _recommend_, but I think all the substantive stuff about how the auth flow actually works LGTM!
jspahrsummers created a review on a pull request on modelcontextprotocol/specification
Mostly requesting discussion on the specifics around what we want to _require_ versus _recommend_, but I think all the substantive stuff about how the auth flow actually works LGTM!
jspahrsummers created a review comment on a pull request on modelcontextprotocol/specification
I thought we were only going to _recommend_ this. Why is it required here?
jspahrsummers created a review comment on a pull request on modelcontextprotocol/specification
Refer to OAuth 2.1 here? (Notably it doesn't call it "PKCE" anymore, just incorporates it directly.)
jspahrsummers created a review comment on a pull request on modelcontextprotocol/specification
This doesn't make sense to me. A backend API could be an MCP client.