fix: python mcp.server dependencies - mcp-foundry unusable as currently written.

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

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
backend

Research direction

Start with pyproject.toml and the MCP migration guide linked in the issue. Check the currently resolved mcp version and whether the repository builds with the 1.29 pin; the intended choice between pinning and migration should be clarified before expanding the scope. Done means the repository is usable with a compatible MCP dependency.

Written by the indexing model from the issue text.

Description

The current release of the standard mcp library has had significant rewrites since this mcp-foundry was written.

See: https://py.sdk.modelcontextprotocol.io/migration/

If I build this repo, it pulls the mcp v2.0 release, which is incompatible with this codebase.

The simplest fix is to pin the release # in the pyproject.toml to 1.29.

The better fix is to migrate the code.

Dominant language
Python
Stars
260
Forks
121
No merged PRs in 30d

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 microsoft-foundry/mcp-foundry

All issues in microsoft-foundry/mcp-foundry

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.