[CHORE]: url_to_markdown_server — migrate from standalone fastmcp to mcp>=2,<3 MCPServer

Open
#34 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
backend-api-design, devtools

Research direction

Start in mcp-servers/python/url_to_markdown_server/ and inspect server_fastmcp.py plus pyproject.toml, including the project scripts entry point. Check the existing tests and run the full test suite after migrating the dependency and imports; done means no remaining fastmcp imports, all tests pass against MCP 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 #30), update mcp-servers/python/url_to_markdown_server/ to migrate from the standalone fastmcp package to the MCP SDK v2 MCPServer.

Changes required

1. Dependency swap
# Before
fastmcp>=3.4.4

# After
mcp>=2,<3
2. FastMCP → MCPServer rename
# Before (standalone fastmcp package)
from fastmcp import FastMCP
app = FastMCP('url-to-markdown-server')

# After (MCP SDK v2)
from mcp.server import MCPServer
app = MCPServer('url-to-markdown-server')

Note: If the server uses standalone fastmcp-specific APIs with no equivalent in mcp.server.MCPServer, document the gap and decide whether to keep fastmcp as an explicit dependency instead.

3. Rename entry-point module (optional)

Consider renaming server_fastmcp.py → server.py and updating pyproject.toml [project.scripts] accordingly.

Acceptance criteria

  • fastmcp dependency replaced with mcp>=2,<3
  • No remaining fastmcp imports
  • All tests pass against MCP SDK v2
  • CI green

References

  • Depends on: #30 (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.