[CHORE]: Move Python server template to mcp-servers/templates/python
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- Half a day
- Newbie friendliness
- 78/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- python
- Domain
- documentation, tooling
Research direction
Compare the source at IBM/mcp-context-forge/mcp-servers/templates/python with the destination mcp-servers/templates/python, then copy the listed template files verbatim. Use cookiecutter to generate a project and verify that the generated project installs and runs cleanly. Update the README with the new home and scaffold instructions.
Written by the indexing model from the issue text.
Description
Summary
Move the Python MCP server cookiecutter template from the mcp-context-forge monorepo into this repository at mcp-servers/templates/python/, as part of the MCP server migration tracked in IBM/mcp-context-forge#6228.
What to move
Copy the contents of mcp-servers/templates/python/ from IBM/mcp-context-forge verbatim:
mcp-servers/templates/python/
├── cookiecutter.json
└── {{cookiecutter.project_slug}}/
├── Containerfile
├── Makefile
├── README.md
├── pyproject.toml
├── src/
│ └── {{cookiecutter.package_name}}/
│ ├── __init__.py
│ └── server.py
└── tests/
└── test_server.py
Dependencies (as-is)
The template's pyproject.toml defaults to:
mcp>=1.0.0,<2
orjson>=3.11.5
pydantic>=2.5.0
The template is moved as-is. Version constraint alignment with the live servers is tracked separately (see sub-issues).
Acceptance criteria
- Template lands at
mcp-servers/templates/python/in this repository -
cookiecuttercan generate a working project from the template - Generated project installs and runs cleanly
- README updated to reflect new home and updated scaffold instructions
References
- Parent issue: IBM/mcp-context-forge#6228
- Source: https://github.com/IBM/mcp-context-forge/tree/main/mcp-servers/templates/python
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- Avg merge
- 4h 29m
- Merged PRs (30d)
- 1
Contributor 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
-
security
Difficulty 3/5 1-2 days Newbie friendliness 62/100
IBM/contextforge-examples#39 · 3 comments ·
-
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 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100