Skip to content

chore: migrate MCP server from mark3labs/mcp-go to modelcontextprotocol/go-sdk#408

Open
cduggn wants to merge 5 commits into
mainfrom
chore/migrate-mcp-go-sdk
Open

chore: migrate MCP server from mark3labs/mcp-go to modelcontextprotocol/go-sdk#408
cduggn wants to merge 5 commits into
mainfrom
chore/migrate-mcp-go-sdk

Conversation

@cduggn

@cduggn cduggn commented Jan 28, 2026

Copy link
Copy Markdown
Owner

Summary

  • Replace third-party mark3labs/mcp-go (v0.32.0) with the official modelcontextprotocol/go-sdk (v1.2.0)
  • Typed handler arguments with automatic JSON schema inference from Go struct tags, eliminating manual argument parsing
  • Stable v1+ API with official MCP team support and protocol compatibility guarantees

Test plan

  • make build passes
  • make test — all tests pass
  • make lint — 0 issues
  • Manual test: ./bin/ccexplorer mcp serve with VSCode MCP client

🤖 Generated with Claude Code

cduggn and others added 5 commits January 17, 2026 14:08
- Update go.mod to require Go 1.25
- Update Dockerfile build stage to golang:1.25-alpine
- Update codeql.yml workflow to use Go 1.25

Closes #405

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Update golangci-lint to v2.8.0 for Go 1.25 compatibility
- Fix module path for v2 (github.com/golangci/golangci-lint/v2)
- Remove deprecated --sort-results flag

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
golangci-lint v2.x requires golangci-lint-action v7

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
…ol/go-sdk

Replace the third-party mark3labs/mcp-go (v0.32.0) with the official
modelcontextprotocol/go-sdk (v1.2.0). This brings official support,
typed handler arguments with automatic JSON schema inference from
struct tags, and a stable v1+ API.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
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