patternfly / patternfly/patternfly-mcp
Review compatibility layer for MCP SDK 2.x
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 11
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 17
Description
As a maintainer I need to review a compatibility layer for the MCP SDK 2.x.
Acceptance criteria
- Review the effort associated with a compatibility layer for interacting with tooling that implements the newer MCP client
Assumptions and questions
-
The MCP SDK release pushed out underneath separate packages like
@modelcontextprotocol/server -
The new setup is supposed be "stateless" meaning on the server-side of things our lift may not be as great as someone implementing an MCP client. Review needing to host both versions of the server 1.x and 2.x if some MCP clients progress and other clients maintain a 1.x setup. There may be a compatibility layer already.
Jira Issue: PF-4526
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 repository's MCP server setup and package dependencies, then compare the current SDK assumptions with the newer MCP SDK 2.x packages. Document whether supporting MCP clients on both server versions requires a compatibility layer and define the effort and scope needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100