Migrate from `mark3labs/go-sdk` to Official `mcp/go-sdk`
Open
Nobody has claimed this yet.
dependencies
enhancement
go
- Dominant language
- Go
- Stars
- 2.2k
- Forks
- 300
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 184
Description
In ToolHive we use mark3labs go-sdk (https://github.com/mark3labs/mcp-go), now that the official go-sdk is 1.0.0 https://github.com/modelcontextprotocol/go-sdk, we should migrate to it. This ticket tracks that work.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inventorying ToolHive's use of mark3labs/go-sdk and compare those integrations with the official mcp/go-sdk 1.0.0 migration requirements. Trace each affected integration and verify that ToolHive's MCP server management and security behavior remains intact after the migration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100