Skip to content

Fix FastMCP compatibility with MCP 1.16.0#6

Open
Hilo-Hilo wants to merge 2 commits intovrtejus:mainfrom
Hilo-Hilo:main
Open

Fix FastMCP compatibility with MCP 1.16.0#6
Hilo-Hilo wants to merge 2 commits intovrtejus:mainfrom
Hilo-Hilo:main

Conversation

@Hilo-Hilo
Copy link
Copy Markdown

Summary

Fixes compatibility with MCP 1.16.0 by updating the FastMCP initialization parameter.

Changes

  • Fixed FastMCP.init() to use instructions parameter instead of description
  • Updated uv.lock to MCP v1.16.0

Issue

Server fails to start with:

TypeError: FastMCP.__init__() got an unexpected keyword argument 'description'

Testing

  • Server starts successfully with MCP 1.16.0

- Change 'description' to 'instructions' parameter in FastMCP initialization
- Update uv.lock to MCP v1.16.0

Fixes TypeError: FastMCP.__init__() got an unexpected keyword argument 'description'
- Replace manual venv creation and pip install with single uv sync command
- Remove redundant activation steps (uv handles this automatically)
- Update step numbering (6 steps reduced to 5)
- Align with official MCP server installation patterns
- Ensures users install exact dependency versions from uv.lock
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant