[CHORE]: Move mcp-rss-search to mcp-servers/python/mcp-rss-search

Open
#30 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
74/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Active
Tech stack
python
Domain
api, backend, ci-cd, testing

Research direction

Start by comparing the source directory mcp-servers/python/mcp-rss-search in IBM/mcp-context-forge#6228 with the destination path in this repository. Check pyproject.toml installation, run the existing tests and test_live.sh as appropriate, and inspect repository CI conventions. Done means the files and README are present at the new path, installation works, tests pass, and CI covers lint and test.

Written by the indexing model from the issue text.

Description

Summary

Move the mcp-rss-search MCP server from the mcp-context-forge monorepo into this repository at mcp-servers/python/mcp-rss-search/, as part of the MCP server migration tracked in IBM/mcp-context-forge#6228.

What to move

Copy the contents of mcp-servers/python/mcp-rss-search/ from IBM/mcp-context-forge verbatim:

mcp-servers/python/mcp-rss-search/
├── Containerfile
├── Makefile
├── README.md
├── pyproject.toml
├── src/
│   └── mcp_rss_search/
│       ├── __init__.py
│       └── server_fastmcp.py
├── test_live.sh
└── tests/

Dependencies (as-is)

From pyproject.toml:

fastmcp>=3.4.4
feedparser>=6.0.12
httpx>=0.28.1
orjson>=3.11.9
pydantic>=2.13.4
python-dateutil>=2.9.0.post0

The server is moved as-is. Version constraint updates are tracked separately (see sub-issues).

Acceptance criteria

  • Server lands at mcp-servers/python/mcp-rss-search/ in this repository
  • pyproject.toml is present and installable (pip install -e mcp-servers/python/mcp-rss-search)
  • Existing tests pass
  • CI covers the server (lint + test)
  • README updated to reflect new home

References

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.