[CHORE]: Move url_to_markdown_server to mcp-servers/python/url_to_markdown_server
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 78/100
Research direction
Compare mcp-servers/python/url_to_markdown_server/ in IBM/mcp-context-forge with the target repository layout, then copy the listed files and directories verbatim. Start with its pyproject.toml, README.md, Makefile, and tests/ directory; verify editable installation and run the existing tests. Done means the server is present at the target path, the README reflects its new home, and CI runs its lint and test checks.
Written by the indexing model from the issue text.
Description
Summary
Move the url_to_markdown_server MCP server from the mcp-context-forge monorepo into this repository at mcp-servers/python/url_to_markdown_server/, as part of the MCP server migration tracked in IBM/mcp-context-forge#6228.
What to move
Copy the contents of mcp-servers/python/url_to_markdown_server/ from IBM/mcp-context-forge verbatim:
mcp-servers/python/url_to_markdown_server/
├── .gitignore
├── Containerfile
├── Makefile
├── README.md
├── pyproject.toml
├── src/
│ └── url_to_markdown_server/
│ ├── __init__.py
│ ├── server_fastmcp.py
│ └── ssrf.py
└── tests/
Dependencies (as-is)
From pyproject.toml:
fastmcp>=3.4.4
httpcore>=1.0.5
httpx>=0.28.1
pydantic>=2.13.4
typing-extensions>=4.16.0
The server is moved as-is. Version constraint updates are tracked separately (see sub-issues).
Acceptance criteria
- Server lands at
mcp-servers/python/url_to_markdown_server/in this repository -
pyproject.tomlis present and installable (pip install -e mcp-servers/python/url_to_markdown_server) - Existing tests pass
- CI covers the server (lint + test)
- README updated to reflect new home
References
- Parent issue: IBM/mcp-context-forge#6228
- Source: https://github.com/IBM/mcp-context-forge/tree/main/mcp-servers/python/url_to_markdown_server
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- Avg merge
- 51m
- Merged PRs (30d)
- 7
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from IBM/contextforge-examples
-
Difficulty 2/5 Half a day Newbie friendliness 78/100
IBM/contextforge-examples#29 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
IBM/contextforge-examples#37 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
IBM/contextforge-examples#38 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
IBM/contextforge-examples#32 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
IBM/contextforge-examples#33 ·
All issues in IBM/contextforge-examples
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 91/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
-
enhancement P2
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Toloka/tolokaforge#1776 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
TencentCloud/Octop#1622 ·
Maintainers usually reply within 1 day
-
[arch] gate_sync.sh: stale remote tmp files on install failure; overlapping cron runs unguardedOpenarch area:fleet priority:p3 severity:low track:hosted-product
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day