[CHORE]: Move Python server template to mcp-servers/templates/python

Open Beginner friendly
#29 0 comments 0 reactions 0 assignees View on GitHub

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

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
  • cookiecutter can generate a working project from the template
  • Generated project installs and runs cleanly
  • README updated to reflect new home and updated scaffold instructions

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.