modelcontextprotocol / modelcontextprotocol/go-sdk

Proposal: progress reporting (analogue to FastMCP)

Open
#460 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

needs community feedback
Dominant language
Go
Stars
5.1k
Forks
543
Avg merge
1d 17h
Merged PRs (30d)
37

Description

Is your feature request related to a problem? Please describe.
For long running requests, I understand clients can provide a progress token - this can be used to notify about progress.
I'd like to see a convenience method as part of e.g. a tool to provide updates on progress, e.g. for larger up- and downloads.

Describe the solution you'd like
In FastMCP there's a way to do this with very convenient DX (see description: https://gofastmcp.com/servers/progress#progress-reporting) - essentially providing the current state and an optional total value in a function and updating it.

Describe alternatives you've considered
I've seen there's a notify func but I'm not sure if this covers what I need.

Additional context
As stated above, this is about long running requests (e.g. a download or upload of a larger file, processing many items etc.)

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.

Research direction

Start by comparing the FastMCP progress-reporting description linked in the issue with the Go SDK's existing notify function. Identify the appropriate server or client entry point and define the intended convenience API for current progress and an optional total; done should include coverage for long-running requests such as uploads, downloads, or item processing. No implementation files or tests are named.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
api, backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.