[CHORE]: Move data_analysis_server to mcp-servers/python/data_analysis_server
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 72/100
Research direction
Compare the source tree at IBM/mcp-context-forge with the target mcp-servers/python/data_analysis_server/ path, including pyproject.toml, tests/, README.md, and CI configuration. Install it with pip install -e mcp-servers/python/data_analysis_server, run the existing tests, and verify that lint and test CI covers the server and the README reflects its new home.
Written by the indexing model from the issue text.
Description
Summary
Move the data_analysis_server MCP server from the mcp-context-forge monorepo into this repository at mcp-servers/python/data_analysis_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/data_analysis_server/ from IBM/mcp-context-forge verbatim:
mcp-servers/python/data_analysis_server/
├── Containerfile
├── Makefile
├── README.md
├── config.yaml
├── examples/
├── pyproject.toml
├── requirements.txt
├── sample_data/
├── src/
│ └── data_analysis_server/
└── tests/
Dependencies (as-is)
From pyproject.toml:
mcp>=1.28.1,<2
matplotlib>=3.11.1
numpy>=2.5.1
pandas>=3.0.5
...
The server is moved as-is. Version constraint updates are tracked separately (see sub-issues).
Acceptance criteria
- Server lands at
mcp-servers/python/data_analysis_server/in this repository -
pyproject.tomlis present and installable (pip install -e mcp-servers/python/data_analysis_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/data_analysis_server
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- Avg merge
- 1h 13m
- Merged PRs (30d)
- 8
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 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
IBM/contextforge-examples#55 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
IBM/contextforge-examples#37 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
IBM/contextforge-examples#38 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
IBM/contextforge-examples#32 ·
Maintainers usually reply within 1 day
All issues in IBM/contextforge-examples
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
QuantEcon/lecture-python-programming#642 ·
Maintainers usually reply within 1 day
-
area/config area/profiles comp/cli needs-decision P3 sweeper:risk-compatibility type/feature
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
NousResearch/hermes-agent#133697 ·
Maintainers usually reply within 1 day
-
enhancement needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
core
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
vectorize-io/hindsight#5279 ·
Maintainers usually reply within 1 day