posit-dev / posit-dev/mcptools
investigate potential breakages with MCP 2.0
Open
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 196
- Forks
- 21
- Avg merge
- 1h 14m
- Merged PRs (30d)
- 1
Description
A major release of the protocol just went out.
With the version negotiation, we can likely get away with not implementing for a while, but worth investigating sooner than later.
Contributor guide
No contributing guide indexed for this repository
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 repository's current MCP protocol handling and the MCP 2.0 release changes, focusing on version negotiation. Identify any compatibility breakages and record the affected behavior and required follow-up; completion means the investigation has a clear result rather than an untested concern.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100