Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[CHORE]: mcp_eval_server — bump mcp to >=2,<3

Open
  • Is something wrong?
#37 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
api, backend

Research direction

Start with mcp-servers/python/mcp_eval_server/pyproject.toml and the MCP SDK v2 migration guide. Review the server's transport call sites, protocol type aliases, and sync handlers for the listed compatibility changes, then run the existing tests and CI. Done means the dependency targets >=2,<3, all tests pass against SDK v2, and CI is green.

Written by the indexing model from the issue text.

Description

Summary

After the server has been moved to this repository (tracked in #26), update mcp-servers/python/mcp_eval_server/pyproject.toml to target MCP SDK v2.

Changes required

1. MCP SDK version bump
# Before
mcp>=1.28.1,<2

# After
mcp>=2,<3
2. API changes required by MCP SDK v2

Per the MCP SDK v2 migration guide:

  • Protocol type aliases using camelCase have been removed; use snake_case equivalents.
  • Review any transport constructor parameters — these may need to move to run()/app call sites.
  • Validate that sync handler functions do not call asyncio.get_running_loop().

Acceptance criteria

  • mcp constraint updated to >=2,<3 in pyproject.toml
  • All tests pass against MCP SDK v2
  • CI green

References

  • Depends on: #26 (move issue)
  • MCP SDK v2 migration epic: IBM/mcp-context-forge#6218
  • Step 10 (mcp-servers update): IBM/mcp-context-forge#6228
Dominant language
Python
Stars
1
Forks
1
Avg merge
51m
Merged PRs (30d)
7

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from IBM/contextforge-examples

All issues in IBM/contextforge-examples

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.