[CHORE]: Python server template — bump mcp to >=2,<3 and align minimum with live servers

Open
#35 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
developer-experience, documentation

Research direction

Start with the Python cookiecutter template's default pyproject.toml and locate the MCP dependency constraint. Review the template README and scaffold generation instructions for SDK v2 API references, including MCPServer and changed imports. Generate a project, verify the v2 patterns and dependency constraint, then run the repository CI checks.

Written by the indexing model from the issue text.

Description

Summary

After the template has been moved to this repository (tracked in #31), update the Python cookiecutter template's default pyproject.toml to target MCP SDK v2 and align its minimum version constraint with the live servers.

Changes required

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

# After
mcp>=2,<3

The current lower bound (1.0.0) is significantly behind what the live servers use (1.28.1). The bump to >=2,<3 brings the template in line with current practice and eliminates the drift.

2. Dev dependency alignment (optional)

Consider aligning the template's dev dependency pins (pytest, ruff, mypy, black) with the versions used in the live servers, so generated projects start from a current baseline.

3. Template documentation

Update the template README and any scaffold generation instructions to reflect the MCP SDK v2 API — particularly the MCPServer class name and any changed import paths.

Acceptance criteria

  • mcp constraint updated to >=2,<3 in template pyproject.toml
  • Generated project uses SDK v2 API patterns
  • Template README reflects v2 usage
  • CI green

References

  • Depends on: #31 (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
4h 29m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

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.