[CHORE]: Move graphviz_server to mcp-servers/python/graphviz_server
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 70/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- python
- Domain
- backend, ci-cd, documentation, testing
Research direction
Compare the source at mcp-servers/python/graphviz_server/ in IBM/mcp-context-forge with the destination in this repository. Copy the listed files, verify pyproject.toml installs with pip install -e, and run the existing tests. Done means the server is present, the README reflects its new home, and CI covers lint and tests.
Written by the indexing model from the issue text.
Description
Summary
Move the graphviz_server MCP server from the mcp-context-forge monorepo into this repository at mcp-servers/python/graphviz_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/graphviz_server/ from IBM/mcp-context-forge verbatim:
mcp-servers/python/graphviz_server/
├── Containerfile
├── Makefile
├── README.md
├── pyproject.toml
├── src/
│ └── graphviz_server/
│ ├── __init__.py
│ └── server_fastmcp.py
└── tests/
Dependencies (as-is)
From pyproject.toml:
fastmcp>=3.4.4
pydantic>=2.13.4
The server is moved as-is. Version constraint updates are tracked separately (see sub-issues).
Acceptance criteria
- Server lands at
mcp-servers/python/graphviz_server/in this repository -
pyproject.tomlis present and installable (pip install -e mcp-servers/python/graphviz_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/graphviz_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 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 Half a day Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Qiskit/qiskit-ibm-runtime#3431 · 1 comment ·
Maintainers usually reply within 1 day
-
[Lesson] A compatibility-gate rejection is a verdict, not something to overwrite with --accept-riskOpenlesson-submission needs-ac pending-review
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Ikalus1988/MisakaNet#2870 ·
Maintainers usually reply within 1 day
-
feature:LinkChecker
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
digitalfabrik/integreat-cms#4594 ·
Maintainers usually reply within 5 days