Skip to content

fix(gti-mcp): pin mcp>=1.23.0,<2.0 to resolve startup failure - #278

Merged
goog-cmmartin merged 1 commit into
mainfrom
kenn-forge/issue-277-gti-mcp-fails-to-start-due-to-incompatible-fastmcp-version-being
Aug 27, 2026
Merged

fix(gti-mcp): pin mcp>=1.23.0,<2.0 to resolve startup failure#278
goog-cmmartin merged 1 commit into
mainfrom
kenn-forge/issue-277-gti-mcp-fails-to-start-due-to-incompatible-fastmcp-version-being

Conversation

@dandye

@dandye dandye commented Aug 13, 2026

Copy link
Copy Markdown
Collaborator

Fixes #277

Pin explicit version constraint for mcp to prevent incompatible mcp 2.x releases from breaking the from mcp.server.fastmcp import FastMCP import at startup.

Changes

  • Pin mcp>=1.23.0,<2.0 in server/gti/pyproject.toml and server/gti/setup.py to remain on compatible MCP v1 server infrastructure.
  • Remove unused standalone fastmcp and uvicorn requirements (gti-mcp imports from mcp.server.fastmcp, which is part of the mcp SDK).

Root Cause

The gti-mcp server failed to start on fresh installations because mcp was not capped below 2.0. With mcp 2.x published on PyPI, package resolvers install 2.x where mcp.server.fastmcp is deprecated/removed and raises ModuleNotFoundError.

Verification

  • Verified in a clean virtual environment that mcp>=1.23.0,<2.0 installs and imports FastMCP and gti_mcp.server successfully.
  • Ran test suite: all 55 tests pass.

@dandye
dandye requested a review from a team August 13, 2026 13:28
@dandye
dandye force-pushed the kenn-forge/issue-277-gti-mcp-fails-to-start-due-to-incompatible-fastmcp-version-being branch from 26e190b to 038b13a Compare August 13, 2026 13:36
@google google deleted a comment from google-cla Bot Aug 13, 2026
@sat-tp

sat-tp commented Aug 24, 2026

Copy link
Copy Markdown

Please can we push this one through? It makes local MCP servers for Google SecOps a non-starter, unless there's a published workaround?

Pin explicit version constraint for mcp to prevent incompatible mcp 2.x
installations from breaking FastMCP import at runtime.

- mcp>=1.23.0,<2.0: Restrict to compatible v1 FastMCP API
- Remove standalone fastmcp and uvicorn dependencies (not used directly by gti-mcp)

Fixes #277
@dandye
dandye force-pushed the kenn-forge/issue-277-gti-mcp-fails-to-start-due-to-incompatible-fastmcp-version-being branch from 038b13a to 73ec01a Compare August 27, 2026 14:56
@dandye dandye changed the title fix(gti-mcp): pin FastMCP and uvicorn versions to resolve startup failure fix(gti-mcp): pin mcp>=1.23.0,<2.0 to resolve startup failure Aug 27, 2026

@goog-cmmartin goog-cmmartin left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@goog-cmmartin
goog-cmmartin merged commit 31a1bbb into main Aug 27, 2026
6 checks passed
pull Bot pushed a commit to quansat775-ux/mcp-security that referenced this pull request Aug 27, 2026
- google-secops-mcp: bump to 0.7.1 and pin mcp[cli]>=1.26.0,<2.0
- gti-mcp: bump to 0.1.3 (mcp>=1.23.0,<2.0 pinned in google#278)
- secops-soar-mcp: bump to 0.1.2 and pin mcp[cli]>=1.4.1,<2.0
- scc-mcp: bump to 0.1.1 and pin mcp[cli]>=1.4.1,<2.0
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.

gti-mcp fails to start due to incompatible FastMCP version being installed automatically

3 participants