example: add example in progress - #271

Merged
jokemanfire merged 1 commit into
modelcontextprotocol:mainfrom
jokemanfire:progress
Sep 13, 2025
Merged

example: add example in progress#271
jokemanfire merged 1 commit into
modelcontextprotocol:mainfrom
jokemanfire:progress

Conversation

@jokemanfire

@jokemanfirejokemanfire commented Jun 18, 2025

Copy link
Copy Markdown
Member

Motivation and Context

add a example to introduce progress

How Has This Been Tested?

Breaking Changes

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

@github-actionsgithub-actionsBot added T-documentation Documentation improvements T-dependencies Dependencies related changes T-config Configuration file changes T-examples Example code changes labels Jun 18, 2025
@jokemanfirejokemanfire mentioned this pull request Jun 18, 2025
Closed
@schwifty-brows

schwifty-brows commented Jun 18, 2025

Copy link
Copy Markdown

i see the "simualte getting from a stream" but to really test, i would create a stream and process the resulting stream

@schwifty-brows

schwifty-brows commented Jun 18, 2025

Copy link
Copy Markdown

after that is added and you run the test, you should be able to see the return inconsistency

alexhancock
alexhancock previously approved these changes Jun 20, 2025
View reviewed changes

@alexhancockalexhancock left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM

@alexhancock

alexhancock commented Jun 20, 2025

Copy link
Copy Markdown
Contributor

I was able to verify/successfully run the example @schwifty-brows via python3 progress_test_client.py in examples/clients/scripts

Screenshot 2025-06-20 at 11 49 45 AM

Were you running into something different than me?

@schwifty-brows

schwifty-brows commented Jun 20, 2025 via email

Copy link
Copy Markdown

@github-actionsgithub-actionsBot added the T-test Testing related changes label Jun 21, 2025
@jokemanfire

jokemanfire commented Jun 21, 2025•
edited
Loading

Copy link
Copy Markdown
MemberAuthor

I think it is not rmcp's problem , I think it should be your business flow problem @schwifty-brows . And I have tested all the transport.

The current example file structure is not very good. In fact, this example is better placed in an integration test. I will modify this structure in another pr. @alexhancock

@schwifty-brows

schwifty-brows commented Jun 21, 2025

Copy link
Copy Markdown

how should we be sending SSE messages back? the progress notification is meant to do this, but running a simple example does not consistently work

@jokemanfire

jokemanfire commented Jun 24, 2025

Copy link
Copy Markdown
MemberAuthor

how should we be sending SSE messages back? the progress notification is meant to do this, but running a simple example does not consistently work

I really find it difficult to reproduce the abnormal scenario you mentioned. In the example, I should have provided a relatively simple example to send progress notifications from the server and obtain notification messages from the client. If it is a problem with the basic components of MCP SDK, then I believe that integration testing can definitely reproduce it (after excluding business interference). Could you please try to provide test cases that can be reproduced after excluding business impact.

@schwifty-brows

schwifty-brows commented Jun 24, 2025•
edited
Loading

Copy link
Copy Markdown

maybe i am missing something (i probably am) but in the code example, i dont see anything like this

i have a tool definition like so


#[tool(description = "do something")]
async fn search_warhouse(
&self,
#[tool(param)]
#[schemars(description = "query")]
query: String,
ctx: RequestContext<RoleServer>
) -> Result<CallToolResult, ErrorData>

and in my example 
//inject some strings into query_results
let mut query_results: Vec<String> = vec![];
let mut counter = 0;
for i in 0..query_results.len() {
let t = query_results[i].to_string();
let progress_param = ProgressNotificationParam {
progress_token: ProgressToken(NumberOrString::Number(counter)),
progress: counter,
total: Some(query_results.len() as u32),
message: Some("test".to_string()),
};
match ctx.peer.notify_progress(progress_param).await {
Ok(_) => {
counter += 1;
debug!("progress notification sent");
}
Err(e) => {
return Err(rmcp::Error::internal_error(
format!("failed to notify progress: {}", e),
Some(e.to_string().parse().unwrap())
));
}
}
}

ctx.peer.notify_progress is used to send the notification. This is the problem area in question i dont see this as part of the example and where i keep getting 1-n notifications. If this is not the recommended way, that might be the problem

@alexhancock

alexhancock commented Jun 24, 2025

Copy link
Copy Markdown
Contributor

This part of the example server here seems relevant, and very similar to the ctx.peer.notify_progress example you're looking for @schwifty-brows

Does that make sense? Or if not maybe it's just github communication tripping me up from understanding. I would be happy to jump on a quick video call if you want tomorrow to discuss/get clear and identify any required improvements at the SDK level.

@schwifty-brows

schwifty-brows commented Jun 24, 2025

Copy link
Copy Markdown

Hey @alexhancock i think that would be a great idea!

Let me know your availability and I can walk you through the real world use case here.

@alexhancock

alexhancock commented Jun 25, 2025•
edited
Loading

Copy link
Copy Markdown
Contributor

Hey @alexhancock i think that would be a great idea!

Let me know your availability and I can walk you through the real world use case here.

@schwifty-brows How about 10am US eastern tomorrow? Email me (address on my profile) and we can set a meet.

@jokemanfirejokemanfire mentioned this pull request Jun 25, 2025
Merged
9 tasks
@alexhancock

alexhancock commented Jun 25, 2025

Copy link
Copy Markdown
Contributor

@schwifty-brows@jokemanfire I think it may be a client difference...

When I run cargo run --example clients_progress_test_client -- --transport sse it works

�[2m2025-06-25T14:36:54.750050Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m RMCP Progress Notification Test Client
�[2m2025-06-25T14:36:54.750186Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m ==========================================
�[2m2025-06-25T14:36:54.750220Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Testing SSE Transport
�[2m2025-06-25T14:36:54.750229Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m =========================
�[2m2025-06-25T14:36:54.750237Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m SSE URL: http://127.0.0.1:8000/sse
�[2m2025-06-25T14:36:55.779656Z�[0m �[32m INFO�[0m �[1mserve_inner�[0m�[2m:�[0m �[2mrmcp::service�[0m�[2m:�[0m Service initialized as client �[3mpeer_info�[0m�[2m=�[0mSome(InitializeResult { protocol_version: ProtocolVersion("2024-11-05"), capabilities: ServerCapabilities { experimental: None, logging: None, completions: None, prompts: None, resources: None, tools: Some(ToolsCapability { list_changed: None }) }, server_info: Implementation { name: "rmcp", version: "0.1.5" }, instructions: Some("This server demonstrates progress notifications during long-running operations. Use the tools to see real-time progress updates for batch processing") })
�[2m2025-06-25T14:36:55.779944Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Connected to server: "rmcp"
�[2m2025-06-25T14:36:55.781660Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Available tools: ["stream_processor"]
�[2m2025-06-25T14:36:55.781674Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Starting to process 10 records...
�[2m2025-06-25T14:36:55.782563Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(1)), progress: 1, total: None, message: Some("H") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.782662Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [1]: 1/0 - H (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.782745Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(2)), progress: 2, total: None, message: Some("e") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.782804Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [2]: 2/0 - e (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.782893Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(3)), progress: 3, total: None, message: Some("l") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.782944Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [3]: 3/0 - l (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783056Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(4)), progress: 4, total: None, message: Some("l") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783124Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [4]: 4/0 - l (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783177Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(5)), progress: 5, total: None, message: Some("o") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783216Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [5]: 5/0 - o (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783289Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(6)), progress: 6, total: None, message: Some(",") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783339Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [6]: 6/0 - , (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783409Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(7)), progress: 7, total: None, message: Some(" ") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783450Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [7]: 7/0 - (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783509Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(8)), progress: 8, total: None, message: Some("w") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783549Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [8]: 8/0 - w (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783598Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(9)), progress: 9, total: None, message: Some("o") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783636Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [9]: 9/0 - o (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783690Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(10)), progress: 10, total: None, message: Some("r") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783725Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [10]: 10/0 - r (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783777Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(11)), progress: 11, total: None, message: Some("l") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783811Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [11]: 11/0 - l (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783858Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(12)), progress: 12, total: None, message: Some("d") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783893Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [12]: 12/0 - d (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783941Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(13)), progress: 13, total: None, message: Some("!") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783973Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [13]: 13/0 - ! (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.784108Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Processing completed: Processed 13 records successfully
�[2m2025-06-25T14:36:55.784174Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m task cancelled
�[2m2025-06-25T14:36:55.784195Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m serve finished �[3mquit_reason�[0m�[2m=�[0mCancelled
�[2m2025-06-25T14:36:55.784352Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Total progress notifications received: 13
�[2m2025-06-25T14:36:55.784370Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Total time elapsed: 0.01s
�[2m2025-06-25T14:36:55.784383Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m SSE transport test completed successfully!

However when I use the MCP inspector as another client to test with by running

cargo run --example servers_progress_demo -- sse

and connect to it via

npx @modelcontextprotocol/inspector

I see this when I run the stream processor tool I only see one progress notification despite it processing 13 records. This is similar to what @schwifty-brows reproduces with his test client:

Screenshot 2025-06-25 at 10 36 08 AM

@jokemanfire Any ideas?

@jokemanfire

jokemanfire commented Jun 26, 2025

Copy link
Copy Markdown
MemberAuthor

It does seem to be related to the client, I will take a look at the inspector and compare the implementation differences.

@jokemanfire

jokemanfire commented Jun 26, 2025•
edited
Loading

Copy link
Copy Markdown
MemberAuthor

I used Wireshark to capture packets, and I can confirm that the notify packet for Rust SDK was sent. I may need to take a look at the inspector code now.
image

All the [PSH,ACK] is the data.

@jokemanfire

jokemanfire commented Jun 26, 2025•
edited
Loading

Copy link
Copy Markdown
MemberAuthor

I have add log in inspector , I can make sure the mcpProxy recived the progress data, the problem should in inspector's front end.

[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":1,"progress":1,"total":13,"message":"H"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":1,"progress":1,"total":13,"message":"H"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":2,"progress":2,"total":13,"message":"e"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":2,"progress":2,"total":13,"message":"e"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":3,"progress":3,"total":13,"message":"l"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":3,"progress":3,"total":13,"message":"l"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":4,"progress":4,"total":13,"message":"l"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":4,"progress":4,"total":13,"message":"l"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":5,"progress":5,"total":13,"message":"o"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":5,"progress":5,"total":13,"message":"o"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":6,"progress":6,"total":13,"message":","}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":6,"progress":6,"total":13,"message":","}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":7,"progress":7,"total":13,"message":" "}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":7,"progress":7,"total":13,"message":" "}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":8,"progress":8,"total":13,"message":"w"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":8,"progress":8,"total":13,"message":"w"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":9,"progress":9,"total":13,"message":"o"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":9,"progress":9,"total":13,"message":"o"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":10,"progress":10,"total":13,"message":"r"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":10,"progress":10,"total":13,"message":"r"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":11,"progress":11,"total":13,"message":"l"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":11,"progress":11,"total":13,"message":"l"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":12,"progress":12,"total":13,"message":"d"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":12,"progress":12,"total":13,"message":"d"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":13,"progress":13,"total":13,"message":"!"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":13,"progress":13,"total":13,"message":"!"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","id":4,"result":{"content":[{"type":"text","text":"Processed 13 records successfully"}],"isError":false}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","id":4,"result":{"content":[{"type":"text","text":"Processed 13 records successfully"}],"isError":false}}

@jokemanfire

jokemanfire commented Jun 26, 2025

Copy link
Copy Markdown
MemberAuthor

Hello @olaservo If you have time, can you help me take a look?

@alexhancock

alexhancock commented Jun 27, 2025

Copy link
Copy Markdown
Contributor

So just to be clear, this is looking to everyone now like a client only issue?

@schwifty-brows Did you repro this only with inspector, or with a client in your actual codebase as well?

@jokemanfire

jokemanfire commented Jul 1, 2025

Copy link
Copy Markdown
MemberAuthor

Sorry for the update, the issue may be due to differences in the implementation of typescript-sdk.

@alexhancock

alexhancock commented Jul 3, 2025

Copy link
Copy Markdown
Contributor

@schwifty-brows Did this ever work for you with a different client?

@alexhancock

alexhancock commented Sep 10, 2025

Copy link
Copy Markdown
Contributor

@jokemanfire Do we want to rebase this one, and merge the example?

And then on the issues with progress notifications generally, @schwifty-brows last I looked it seemed to be an issue only with non rust-sdk clients. Have you verified if there is a client you can use that works with the server implementation of rust-sdk for sending progress notifications?

@jokemanfire

jokemanfire commented Sep 11, 2025

Copy link
Copy Markdown
MemberAuthor

@jokemanfire Do we want to rebase this one, and merge the example?

And then on the issues with progress notifications generally, @schwifty-brows last I looked it seemed to be an issue only with non rust-sdk clients. Have you verified if there is a client you can use that works with the server implementation of rust-sdk for sending progress notifications?

I will rebase it , providing richer examples can reduce the burden of development.
Regarding the differences in the implementation progress of the typescript SDK, I may not have time to take a look as I am not familiar with this language.

@github-actionsgithub-actionsBot removed the T-test Testing related changes label Sep 12, 2025
@jokemanfire
chore(example): add example in progress
0e5abb0
Signed-off-by: jokemanfire <hu.dingyang@zte.com.cn>
@jokemanfire

jokemanfire commented Sep 12, 2025

Copy link
Copy Markdown
MemberAuthor

@alexhancock I will put most of the examples into system testing later when I have time.

@jokemanfire
jokemanfire merged commit f8a747e into modelcontextprotocol:mainSep 13, 2025
11 checks passed
takumi-earth pushed a commit to earthlings-dev/rmcp that referenced this pull request Jan 27, 2026
@jokemanfire
chore(example): add example in progress (modelcontextprotocol#271)
6492d12
Signed-off-by: jokemanfire <hu.dingyang@zte.com.cn>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@alexhancockalexhancockalexhancock approved these changes

Assignees

No one assigned

Labels

T-configConfiguration file changesT-dependenciesDependencies related changesT-documentationDocumentation improvementsT-examplesExample code changes

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@jokemanfire@schwifty-brows@alexhancock
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all 
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '

Skip to content
example: add example in progress - #271
Merged
jokemanfire merged 1 commit into
modelcontextprotocol:mainfrom 
jokemanfire:progress
Sep 13, 2025
Merged
example: add example in progress#271
jokemanfire merged 1 commit into
modelcontextprotocol:mainfrom 
jokemanfire:progress
Conversation
@jokemanfire
@jokemanfirejokemanfire
commented
Jun 18, 2025

Copy link


Copy Markdown

Member
Motivation and Context
add a example to introduce progress
How Has This Been Tested?
Breaking Changes
Types of changes
  •  Bug fix (non-breaking change which fixes an issue)
  •  New feature (non-breaking change which adds functionality)
  •  Breaking change (fix or feature that would cause existing functionality to change)
  •  Documentation update
Checklist
  •  I have read the MCP Documentation
  •  My code follows the repository's style guidelines
  •  New and existing tests pass locally
  •  I have added appropriate error handling
  •  I have added or updated documentation as needed
Additional context
@github-actionsgithub-actionsBot
added

T-documentation
Documentation improvements
T-dependencies
Dependencies related changes
T-config
Configuration file changes
T-examples
Example code changes
labels
Jun 18, 2025
@jokemanfirejokemanfire
mentioned this pull request
Jun 18, 2025

Closed

@schwifty-brows
schwifty-brows
commented
Jun 18, 2025

Copy link


Copy Markdown

i see the "simualte getting from a stream" but to really test, i would create a stream and process the resulting stream
@schwifty-brows
schwifty-brows
commented
Jun 18, 2025

Copy link


Copy Markdown

after that is added and you run the test, you should be able to see the return inconsistency
alexhancock
alexhancock
previously approved these changes
Jun 20, 2025
View reviewed changes
@alexhancockalexhancock
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

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

LGTM
@alexhancock
alexhancock
commented
Jun 20, 2025

Copy link


Copy Markdown

Contributor
I was able to verify/successfully run the example @schwifty-brows via python3 progress_test_client.py in examples/clients/scripts
Screenshot 2025-06-20 at 11 49 45 AM
Were you running into something different than me?
@schwifty-brows
schwifty-brows
commented
Jun 20, 2025
via email 

Copy link


Copy Markdown

@github-actionsgithub-actionsBot
added
the 
T-test
Testing related changes
label
Jun 21, 2025
@jokemanfire
jokemanfire
commented
Jun 21, 2025•

edited

Loading

Copy link


Copy Markdown

MemberAuthor
I think it is not rmcp's problem , I think it should be your business flow problem @schwifty-brows . And I have tested all the transport.
The current example file structure is not very good. In fact, this example is better placed in an integration test. I will modify this structure in another pr. @alexhancock
@schwifty-brows
schwifty-brows
commented
Jun 21, 2025

Copy link


Copy Markdown

how should we be sending SSE messages back? the progress notification is meant to do this, but running a simple example does not consistently work
@jokemanfire
jokemanfire
commented
Jun 24, 2025

Copy link


Copy Markdown

MemberAuthor
how should we be sending SSE messages back? the progress notification is meant to do this, but running a simple example does not consistently work
I really find it difficult to reproduce the abnormal scenario you mentioned. In the example, I should have provided a relatively simple example to send progress notifications from the server and obtain notification messages from the client. If it is a problem with the basic components of MCP SDK, then I believe that integration testing can definitely reproduce it (after excluding business interference). Could you please try to provide test cases that can be reproduced after excluding business impact.
@schwifty-brows
schwifty-brows
commented
Jun 24, 2025•

edited

Loading

Copy link


Copy Markdown

maybe i am missing something (i probably am) but in the code example, i dont see anything like this
i have a tool definition like so

#[tool(description = "do something")]
async fn search_warhouse(
&self,
#[tool(param)]
#[schemars(description = "query")]
query: String,
ctx: RequestContext<RoleServer>
) -> Result<CallToolResult, ErrorData>

and in my example 
//inject some strings into query_results
let mut query_results: Vec<String> = vec![];
let mut counter = 0;
for i in 0..query_results.len() {
let t = query_results[i].to_string();
let progress_param = ProgressNotificationParam {
progress_token: ProgressToken(NumberOrString::Number(counter)),
progress: counter,
total: Some(query_results.len() as u32),
message: Some("test".to_string()),
};
match ctx.peer.notify_progress(progress_param).await {
Ok(_) => {
counter += 1;
debug!("progress notification sent");
}
Err(e) => {
return Err(rmcp::Error::internal_error(
format!("failed to notify progress: {}", e),
Some(e.to_string().parse().unwrap())
));
}
}
}

 ctx.peer.notify_progress is used to send the notification. This is the problem area in question i dont see this as part of the example and where i keep getting 1-n notifications. If this is not the recommended way, that might be the problem
@alexhancock
alexhancock
commented
Jun 24, 2025

Copy link


Copy Markdown

Contributor
This part of the example server here seems relevant, and very similar to the ctx.peer.notify_progress example you're looking for @schwifty-brows
Does that make sense? Or if not maybe it's just github communication tripping me up from understanding. I would be happy to jump on a quick video call if you want tomorrow to discuss/get clear and identify any required improvements at the SDK level.
@schwifty-brows
schwifty-brows
commented
Jun 24, 2025

Copy link


Copy Markdown

Hey @alexhancock i think that would be a great idea!
Let me know your availability and I can walk you through the real world use case here.
@alexhancock
alexhancock
commented
Jun 25, 2025•

edited

Loading

Copy link


Copy Markdown

Contributor
Hey @alexhancock i think that would be a great idea!
Let me know your availability and I can walk you through the real world use case here.
@schwifty-brows How about 10am US eastern tomorrow? Email me (address on my profile) and we can set a meet.
@jokemanfirejokemanfire
mentioned this pull request
Jun 25, 2025
 Merged

9 tasks
@alexhancock
alexhancock
commented
Jun 25, 2025

Copy link


Copy Markdown

Contributor
@schwifty-brows@jokemanfire I think it may be a client difference...
When I run cargo run --example clients_progress_test_client -- --transport sse it works
�[2m2025-06-25T14:36:54.750050Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m RMCP Progress Notification Test Client
�[2m2025-06-25T14:36:54.750186Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m ==========================================
�[2m2025-06-25T14:36:54.750220Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Testing SSE Transport
�[2m2025-06-25T14:36:54.750229Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m =========================
�[2m2025-06-25T14:36:54.750237Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m SSE URL: http://127.0.0.1:8000/sse
�[2m2025-06-25T14:36:55.779656Z�[0m �[32m INFO�[0m �[1mserve_inner�[0m�[2m:�[0m �[2mrmcp::service�[0m�[2m:�[0m Service initialized as client �[3mpeer_info�[0m�[2m=�[0mSome(InitializeResult { protocol_version: ProtocolVersion("2024-11-05"), capabilities: ServerCapabilities { experimental: None, logging: None, completions: None, prompts: None, resources: None, tools: Some(ToolsCapability { list_changed: None }) }, server_info: Implementation { name: "rmcp", version: "0.1.5" }, instructions: Some("This server demonstrates progress notifications during long-running operations. Use the tools to see real-time progress updates for batch processing") })
�[2m2025-06-25T14:36:55.779944Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Connected to server: "rmcp"
�[2m2025-06-25T14:36:55.781660Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Available tools: ["stream_processor"]
�[2m2025-06-25T14:36:55.781674Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Starting to process 10 records...
�[2m2025-06-25T14:36:55.782563Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(1)), progress: 1, total: None, message: Some("H") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.782662Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [1]: 1/0 - H (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.782745Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(2)), progress: 2, total: None, message: Some("e") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.782804Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [2]: 2/0 - e (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.782893Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(3)), progress: 3, total: None, message: Some("l") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.782944Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [3]: 3/0 - l (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783056Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(4)), progress: 4, total: None, message: Some("l") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783124Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [4]: 4/0 - l (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783177Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(5)), progress: 5, total: None, message: Some("o") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783216Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [5]: 5/0 - o (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783289Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(6)), progress: 6, total: None, message: Some(",") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783339Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [6]: 6/0 - , (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783409Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(7)), progress: 7, total: None, message: Some(" ") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783450Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [7]: 7/0 - (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783509Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(8)), progress: 8, total: None, message: Some("w") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783549Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [8]: 8/0 - w (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783598Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(9)), progress: 9, total: None, message: Some("o") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783636Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [9]: 9/0 - o (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783690Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(10)), progress: 10, total: None, message: Some("r") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783725Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [10]: 10/0 - r (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783777Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(11)), progress: 11, total: None, message: Some("l") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783811Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [11]: 11/0 - l (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783858Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(12)), progress: 12, total: None, message: Some("d") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783893Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [12]: 12/0 - d (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783941Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(13)), progress: 13, total: None, message: Some("!") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783973Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [13]: 13/0 - ! (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.784108Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Processing completed: Processed 13 records successfully
�[2m2025-06-25T14:36:55.784174Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m task cancelled
�[2m2025-06-25T14:36:55.784195Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m serve finished �[3mquit_reason�[0m�[2m=�[0mCancelled
�[2m2025-06-25T14:36:55.784352Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Total progress notifications received: 13
�[2m2025-06-25T14:36:55.784370Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Total time elapsed: 0.01s
�[2m2025-06-25T14:36:55.784383Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m SSE transport test completed successfully!

However when I use the MCP inspector as another client to test with by running
cargo run --example servers_progress_demo -- sse

and connect to it via
npx @modelcontextprotocol/inspector

I see this when I run the stream processor tool I only see one progress notification despite it processing 13 records. This is similar to what @schwifty-brows reproduces with his test client:
Screenshot 2025-06-25 at 10 36 08 AM
@jokemanfire Any ideas?
@jokemanfire
jokemanfire
commented
Jun 26, 2025

Copy link


Copy Markdown

MemberAuthor
It does seem to be related to the client, I will take a look at the inspector and compare the implementation differences.
@jokemanfire
jokemanfire
commented
Jun 26, 2025•

edited

Loading

Copy link


Copy Markdown

MemberAuthor
I used Wireshark to capture packets, and I can confirm that the notify packet for Rust SDK was sent. I may need to take a look at the inspector code now.
image
All the [PSH,ACK] is the data.
@jokemanfire
jokemanfire
commented
Jun 26, 2025•

edited

Loading

Copy link


Copy Markdown

MemberAuthor
I have add log in inspector , I can make sure the mcpProxy recived the progress data, the problem should in inspector's front end.
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":1,"progress":1,"total":13,"message":"H"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":1,"progress":1,"total":13,"message":"H"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":2,"progress":2,"total":13,"message":"e"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":2,"progress":2,"total":13,"message":"e"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":3,"progress":3,"total":13,"message":"l"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":3,"progress":3,"total":13,"message":"l"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":4,"progress":4,"total":13,"message":"l"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":4,"progress":4,"total":13,"message":"l"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":5,"progress":5,"total":13,"message":"o"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":5,"progress":5,"total":13,"message":"o"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":6,"progress":6,"total":13,"message":","}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":6,"progress":6,"total":13,"message":","}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":7,"progress":7,"total":13,"message":" "}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":7,"progress":7,"total":13,"message":" "}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":8,"progress":8,"total":13,"message":"w"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":8,"progress":8,"total":13,"message":"w"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":9,"progress":9,"total":13,"message":"o"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":9,"progress":9,"total":13,"message":"o"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":10,"progress":10,"total":13,"message":"r"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":10,"progress":10,"total":13,"message":"r"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":11,"progress":11,"total":13,"message":"l"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":11,"progress":11,"total":13,"message":"l"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":12,"progress":12,"total":13,"message":"d"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":12,"progress":12,"total":13,"message":"d"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":13,"progress":13,"total":13,"message":"!"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":13,"progress":13,"total":13,"message":"!"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","id":4,"result":{"content":[{"type":"text","text":"Processed 13 records successfully"}],"isError":false}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","id":4,"result":{"content":[{"type":"text","text":"Processed 13 records successfully"}],"isError":false}}

@jokemanfire
jokemanfire
commented
Jun 26, 2025

Copy link


Copy Markdown

MemberAuthor
Hello @olaservo If you have time, can you help me take a look?
@alexhancock
alexhancock
commented
Jun 27, 2025

Copy link


Copy Markdown

Contributor
So just to be clear, this is looking to everyone now like a client only issue?
@schwifty-brows Did you repro this only with inspector, or with a client in your actual codebase as well?
@jokemanfire
jokemanfire
commented
Jul 1, 2025

Copy link


Copy Markdown

MemberAuthor
Sorry for the update, the issue may be due to differences in the implementation of typescript-sdk.
@alexhancock
alexhancock
commented
Jul 3, 2025

Copy link


Copy Markdown

Contributor
@schwifty-brows Did this ever work for you with a different client?
@alexhancock
alexhancock
commented
Sep 10, 2025

Copy link


Copy Markdown

Contributor
@jokemanfire Do we want to rebase this one, and merge the example?
And then on the issues with progress notifications generally, @schwifty-brows last I looked it seemed to be an issue only with non rust-sdk clients. Have you verified if there is a client you can use that works with the server implementation of rust-sdk for sending progress notifications?
@jokemanfire
jokemanfire
commented
Sep 11, 2025

Copy link


Copy Markdown

MemberAuthor
@jokemanfire Do we want to rebase this one, and merge the example?
And then on the issues with progress notifications generally, @schwifty-brows last I looked it seemed to be an issue only with non rust-sdk clients. Have you verified if there is a client you can use that works with the server implementation of rust-sdk for sending progress notifications?
I will rebase it , providing richer examples can reduce the burden of development.

Regarding the differences in the implementation progress of the typescript SDK, I may not have time to take a look as I am not familiar with this language.
@github-actionsgithub-actionsBot
removed
the 
T-test
Testing related changes
label
Sep 12, 2025
@jokemanfire
chore(example): add example in progress
0e5abb0
Signed-off-by: jokemanfire <hu.dingyang@zte.com.cn>
@jokemanfire
jokemanfire
commented
Sep 12, 2025

Copy link


Copy Markdown

MemberAuthor
@alexhancock I will put most of the examples into system testing later when I have time.
@jokemanfire
jokemanfire
merged commit f8a747e
into
modelcontextprotocol:mainSep 13, 2025

11 checks passed

takumi-earth pushed a commit
to earthlings-dev/rmcp
that referenced
this pull request
Jan 27, 2026
@jokemanfire
chore(example): add example in progress (modelcontextprotocol#271)
6492d12
Signed-off-by: jokemanfire <hu.dingyang@zte.com.cn>
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@alexhancockalexhancockalexhancock approved these changes

Assignees


No one assigned


Labels

T-configConfiguration file changesT-dependenciesDependencies related changesT-documentationDocumentation improvementsT-examplesExample code changes

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

3 participants

@jokemanfire@schwifty-brows@alexhancock

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix");
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
example: add example in progress - #271
Merged
jokemanfire merged 1 commit into
modelcontextprotocol:mainfrom 
jokemanfire:progress
Sep 13, 2025
Merged
example: add example in progress#271
jokemanfire merged 1 commit into
modelcontextprotocol:mainfrom 
jokemanfire:progress
Conversation
@jokemanfire
@jokemanfirejokemanfire
commented
Jun 18, 2025

Copy link


Copy Markdown

Member
Motivation and Context
add a example to introduce progress
How Has This Been Tested?
Breaking Changes
Types of changes
  •  Bug fix (non-breaking change which fixes an issue)
  •  New feature (non-breaking change which adds functionality)
  •  Breaking change (fix or feature that would cause existing functionality to change)
  •  Documentation update
Checklist
  •  I have read the MCP Documentation
  •  My code follows the repository's style guidelines
  •  New and existing tests pass locally
  •  I have added appropriate error handling
  •  I have added or updated documentation as needed
Additional context
@github-actionsgithub-actionsBot
added

T-documentation
Documentation improvements
T-dependencies
Dependencies related changes
T-config
Configuration file changes
T-examples
Example code changes
labels
Jun 18, 2025
@jokemanfirejokemanfire
mentioned this pull request
Jun 18, 2025

Closed

@schwifty-brows
schwifty-brows
commented
Jun 18, 2025

Copy link


Copy Markdown

i see the "simualte getting from a stream" but to really test, i would create a stream and process the resulting stream
@schwifty-brows
schwifty-brows
commented
Jun 18, 2025

Copy link


Copy Markdown

after that is added and you run the test, you should be able to see the return inconsistency
alexhancock
alexhancock
previously approved these changes
Jun 20, 2025
View reviewed changes
@alexhancockalexhancock
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

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

LGTM
@alexhancock
alexhancock
commented
Jun 20, 2025

Copy link


Copy Markdown

Contributor
I was able to verify/successfully run the example @schwifty-brows via python3 progress_test_client.py in examples/clients/scripts
Screenshot 2025-06-20 at 11 49 45 AM
Were you running into something different than me?
@schwifty-brows
schwifty-brows
commented
Jun 20, 2025
via email 

Copy link


Copy Markdown

@github-actionsgithub-actionsBot
added
the 
T-test
Testing related changes
label
Jun 21, 2025
@jokemanfire
jokemanfire
commented
Jun 21, 2025•

edited

Loading

Copy link


Copy Markdown

MemberAuthor
I think it is not rmcp's problem , I think it should be your business flow problem @schwifty-brows . And I have tested all the transport.
The current example file structure is not very good. In fact, this example is better placed in an integration test. I will modify this structure in another pr. @alexhancock
@schwifty-brows
schwifty-brows
commented
Jun 21, 2025

Copy link


Copy Markdown

how should we be sending SSE messages back? the progress notification is meant to do this, but running a simple example does not consistently work
@jokemanfire
jokemanfire
commented
Jun 24, 2025

Copy link


Copy Markdown

MemberAuthor
how should we be sending SSE messages back? the progress notification is meant to do this, but running a simple example does not consistently work
I really find it difficult to reproduce the abnormal scenario you mentioned. In the example, I should have provided a relatively simple example to send progress notifications from the server and obtain notification messages from the client. If it is a problem with the basic components of MCP SDK, then I believe that integration testing can definitely reproduce it (after excluding business interference). Could you please try to provide test cases that can be reproduced after excluding business impact.
@schwifty-brows
schwifty-brows
commented
Jun 24, 2025•

edited

Loading

Copy link


Copy Markdown

maybe i am missing something (i probably am) but in the code example, i dont see anything like this
i have a tool definition like so

#[tool(description = "do something")]
async fn search_warhouse(
&self,
#[tool(param)]
#[schemars(description = "query")]
query: String,
ctx: RequestContext<RoleServer>
) -> Result<CallToolResult, ErrorData>

and in my example 
//inject some strings into query_results
let mut query_results: Vec<String> = vec![];
let mut counter = 0;
for i in 0..query_results.len() {
let t = query_results[i].to_string();
let progress_param = ProgressNotificationParam {
progress_token: ProgressToken(NumberOrString::Number(counter)),
progress: counter,
total: Some(query_results.len() as u32),
message: Some("test".to_string()),
};
match ctx.peer.notify_progress(progress_param).await {
Ok(_) => {
counter += 1;
debug!("progress notification sent");
}
Err(e) => {
return Err(rmcp::Error::internal_error(
format!("failed to notify progress: {}", e),
Some(e.to_string().parse().unwrap())
));
}
}
}

 ctx.peer.notify_progress is used to send the notification. This is the problem area in question i dont see this as part of the example and where i keep getting 1-n notifications. If this is not the recommended way, that might be the problem
@alexhancock
alexhancock
commented
Jun 24, 2025

Copy link


Copy Markdown

Contributor
This part of the example server here seems relevant, and very similar to the ctx.peer.notify_progress example you're looking for @schwifty-brows
Does that make sense? Or if not maybe it's just github communication tripping me up from understanding. I would be happy to jump on a quick video call if you want tomorrow to discuss/get clear and identify any required improvements at the SDK level.
@schwifty-brows
schwifty-brows
commented
Jun 24, 2025

Copy link


Copy Markdown

Hey @alexhancock i think that would be a great idea!
Let me know your availability and I can walk you through the real world use case here.
@alexhancock
alexhancock
commented
Jun 25, 2025•

edited

Loading

Copy link


Copy Markdown

Contributor
Hey @alexhancock i think that would be a great idea!
Let me know your availability and I can walk you through the real world use case here.
@schwifty-brows How about 10am US eastern tomorrow? Email me (address on my profile) and we can set a meet.
@jokemanfirejokemanfire
mentioned this pull request
Jun 25, 2025
 Merged

9 tasks
@alexhancock
alexhancock
commented
Jun 25, 2025

Copy link


Copy Markdown

Contributor
@schwifty-brows@jokemanfire I think it may be a client difference...
When I run cargo run --example clients_progress_test_client -- --transport sse it works
�[2m2025-06-25T14:36:54.750050Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m RMCP Progress Notification Test Client
�[2m2025-06-25T14:36:54.750186Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m ==========================================
�[2m2025-06-25T14:36:54.750220Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Testing SSE Transport
�[2m2025-06-25T14:36:54.750229Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m =========================
�[2m2025-06-25T14:36:54.750237Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m SSE URL: http://127.0.0.1:8000/sse
�[2m2025-06-25T14:36:55.779656Z�[0m �[32m INFO�[0m �[1mserve_inner�[0m�[2m:�[0m �[2mrmcp::service�[0m�[2m:�[0m Service initialized as client �[3mpeer_info�[0m�[2m=�[0mSome(InitializeResult { protocol_version: ProtocolVersion("2024-11-05"), capabilities: ServerCapabilities { experimental: None, logging: None, completions: None, prompts: None, resources: None, tools: Some(ToolsCapability { list_changed: None }) }, server_info: Implementation { name: "rmcp", version: "0.1.5" }, instructions: Some("This server demonstrates progress notifications during long-running operations. Use the tools to see real-time progress updates for batch processing") })
�[2m2025-06-25T14:36:55.779944Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Connected to server: "rmcp"
�[2m2025-06-25T14:36:55.781660Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Available tools: ["stream_processor"]
�[2m2025-06-25T14:36:55.781674Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Starting to process 10 records...
�[2m2025-06-25T14:36:55.782563Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(1)), progress: 1, total: None, message: Some("H") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.782662Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [1]: 1/0 - H (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.782745Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(2)), progress: 2, total: None, message: Some("e") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.782804Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [2]: 2/0 - e (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.782893Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(3)), progress: 3, total: None, message: Some("l") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.782944Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [3]: 3/0 - l (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783056Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(4)), progress: 4, total: None, message: Some("l") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783124Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [4]: 4/0 - l (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783177Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(5)), progress: 5, total: None, message: Some("o") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783216Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [5]: 5/0 - o (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783289Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(6)), progress: 6, total: None, message: Some(",") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783339Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [6]: 6/0 - , (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783409Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(7)), progress: 7, total: None, message: Some(" ") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783450Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [7]: 7/0 - (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783509Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(8)), progress: 8, total: None, message: Some("w") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783549Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [8]: 8/0 - w (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783598Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(9)), progress: 9, total: None, message: Some("o") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783636Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [9]: 9/0 - o (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783690Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(10)), progress: 10, total: None, message: Some("r") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783725Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [10]: 10/0 - r (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783777Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(11)), progress: 11, total: None, message: Some("l") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783811Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [11]: 11/0 - l (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783858Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(12)), progress: 12, total: None, message: Some("d") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783893Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [12]: 12/0 - d (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783941Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(13)), progress: 13, total: None, message: Some("!") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783973Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [13]: 13/0 - ! (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.784108Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Processing completed: Processed 13 records successfully
�[2m2025-06-25T14:36:55.784174Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m task cancelled
�[2m2025-06-25T14:36:55.784195Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m serve finished �[3mquit_reason�[0m�[2m=�[0mCancelled
�[2m2025-06-25T14:36:55.784352Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Total progress notifications received: 13
�[2m2025-06-25T14:36:55.784370Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Total time elapsed: 0.01s
�[2m2025-06-25T14:36:55.784383Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m SSE transport test completed successfully!

However when I use the MCP inspector as another client to test with by running
cargo run --example servers_progress_demo -- sse

and connect to it via
npx @modelcontextprotocol/inspector

I see this when I run the stream processor tool I only see one progress notification despite it processing 13 records. This is similar to what @schwifty-brows reproduces with his test client:
Screenshot 2025-06-25 at 10 36 08 AM
@jokemanfire Any ideas?
@jokemanfire
jokemanfire
commented
Jun 26, 2025

Copy link


Copy Markdown

MemberAuthor
It does seem to be related to the client, I will take a look at the inspector and compare the implementation differences.
@jokemanfire
jokemanfire
commented
Jun 26, 2025•

edited

Loading

Copy link


Copy Markdown

MemberAuthor
I used Wireshark to capture packets, and I can confirm that the notify packet for Rust SDK was sent. I may need to take a look at the inspector code now.
image
All the [PSH,ACK] is the data.
@jokemanfire
jokemanfire
commented
Jun 26, 2025•

edited

Loading

Copy link


Copy Markdown

MemberAuthor
I have add log in inspector , I can make sure the mcpProxy recived the progress data, the problem should in inspector's front end.
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":1,"progress":1,"total":13,"message":"H"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":1,"progress":1,"total":13,"message":"H"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":2,"progress":2,"total":13,"message":"e"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":2,"progress":2,"total":13,"message":"e"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":3,"progress":3,"total":13,"message":"l"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":3,"progress":3,"total":13,"message":"l"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":4,"progress":4,"total":13,"message":"l"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":4,"progress":4,"total":13,"message":"l"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":5,"progress":5,"total":13,"message":"o"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":5,"progress":5,"total":13,"message":"o"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":6,"progress":6,"total":13,"message":","}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":6,"progress":6,"total":13,"message":","}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":7,"progress":7,"total":13,"message":" "}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":7,"progress":7,"total":13,"message":" "}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":8,"progress":8,"total":13,"message":"w"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":8,"progress":8,"total":13,"message":"w"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":9,"progress":9,"total":13,"message":"o"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":9,"progress":9,"total":13,"message":"o"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":10,"progress":10,"total":13,"message":"r"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":10,"progress":10,"total":13,"message":"r"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":11,"progress":11,"total":13,"message":"l"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":11,"progress":11,"total":13,"message":"l"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":12,"progress":12,"total":13,"message":"d"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":12,"progress":12,"total":13,"message":"d"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":13,"progress":13,"total":13,"message":"!"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":13,"progress":13,"total":13,"message":"!"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","id":4,"result":{"content":[{"type":"text","text":"Processed 13 records successfully"}],"isError":false}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","id":4,"result":{"content":[{"type":"text","text":"Processed 13 records successfully"}],"isError":false}}

@jokemanfire
jokemanfire
commented
Jun 26, 2025

Copy link


Copy Markdown

MemberAuthor
Hello @olaservo If you have time, can you help me take a look?
@alexhancock
alexhancock
commented
Jun 27, 2025

Copy link


Copy Markdown

Contributor
So just to be clear, this is looking to everyone now like a client only issue?
@schwifty-brows Did you repro this only with inspector, or with a client in your actual codebase as well?
@jokemanfire
jokemanfire
commented
Jul 1, 2025

Copy link


Copy Markdown

MemberAuthor
Sorry for the update, the issue may be due to differences in the implementation of typescript-sdk.
@alexhancock
alexhancock
commented
Jul 3, 2025

Copy link


Copy Markdown

Contributor
@schwifty-brows Did this ever work for you with a different client?
@alexhancock
alexhancock
commented
Sep 10, 2025

Copy link


Copy Markdown

Contributor
@jokemanfire Do we want to rebase this one, and merge the example?
And then on the issues with progress notifications generally, @schwifty-brows last I looked it seemed to be an issue only with non rust-sdk clients. Have you verified if there is a client you can use that works with the server implementation of rust-sdk for sending progress notifications?
@jokemanfire
jokemanfire
commented
Sep 11, 2025

Copy link


Copy Markdown

MemberAuthor
@jokemanfire Do we want to rebase this one, and merge the example?
And then on the issues with progress notifications generally, @schwifty-brows last I looked it seemed to be an issue only with non rust-sdk clients. Have you verified if there is a client you can use that works with the server implementation of rust-sdk for sending progress notifications?
I will rebase it , providing richer examples can reduce the burden of development.

Regarding the differences in the implementation progress of the typescript SDK, I may not have time to take a look as I am not familiar with this language.
@github-actionsgithub-actionsBot
removed
the 
T-test
Testing related changes
label
Sep 12, 2025
@jokemanfire
chore(example): add example in progress
0e5abb0
Signed-off-by: jokemanfire <hu.dingyang@zte.com.cn>
@jokemanfire
jokemanfire
commented
Sep 12, 2025

Copy link


Copy Markdown

MemberAuthor
@alexhancock I will put most of the examples into system testing later when I have time.
@jokemanfire
jokemanfire
merged commit f8a747e
into
modelcontextprotocol:mainSep 13, 2025

11 checks passed

takumi-earth pushed a commit
to earthlings-dev/rmcp
that referenced
this pull request
Jan 27, 2026
@jokemanfire
chore(example): add example in progress (modelcontextprotocol#271)
6492d12
Signed-off-by: jokemanfire <hu.dingyang@zte.com.cn>
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@alexhancockalexhancockalexhancock approved these changes

Assignees


No one assigned


Labels

T-configConfiguration file changesT-dependenciesDependencies related changesT-documentationDocumentation improvementsT-examplesExample code changes

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

3 participants

@jokemanfire@schwifty-brows@alexhancock

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms");
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
example: add example in progress - #271
Merged
jokemanfire merged 1 commit into
modelcontextprotocol:mainfrom 
jokemanfire:progress
Sep 13, 2025
Merged
example: add example in progress#271
jokemanfire merged 1 commit into
modelcontextprotocol:mainfrom 
jokemanfire:progress
Conversation
@jokemanfire
@jokemanfirejokemanfire
commented
Jun 18, 2025

Copy link


Copy Markdown

Member
Motivation and Context
add a example to introduce progress
How Has This Been Tested?
Breaking Changes
Types of changes
  •  Bug fix (non-breaking change which fixes an issue)
  •  New feature (non-breaking change which adds functionality)
  •  Breaking change (fix or feature that would cause existing functionality to change)
  •  Documentation update
Checklist
  •  I have read the MCP Documentation
  •  My code follows the repository's style guidelines
  •  New and existing tests pass locally
  •  I have added appropriate error handling
  •  I have added or updated documentation as needed
Additional context
@github-actionsgithub-actionsBot
added

T-documentation
Documentation improvements
T-dependencies
Dependencies related changes
T-config
Configuration file changes
T-examples
Example code changes
labels
Jun 18, 2025
@jokemanfirejokemanfire
mentioned this pull request
Jun 18, 2025

Closed

@schwifty-brows
schwifty-brows
commented
Jun 18, 2025

Copy link


Copy Markdown

i see the "simualte getting from a stream" but to really test, i would create a stream and process the resulting stream
@schwifty-brows
schwifty-brows
commented
Jun 18, 2025

Copy link


Copy Markdown

after that is added and you run the test, you should be able to see the return inconsistency
alexhancock
alexhancock
previously approved these changes
Jun 20, 2025
View reviewed changes
@alexhancockalexhancock
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

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

LGTM
@alexhancock
alexhancock
commented
Jun 20, 2025

Copy link


Copy Markdown

Contributor
I was able to verify/successfully run the example @schwifty-brows via python3 progress_test_client.py in examples/clients/scripts
Screenshot 2025-06-20 at 11 49 45 AM
Were you running into something different than me?
@schwifty-brows
schwifty-brows
commented
Jun 20, 2025
via email 

Copy link


Copy Markdown

@github-actionsgithub-actionsBot
added
the 
T-test
Testing related changes
label
Jun 21, 2025
@jokemanfire
jokemanfire
commented
Jun 21, 2025•

edited

Loading

Copy link


Copy Markdown

MemberAuthor
I think it is not rmcp's problem , I think it should be your business flow problem @schwifty-brows . And I have tested all the transport.
The current example file structure is not very good. In fact, this example is better placed in an integration test. I will modify this structure in another pr. @alexhancock
@schwifty-brows
schwifty-brows
commented
Jun 21, 2025

Copy link


Copy Markdown

how should we be sending SSE messages back? the progress notification is meant to do this, but running a simple example does not consistently work
@jokemanfire
jokemanfire
commented
Jun 24, 2025

Copy link


Copy Markdown

MemberAuthor
how should we be sending SSE messages back? the progress notification is meant to do this, but running a simple example does not consistently work
I really find it difficult to reproduce the abnormal scenario you mentioned. In the example, I should have provided a relatively simple example to send progress notifications from the server and obtain notification messages from the client. If it is a problem with the basic components of MCP SDK, then I believe that integration testing can definitely reproduce it (after excluding business interference). Could you please try to provide test cases that can be reproduced after excluding business impact.
@schwifty-brows
schwifty-brows
commented
Jun 24, 2025•

edited

Loading

Copy link


Copy Markdown

maybe i am missing something (i probably am) but in the code example, i dont see anything like this
i have a tool definition like so

#[tool(description = "do something")]
async fn search_warhouse(
&self,
#[tool(param)]
#[schemars(description = "query")]
query: String,
ctx: RequestContext<RoleServer>
) -> Result<CallToolResult, ErrorData>

and in my example 
//inject some strings into query_results
let mut query_results: Vec<String> = vec![];
let mut counter = 0;
for i in 0..query_results.len() {
let t = query_results[i].to_string();
let progress_param = ProgressNotificationParam {
progress_token: ProgressToken(NumberOrString::Number(counter)),
progress: counter,
total: Some(query_results.len() as u32),
message: Some("test".to_string()),
};
match ctx.peer.notify_progress(progress_param).await {
Ok(_) => {
counter += 1;
debug!("progress notification sent");
}
Err(e) => {
return Err(rmcp::Error::internal_error(
format!("failed to notify progress: {}", e),
Some(e.to_string().parse().unwrap())
));
}
}
}

 ctx.peer.notify_progress is used to send the notification. This is the problem area in question i dont see this as part of the example and where i keep getting 1-n notifications. If this is not the recommended way, that might be the problem
@alexhancock
alexhancock
commented
Jun 24, 2025

Copy link


Copy Markdown

Contributor
This part of the example server here seems relevant, and very similar to the ctx.peer.notify_progress example you're looking for @schwifty-brows
Does that make sense? Or if not maybe it's just github communication tripping me up from understanding. I would be happy to jump on a quick video call if you want tomorrow to discuss/get clear and identify any required improvements at the SDK level.
@schwifty-brows
schwifty-brows
commented
Jun 24, 2025

Copy link


Copy Markdown

Hey @alexhancock i think that would be a great idea!
Let me know your availability and I can walk you through the real world use case here.
@alexhancock
alexhancock
commented
Jun 25, 2025•

edited

Loading

Copy link


Copy Markdown

Contributor
Hey @alexhancock i think that would be a great idea!
Let me know your availability and I can walk you through the real world use case here.
@schwifty-brows How about 10am US eastern tomorrow? Email me (address on my profile) and we can set a meet.
@jokemanfirejokemanfire
mentioned this pull request
Jun 25, 2025
 Merged

9 tasks
@alexhancock
alexhancock
commented
Jun 25, 2025

Copy link


Copy Markdown

Contributor
@schwifty-brows@jokemanfire I think it may be a client difference...
When I run cargo run --example clients_progress_test_client -- --transport sse it works
�[2m2025-06-25T14:36:54.750050Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m RMCP Progress Notification Test Client
�[2m2025-06-25T14:36:54.750186Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m ==========================================
�[2m2025-06-25T14:36:54.750220Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Testing SSE Transport
�[2m2025-06-25T14:36:54.750229Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m =========================
�[2m2025-06-25T14:36:54.750237Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m SSE URL: http://127.0.0.1:8000/sse
�[2m2025-06-25T14:36:55.779656Z�[0m �[32m INFO�[0m �[1mserve_inner�[0m�[2m:�[0m �[2mrmcp::service�[0m�[2m:�[0m Service initialized as client �[3mpeer_info�[0m�[2m=�[0mSome(InitializeResult { protocol_version: ProtocolVersion("2024-11-05"), capabilities: ServerCapabilities { experimental: None, logging: None, completions: None, prompts: None, resources: None, tools: Some(ToolsCapability { list_changed: None }) }, server_info: Implementation { name: "rmcp", version: "0.1.5" }, instructions: Some("This server demonstrates progress notifications during long-running operations. Use the tools to see real-time progress updates for batch processing") })
�[2m2025-06-25T14:36:55.779944Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Connected to server: "rmcp"
�[2m2025-06-25T14:36:55.781660Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Available tools: ["stream_processor"]
�[2m2025-06-25T14:36:55.781674Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Starting to process 10 records...
�[2m2025-06-25T14:36:55.782563Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(1)), progress: 1, total: None, message: Some("H") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.782662Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [1]: 1/0 - H (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.782745Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(2)), progress: 2, total: None, message: Some("e") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.782804Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [2]: 2/0 - e (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.782893Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(3)), progress: 3, total: None, message: Some("l") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.782944Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [3]: 3/0 - l (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783056Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(4)), progress: 4, total: None, message: Some("l") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783124Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [4]: 4/0 - l (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783177Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(5)), progress: 5, total: None, message: Some("o") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783216Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [5]: 5/0 - o (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783289Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(6)), progress: 6, total: None, message: Some(",") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783339Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [6]: 6/0 - , (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783409Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(7)), progress: 7, total: None, message: Some(" ") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783450Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [7]: 7/0 - (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783509Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(8)), progress: 8, total: None, message: Some("w") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783549Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [8]: 8/0 - w (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783598Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(9)), progress: 9, total: None, message: Some("o") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783636Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [9]: 9/0 - o (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783690Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(10)), progress: 10, total: None, message: Some("r") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783725Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [10]: 10/0 - r (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783777Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(11)), progress: 11, total: None, message: Some("l") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783811Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [11]: 11/0 - l (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783858Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(12)), progress: 12, total: None, message: Some("d") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783893Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [12]: 12/0 - d (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783941Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(13)), progress: 13, total: None, message: Some("!") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783973Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [13]: 13/0 - ! (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.784108Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Processing completed: Processed 13 records successfully
�[2m2025-06-25T14:36:55.784174Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m task cancelled
�[2m2025-06-25T14:36:55.784195Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m serve finished �[3mquit_reason�[0m�[2m=�[0mCancelled
�[2m2025-06-25T14:36:55.784352Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Total progress notifications received: 13
�[2m2025-06-25T14:36:55.784370Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Total time elapsed: 0.01s
�[2m2025-06-25T14:36:55.784383Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m SSE transport test completed successfully!

However when I use the MCP inspector as another client to test with by running
cargo run --example servers_progress_demo -- sse

and connect to it via
npx @modelcontextprotocol/inspector

I see this when I run the stream processor tool I only see one progress notification despite it processing 13 records. This is similar to what @schwifty-brows reproduces with his test client:
Screenshot 2025-06-25 at 10 36 08 AM
@jokemanfire Any ideas?
@jokemanfire
jokemanfire
commented
Jun 26, 2025

Copy link


Copy Markdown

MemberAuthor
It does seem to be related to the client, I will take a look at the inspector and compare the implementation differences.
@jokemanfire
jokemanfire
commented
Jun 26, 2025•

edited

Loading

Copy link


Copy Markdown

MemberAuthor
I used Wireshark to capture packets, and I can confirm that the notify packet for Rust SDK was sent. I may need to take a look at the inspector code now.
image
All the [PSH,ACK] is the data.
@jokemanfire
jokemanfire
commented
Jun 26, 2025•

edited

Loading

Copy link


Copy Markdown

MemberAuthor
I have add log in inspector , I can make sure the mcpProxy recived the progress data, the problem should in inspector's front end.
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":1,"progress":1,"total":13,"message":"H"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":1,"progress":1,"total":13,"message":"H"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":2,"progress":2,"total":13,"message":"e"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":2,"progress":2,"total":13,"message":"e"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":3,"progress":3,"total":13,"message":"l"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":3,"progress":3,"total":13,"message":"l"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":4,"progress":4,"total":13,"message":"l"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":4,"progress":4,"total":13,"message":"l"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":5,"progress":5,"total":13,"message":"o"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":5,"progress":5,"total":13,"message":"o"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":6,"progress":6,"total":13,"message":","}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":6,"progress":6,"total":13,"message":","}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":7,"progress":7,"total":13,"message":" "}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":7,"progress":7,"total":13,"message":" "}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":8,"progress":8,"total":13,"message":"w"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":8,"progress":8,"total":13,"message":"w"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":9,"progress":9,"total":13,"message":"o"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":9,"progress":9,"total":13,"message":"o"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":10,"progress":10,"total":13,"message":"r"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":10,"progress":10,"total":13,"message":"r"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":11,"progress":11,"total":13,"message":"l"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":11,"progress":11,"total":13,"message":"l"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":12,"progress":12,"total":13,"message":"d"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":12,"progress":12,"total":13,"message":"d"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":13,"progress":13,"total":13,"message":"!"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":13,"progress":13,"total":13,"message":"!"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","id":4,"result":{"content":[{"type":"text","text":"Processed 13 records successfully"}],"isError":false}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","id":4,"result":{"content":[{"type":"text","text":"Processed 13 records successfully"}],"isError":false}}

@jokemanfire
jokemanfire
commented
Jun 26, 2025

Copy link


Copy Markdown

MemberAuthor
Hello @olaservo If you have time, can you help me take a look?
@alexhancock
alexhancock
commented
Jun 27, 2025

Copy link


Copy Markdown

Contributor
So just to be clear, this is looking to everyone now like a client only issue?
@schwifty-brows Did you repro this only with inspector, or with a client in your actual codebase as well?
@jokemanfire
jokemanfire
commented
Jul 1, 2025

Copy link


Copy Markdown

MemberAuthor
Sorry for the update, the issue may be due to differences in the implementation of typescript-sdk.
@alexhancock
alexhancock
commented
Jul 3, 2025

Copy link


Copy Markdown

Contributor
@schwifty-brows Did this ever work for you with a different client?
@alexhancock
alexhancock
commented
Sep 10, 2025

Copy link


Copy Markdown

Contributor
@jokemanfire Do we want to rebase this one, and merge the example?
And then on the issues with progress notifications generally, @schwifty-brows last I looked it seemed to be an issue only with non rust-sdk clients. Have you verified if there is a client you can use that works with the server implementation of rust-sdk for sending progress notifications?
@jokemanfire
jokemanfire
commented
Sep 11, 2025

Copy link


Copy Markdown

MemberAuthor
@jokemanfire Do we want to rebase this one, and merge the example?
And then on the issues with progress notifications generally, @schwifty-brows last I looked it seemed to be an issue only with non rust-sdk clients. Have you verified if there is a client you can use that works with the server implementation of rust-sdk for sending progress notifications?
I will rebase it , providing richer examples can reduce the burden of development.

Regarding the differences in the implementation progress of the typescript SDK, I may not have time to take a look as I am not familiar with this language.
@github-actionsgithub-actionsBot
removed
the 
T-test
Testing related changes
label
Sep 12, 2025
@jokemanfire
chore(example): add example in progress
0e5abb0
Signed-off-by: jokemanfire <hu.dingyang@zte.com.cn>
@jokemanfire
jokemanfire
commented
Sep 12, 2025

Copy link


Copy Markdown

MemberAuthor
@alexhancock I will put most of the examples into system testing later when I have time.
@jokemanfire
jokemanfire
merged commit f8a747e
into
modelcontextprotocol:mainSep 13, 2025

11 checks passed

takumi-earth pushed a commit
to earthlings-dev/rmcp
that referenced
this pull request
Jan 27, 2026
@jokemanfire
chore(example): add example in progress (modelcontextprotocol#271)
6492d12
Signed-off-by: jokemanfire <hu.dingyang@zte.com.cn>
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@alexhancockalexhancockalexhancock approved these changes

Assignees


No one assigned


Labels

T-configConfiguration file changesT-dependenciesDependencies related changesT-documentationDocumentation improvementsT-examplesExample code changes

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

3 participants

@jokemanfire@schwifty-brows@alexhancock

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links");
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '

Skip to content
example: add example in progress - #271
Merged
jokemanfire merged 1 commit into
modelcontextprotocol:mainfrom 
jokemanfire:progress
Sep 13, 2025
Merged
example: add example in progress#271
jokemanfire merged 1 commit into
modelcontextprotocol:mainfrom 
jokemanfire:progress
Conversation
@jokemanfire
@jokemanfirejokemanfire
commented
Jun 18, 2025

Copy link


Copy Markdown

Member
Motivation and Context
add a example to introduce progress
How Has This Been Tested?
Breaking Changes
Types of changes
  •  Bug fix (non-breaking change which fixes an issue)
  •  New feature (non-breaking change which adds functionality)
  •  Breaking change (fix or feature that would cause existing functionality to change)
  •  Documentation update
Checklist
  •  I have read the MCP Documentation
  •  My code follows the repository's style guidelines
  •  New and existing tests pass locally
  •  I have added appropriate error handling
  •  I have added or updated documentation as needed
Additional context
@github-actionsgithub-actionsBot
added

T-documentation
Documentation improvements
T-dependencies
Dependencies related changes
T-config
Configuration file changes
T-examples
Example code changes
labels
Jun 18, 2025
@jokemanfirejokemanfire
mentioned this pull request
Jun 18, 2025

Closed

@schwifty-brows
schwifty-brows
commented
Jun 18, 2025

Copy link


Copy Markdown

i see the "simualte getting from a stream" but to really test, i would create a stream and process the resulting stream
@schwifty-brows
schwifty-brows
commented
Jun 18, 2025

Copy link


Copy Markdown

after that is added and you run the test, you should be able to see the return inconsistency
alexhancock
alexhancock
previously approved these changes
Jun 20, 2025
View reviewed changes
@alexhancockalexhancock
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

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

LGTM
@alexhancock
alexhancock
commented
Jun 20, 2025

Copy link


Copy Markdown

Contributor
I was able to verify/successfully run the example @schwifty-brows via python3 progress_test_client.py in examples/clients/scripts
Screenshot 2025-06-20 at 11 49 45 AM
Were you running into something different than me?
@schwifty-brows
schwifty-brows
commented
Jun 20, 2025
via email 

Copy link


Copy Markdown

@github-actionsgithub-actionsBot
added
the 
T-test
Testing related changes
label
Jun 21, 2025
@jokemanfire
jokemanfire
commented
Jun 21, 2025•

edited

Loading

Copy link


Copy Markdown

MemberAuthor
I think it is not rmcp's problem , I think it should be your business flow problem @schwifty-brows . And I have tested all the transport.
The current example file structure is not very good. In fact, this example is better placed in an integration test. I will modify this structure in another pr. @alexhancock
@schwifty-brows
schwifty-brows
commented
Jun 21, 2025

Copy link


Copy Markdown

how should we be sending SSE messages back? the progress notification is meant to do this, but running a simple example does not consistently work
@jokemanfire
jokemanfire
commented
Jun 24, 2025

Copy link


Copy Markdown

MemberAuthor
how should we be sending SSE messages back? the progress notification is meant to do this, but running a simple example does not consistently work
I really find it difficult to reproduce the abnormal scenario you mentioned. In the example, I should have provided a relatively simple example to send progress notifications from the server and obtain notification messages from the client. If it is a problem with the basic components of MCP SDK, then I believe that integration testing can definitely reproduce it (after excluding business interference). Could you please try to provide test cases that can be reproduced after excluding business impact.
@schwifty-brows
schwifty-brows
commented
Jun 24, 2025•

edited

Loading

Copy link


Copy Markdown

maybe i am missing something (i probably am) but in the code example, i dont see anything like this
i have a tool definition like so

#[tool(description = "do something")]
async fn search_warhouse(
&self,
#[tool(param)]
#[schemars(description = "query")]
query: String,
ctx: RequestContext<RoleServer>
) -> Result<CallToolResult, ErrorData>

and in my example 
//inject some strings into query_results
let mut query_results: Vec<String> = vec![];
let mut counter = 0;
for i in 0..query_results.len() {
let t = query_results[i].to_string();
let progress_param = ProgressNotificationParam {
progress_token: ProgressToken(NumberOrString::Number(counter)),
progress: counter,
total: Some(query_results.len() as u32),
message: Some("test".to_string()),
};
match ctx.peer.notify_progress(progress_param).await {
Ok(_) => {
counter += 1;
debug!("progress notification sent");
}
Err(e) => {
return Err(rmcp::Error::internal_error(
format!("failed to notify progress: {}", e),
Some(e.to_string().parse().unwrap())
));
}
}
}

 ctx.peer.notify_progress is used to send the notification. This is the problem area in question i dont see this as part of the example and where i keep getting 1-n notifications. If this is not the recommended way, that might be the problem
@alexhancock
alexhancock
commented
Jun 24, 2025

Copy link


Copy Markdown

Contributor
This part of the example server here seems relevant, and very similar to the ctx.peer.notify_progress example you're looking for @schwifty-brows
Does that make sense? Or if not maybe it's just github communication tripping me up from understanding. I would be happy to jump on a quick video call if you want tomorrow to discuss/get clear and identify any required improvements at the SDK level.
@schwifty-brows
schwifty-brows
commented
Jun 24, 2025

Copy link


Copy Markdown

Hey @alexhancock i think that would be a great idea!
Let me know your availability and I can walk you through the real world use case here.
@alexhancock
alexhancock
commented
Jun 25, 2025•

edited

Loading

Copy link


Copy Markdown

Contributor
Hey @alexhancock i think that would be a great idea!
Let me know your availability and I can walk you through the real world use case here.
@schwifty-brows How about 10am US eastern tomorrow? Email me (address on my profile) and we can set a meet.
@jokemanfirejokemanfire
mentioned this pull request
Jun 25, 2025
 Merged

9 tasks
@alexhancock
alexhancock
commented
Jun 25, 2025

Copy link


Copy Markdown

Contributor
@schwifty-brows@jokemanfire I think it may be a client difference...
When I run cargo run --example clients_progress_test_client -- --transport sse it works
�[2m2025-06-25T14:36:54.750050Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m RMCP Progress Notification Test Client
�[2m2025-06-25T14:36:54.750186Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m ==========================================
�[2m2025-06-25T14:36:54.750220Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Testing SSE Transport
�[2m2025-06-25T14:36:54.750229Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m =========================
�[2m2025-06-25T14:36:54.750237Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m SSE URL: http://127.0.0.1:8000/sse
�[2m2025-06-25T14:36:55.779656Z�[0m �[32m INFO�[0m �[1mserve_inner�[0m�[2m:�[0m �[2mrmcp::service�[0m�[2m:�[0m Service initialized as client �[3mpeer_info�[0m�[2m=�[0mSome(InitializeResult { protocol_version: ProtocolVersion("2024-11-05"), capabilities: ServerCapabilities { experimental: None, logging: None, completions: None, prompts: None, resources: None, tools: Some(ToolsCapability { list_changed: None }) }, server_info: Implementation { name: "rmcp", version: "0.1.5" }, instructions: Some("This server demonstrates progress notifications during long-running operations. Use the tools to see real-time progress updates for batch processing") })
�[2m2025-06-25T14:36:55.779944Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Connected to server: "rmcp"
�[2m2025-06-25T14:36:55.781660Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Available tools: ["stream_processor"]
�[2m2025-06-25T14:36:55.781674Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Starting to process 10 records...
�[2m2025-06-25T14:36:55.782563Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(1)), progress: 1, total: None, message: Some("H") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.782662Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [1]: 1/0 - H (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.782745Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(2)), progress: 2, total: None, message: Some("e") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.782804Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [2]: 2/0 - e (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.782893Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(3)), progress: 3, total: None, message: Some("l") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.782944Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [3]: 3/0 - l (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783056Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(4)), progress: 4, total: None, message: Some("l") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783124Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [4]: 4/0 - l (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783177Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(5)), progress: 5, total: None, message: Some("o") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783216Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [5]: 5/0 - o (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783289Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(6)), progress: 6, total: None, message: Some(",") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783339Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [6]: 6/0 - , (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783409Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(7)), progress: 7, total: None, message: Some(" ") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783450Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [7]: 7/0 - (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783509Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(8)), progress: 8, total: None, message: Some("w") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783549Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [8]: 8/0 - w (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783598Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(9)), progress: 9, total: None, message: Some("o") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783636Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [9]: 9/0 - o (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783690Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(10)), progress: 10, total: None, message: Some("r") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783725Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [10]: 10/0 - r (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783777Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(11)), progress: 11, total: None, message: Some("l") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783811Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [11]: 11/0 - l (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783858Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(12)), progress: 12, total: None, message: Some("d") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783893Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [12]: 12/0 - d (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783941Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(13)), progress: 13, total: None, message: Some("!") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783973Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [13]: 13/0 - ! (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.784108Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Processing completed: Processed 13 records successfully
�[2m2025-06-25T14:36:55.784174Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m task cancelled
�[2m2025-06-25T14:36:55.784195Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m serve finished �[3mquit_reason�[0m�[2m=�[0mCancelled
�[2m2025-06-25T14:36:55.784352Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Total progress notifications received: 13
�[2m2025-06-25T14:36:55.784370Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Total time elapsed: 0.01s
�[2m2025-06-25T14:36:55.784383Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m SSE transport test completed successfully!

However when I use the MCP inspector as another client to test with by running
cargo run --example servers_progress_demo -- sse

and connect to it via
npx @modelcontextprotocol/inspector

I see this when I run the stream processor tool I only see one progress notification despite it processing 13 records. This is similar to what @schwifty-brows reproduces with his test client:
Screenshot 2025-06-25 at 10 36 08 AM
@jokemanfire Any ideas?
@jokemanfire
jokemanfire
commented
Jun 26, 2025

Copy link


Copy Markdown

MemberAuthor
It does seem to be related to the client, I will take a look at the inspector and compare the implementation differences.
@jokemanfire
jokemanfire
commented
Jun 26, 2025•

edited

Loading

Copy link


Copy Markdown

MemberAuthor
I used Wireshark to capture packets, and I can confirm that the notify packet for Rust SDK was sent. I may need to take a look at the inspector code now.
image
All the [PSH,ACK] is the data.
@jokemanfire
jokemanfire
commented
Jun 26, 2025•

edited

Loading

Copy link


Copy Markdown

MemberAuthor
I have add log in inspector , I can make sure the mcpProxy recived the progress data, the problem should in inspector's front end.
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":1,"progress":1,"total":13,"message":"H"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":1,"progress":1,"total":13,"message":"H"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":2,"progress":2,"total":13,"message":"e"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":2,"progress":2,"total":13,"message":"e"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":3,"progress":3,"total":13,"message":"l"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":3,"progress":3,"total":13,"message":"l"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":4,"progress":4,"total":13,"message":"l"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":4,"progress":4,"total":13,"message":"l"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":5,"progress":5,"total":13,"message":"o"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":5,"progress":5,"total":13,"message":"o"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":6,"progress":6,"total":13,"message":","}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":6,"progress":6,"total":13,"message":","}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":7,"progress":7,"total":13,"message":" "}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":7,"progress":7,"total":13,"message":" "}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":8,"progress":8,"total":13,"message":"w"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":8,"progress":8,"total":13,"message":"w"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":9,"progress":9,"total":13,"message":"o"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":9,"progress":9,"total":13,"message":"o"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":10,"progress":10,"total":13,"message":"r"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":10,"progress":10,"total":13,"message":"r"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":11,"progress":11,"total":13,"message":"l"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":11,"progress":11,"total":13,"message":"l"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":12,"progress":12,"total":13,"message":"d"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":12,"progress":12,"total":13,"message":"d"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":13,"progress":13,"total":13,"message":"!"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":13,"progress":13,"total":13,"message":"!"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","id":4,"result":{"content":[{"type":"text","text":"Processed 13 records successfully"}],"isError":false}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","id":4,"result":{"content":[{"type":"text","text":"Processed 13 records successfully"}],"isError":false}}

@jokemanfire
jokemanfire
commented
Jun 26, 2025

Copy link


Copy Markdown

MemberAuthor
Hello @olaservo If you have time, can you help me take a look?
@alexhancock
alexhancock
commented
Jun 27, 2025

Copy link


Copy Markdown

Contributor
So just to be clear, this is looking to everyone now like a client only issue?
@schwifty-brows Did you repro this only with inspector, or with a client in your actual codebase as well?
@jokemanfire
jokemanfire
commented
Jul 1, 2025

Copy link


Copy Markdown

MemberAuthor
Sorry for the update, the issue may be due to differences in the implementation of typescript-sdk.
@alexhancock
alexhancock
commented
Jul 3, 2025

Copy link


Copy Markdown

Contributor
@schwifty-brows Did this ever work for you with a different client?
@alexhancock
alexhancock
commented
Sep 10, 2025

Copy link


Copy Markdown

Contributor
@jokemanfire Do we want to rebase this one, and merge the example?
And then on the issues with progress notifications generally, @schwifty-brows last I looked it seemed to be an issue only with non rust-sdk clients. Have you verified if there is a client you can use that works with the server implementation of rust-sdk for sending progress notifications?
@jokemanfire
jokemanfire
commented
Sep 11, 2025

Copy link


Copy Markdown

MemberAuthor
@jokemanfire Do we want to rebase this one, and merge the example?
And then on the issues with progress notifications generally, @schwifty-brows last I looked it seemed to be an issue only with non rust-sdk clients. Have you verified if there is a client you can use that works with the server implementation of rust-sdk for sending progress notifications?
I will rebase it , providing richer examples can reduce the burden of development.

Regarding the differences in the implementation progress of the typescript SDK, I may not have time to take a look as I am not familiar with this language.
@github-actionsgithub-actionsBot
removed
the 
T-test
Testing related changes
label
Sep 12, 2025
@jokemanfire
chore(example): add example in progress
0e5abb0
Signed-off-by: jokemanfire <hu.dingyang@zte.com.cn>
@jokemanfire
jokemanfire
commented
Sep 12, 2025

Copy link


Copy Markdown

MemberAuthor
@alexhancock I will put most of the examples into system testing later when I have time.
@jokemanfire
jokemanfire
merged commit f8a747e
into
modelcontextprotocol:mainSep 13, 2025

11 checks passed

takumi-earth pushed a commit
to earthlings-dev/rmcp
that referenced
this pull request
Jan 27, 2026
@jokemanfire
chore(example): add example in progress (modelcontextprotocol#271)
6492d12
Signed-off-by: jokemanfire <hu.dingyang@zte.com.cn>
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@alexhancockalexhancockalexhancock approved these changes

Assignees


No one assigned


Labels

T-configConfiguration file changesT-dependenciesDependencies related changesT-documentationDocumentation improvementsT-examplesExample code changes

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

3 participants

@jokemanfire@schwifty-brows@alexhancock

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default");
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
example: add example in progress - #271
Merged
jokemanfire merged 1 commit into
modelcontextprotocol:mainfrom 
jokemanfire:progress
Sep 13, 2025
Merged
example: add example in progress#271
jokemanfire merged 1 commit into
modelcontextprotocol:mainfrom 
jokemanfire:progress
Conversation
@jokemanfire
@jokemanfirejokemanfire
commented
Jun 18, 2025

Copy link


Copy Markdown

Member
Motivation and Context
add a example to introduce progress
How Has This Been Tested?
Breaking Changes
Types of changes
  •  Bug fix (non-breaking change which fixes an issue)
  •  New feature (non-breaking change which adds functionality)
  •  Breaking change (fix or feature that would cause existing functionality to change)
  •  Documentation update
Checklist
  •  I have read the MCP Documentation
  •  My code follows the repository's style guidelines
  •  New and existing tests pass locally
  •  I have added appropriate error handling
  •  I have added or updated documentation as needed
Additional context
@github-actionsgithub-actionsBot
added

T-documentation
Documentation improvements
T-dependencies
Dependencies related changes
T-config
Configuration file changes
T-examples
Example code changes
labels
Jun 18, 2025
@jokemanfirejokemanfire
mentioned this pull request
Jun 18, 2025

Closed

@schwifty-brows
schwifty-brows
commented
Jun 18, 2025

Copy link


Copy Markdown

i see the "simualte getting from a stream" but to really test, i would create a stream and process the resulting stream
@schwifty-brows
schwifty-brows
commented
Jun 18, 2025

Copy link


Copy Markdown

after that is added and you run the test, you should be able to see the return inconsistency
alexhancock
alexhancock
previously approved these changes
Jun 20, 2025
View reviewed changes
@alexhancockalexhancock
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

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

LGTM
@alexhancock
alexhancock
commented
Jun 20, 2025

Copy link


Copy Markdown

Contributor
I was able to verify/successfully run the example @schwifty-brows via python3 progress_test_client.py in examples/clients/scripts
Screenshot 2025-06-20 at 11 49 45 AM
Were you running into something different than me?
@schwifty-brows
schwifty-brows
commented
Jun 20, 2025
via email 

Copy link


Copy Markdown

@github-actionsgithub-actionsBot
added
the 
T-test
Testing related changes
label
Jun 21, 2025
@jokemanfire
jokemanfire
commented
Jun 21, 2025•

edited

Loading

Copy link


Copy Markdown

MemberAuthor
I think it is not rmcp's problem , I think it should be your business flow problem @schwifty-brows . And I have tested all the transport.
The current example file structure is not very good. In fact, this example is better placed in an integration test. I will modify this structure in another pr. @alexhancock
@schwifty-brows
schwifty-brows
commented
Jun 21, 2025

Copy link


Copy Markdown

how should we be sending SSE messages back? the progress notification is meant to do this, but running a simple example does not consistently work
@jokemanfire
jokemanfire
commented
Jun 24, 2025

Copy link


Copy Markdown

MemberAuthor
how should we be sending SSE messages back? the progress notification is meant to do this, but running a simple example does not consistently work
I really find it difficult to reproduce the abnormal scenario you mentioned. In the example, I should have provided a relatively simple example to send progress notifications from the server and obtain notification messages from the client. If it is a problem with the basic components of MCP SDK, then I believe that integration testing can definitely reproduce it (after excluding business interference). Could you please try to provide test cases that can be reproduced after excluding business impact.
@schwifty-brows
schwifty-brows
commented
Jun 24, 2025•

edited

Loading

Copy link


Copy Markdown

maybe i am missing something (i probably am) but in the code example, i dont see anything like this
i have a tool definition like so

#[tool(description = "do something")]
async fn search_warhouse(
&self,
#[tool(param)]
#[schemars(description = "query")]
query: String,
ctx: RequestContext<RoleServer>
) -> Result<CallToolResult, ErrorData>

and in my example 
//inject some strings into query_results
let mut query_results: Vec<String> = vec![];
let mut counter = 0;
for i in 0..query_results.len() {
let t = query_results[i].to_string();
let progress_param = ProgressNotificationParam {
progress_token: ProgressToken(NumberOrString::Number(counter)),
progress: counter,
total: Some(query_results.len() as u32),
message: Some("test".to_string()),
};
match ctx.peer.notify_progress(progress_param).await {
Ok(_) => {
counter += 1;
debug!("progress notification sent");
}
Err(e) => {
return Err(rmcp::Error::internal_error(
format!("failed to notify progress: {}", e),
Some(e.to_string().parse().unwrap())
));
}
}
}

 ctx.peer.notify_progress is used to send the notification. This is the problem area in question i dont see this as part of the example and where i keep getting 1-n notifications. If this is not the recommended way, that might be the problem
@alexhancock
alexhancock
commented
Jun 24, 2025

Copy link


Copy Markdown

Contributor
This part of the example server here seems relevant, and very similar to the ctx.peer.notify_progress example you're looking for @schwifty-brows
Does that make sense? Or if not maybe it's just github communication tripping me up from understanding. I would be happy to jump on a quick video call if you want tomorrow to discuss/get clear and identify any required improvements at the SDK level.
@schwifty-brows
schwifty-brows
commented
Jun 24, 2025

Copy link


Copy Markdown

Hey @alexhancock i think that would be a great idea!
Let me know your availability and I can walk you through the real world use case here.
@alexhancock
alexhancock
commented
Jun 25, 2025•

edited

Loading

Copy link


Copy Markdown

Contributor
Hey @alexhancock i think that would be a great idea!
Let me know your availability and I can walk you through the real world use case here.
@schwifty-brows How about 10am US eastern tomorrow? Email me (address on my profile) and we can set a meet.
@jokemanfirejokemanfire
mentioned this pull request
Jun 25, 2025
 Merged

9 tasks
@alexhancock
alexhancock
commented
Jun 25, 2025

Copy link


Copy Markdown

Contributor
@schwifty-brows@jokemanfire I think it may be a client difference...
When I run cargo run --example clients_progress_test_client -- --transport sse it works
�[2m2025-06-25T14:36:54.750050Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m RMCP Progress Notification Test Client
�[2m2025-06-25T14:36:54.750186Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m ==========================================
�[2m2025-06-25T14:36:54.750220Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Testing SSE Transport
�[2m2025-06-25T14:36:54.750229Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m =========================
�[2m2025-06-25T14:36:54.750237Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m SSE URL: http://127.0.0.1:8000/sse
�[2m2025-06-25T14:36:55.779656Z�[0m �[32m INFO�[0m �[1mserve_inner�[0m�[2m:�[0m �[2mrmcp::service�[0m�[2m:�[0m Service initialized as client �[3mpeer_info�[0m�[2m=�[0mSome(InitializeResult { protocol_version: ProtocolVersion("2024-11-05"), capabilities: ServerCapabilities { experimental: None, logging: None, completions: None, prompts: None, resources: None, tools: Some(ToolsCapability { list_changed: None }) }, server_info: Implementation { name: "rmcp", version: "0.1.5" }, instructions: Some("This server demonstrates progress notifications during long-running operations. Use the tools to see real-time progress updates for batch processing") })
�[2m2025-06-25T14:36:55.779944Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Connected to server: "rmcp"
�[2m2025-06-25T14:36:55.781660Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Available tools: ["stream_processor"]
�[2m2025-06-25T14:36:55.781674Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Starting to process 10 records...
�[2m2025-06-25T14:36:55.782563Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(1)), progress: 1, total: None, message: Some("H") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.782662Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [1]: 1/0 - H (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.782745Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(2)), progress: 2, total: None, message: Some("e") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.782804Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [2]: 2/0 - e (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.782893Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(3)), progress: 3, total: None, message: Some("l") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.782944Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [3]: 3/0 - l (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783056Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(4)), progress: 4, total: None, message: Some("l") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783124Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [4]: 4/0 - l (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783177Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(5)), progress: 5, total: None, message: Some("o") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783216Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [5]: 5/0 - o (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783289Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(6)), progress: 6, total: None, message: Some(",") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783339Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [6]: 6/0 - , (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783409Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(7)), progress: 7, total: None, message: Some(" ") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783450Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [7]: 7/0 - (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783509Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(8)), progress: 8, total: None, message: Some("w") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783549Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [8]: 8/0 - w (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783598Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(9)), progress: 9, total: None, message: Some("o") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783636Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [9]: 9/0 - o (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783690Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(10)), progress: 10, total: None, message: Some("r") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783725Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [10]: 10/0 - r (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783777Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(11)), progress: 11, total: None, message: Some("l") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783811Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [11]: 11/0 - l (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783858Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(12)), progress: 12, total: None, message: Some("d") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783893Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [12]: 12/0 - d (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783941Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(13)), progress: 13, total: None, message: Some("!") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783973Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [13]: 13/0 - ! (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.784108Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Processing completed: Processed 13 records successfully
�[2m2025-06-25T14:36:55.784174Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m task cancelled
�[2m2025-06-25T14:36:55.784195Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m serve finished �[3mquit_reason�[0m�[2m=�[0mCancelled
�[2m2025-06-25T14:36:55.784352Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Total progress notifications received: 13
�[2m2025-06-25T14:36:55.784370Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Total time elapsed: 0.01s
�[2m2025-06-25T14:36:55.784383Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m SSE transport test completed successfully!

However when I use the MCP inspector as another client to test with by running
cargo run --example servers_progress_demo -- sse

and connect to it via
npx @modelcontextprotocol/inspector

I see this when I run the stream processor tool I only see one progress notification despite it processing 13 records. This is similar to what @schwifty-brows reproduces with his test client:
Screenshot 2025-06-25 at 10 36 08 AM
@jokemanfire Any ideas?
@jokemanfire
jokemanfire
commented
Jun 26, 2025

Copy link


Copy Markdown

MemberAuthor
It does seem to be related to the client, I will take a look at the inspector and compare the implementation differences.
@jokemanfire
jokemanfire
commented
Jun 26, 2025•

edited

Loading

Copy link


Copy Markdown

MemberAuthor
I used Wireshark to capture packets, and I can confirm that the notify packet for Rust SDK was sent. I may need to take a look at the inspector code now.
image
All the [PSH,ACK] is the data.
@jokemanfire
jokemanfire
commented
Jun 26, 2025•

edited

Loading

Copy link


Copy Markdown

MemberAuthor
I have add log in inspector , I can make sure the mcpProxy recived the progress data, the problem should in inspector's front end.
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":1,"progress":1,"total":13,"message":"H"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":1,"progress":1,"total":13,"message":"H"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":2,"progress":2,"total":13,"message":"e"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":2,"progress":2,"total":13,"message":"e"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":3,"progress":3,"total":13,"message":"l"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":3,"progress":3,"total":13,"message":"l"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":4,"progress":4,"total":13,"message":"l"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":4,"progress":4,"total":13,"message":"l"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":5,"progress":5,"total":13,"message":"o"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":5,"progress":5,"total":13,"message":"o"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":6,"progress":6,"total":13,"message":","}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":6,"progress":6,"total":13,"message":","}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":7,"progress":7,"total":13,"message":" "}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":7,"progress":7,"total":13,"message":" "}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":8,"progress":8,"total":13,"message":"w"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":8,"progress":8,"total":13,"message":"w"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":9,"progress":9,"total":13,"message":"o"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":9,"progress":9,"total":13,"message":"o"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":10,"progress":10,"total":13,"message":"r"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":10,"progress":10,"total":13,"message":"r"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":11,"progress":11,"total":13,"message":"l"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":11,"progress":11,"total":13,"message":"l"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":12,"progress":12,"total":13,"message":"d"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":12,"progress":12,"total":13,"message":"d"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":13,"progress":13,"total":13,"message":"!"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":13,"progress":13,"total":13,"message":"!"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","id":4,"result":{"content":[{"type":"text","text":"Processed 13 records successfully"}],"isError":false}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","id":4,"result":{"content":[{"type":"text","text":"Processed 13 records successfully"}],"isError":false}}

@jokemanfire
jokemanfire
commented
Jun 26, 2025

Copy link


Copy Markdown

MemberAuthor
Hello @olaservo If you have time, can you help me take a look?
@alexhancock
alexhancock
commented
Jun 27, 2025

Copy link


Copy Markdown

Contributor
So just to be clear, this is looking to everyone now like a client only issue?
@schwifty-brows Did you repro this only with inspector, or with a client in your actual codebase as well?
@jokemanfire
jokemanfire
commented
Jul 1, 2025

Copy link


Copy Markdown

MemberAuthor
Sorry for the update, the issue may be due to differences in the implementation of typescript-sdk.
@alexhancock
alexhancock
commented
Jul 3, 2025

Copy link


Copy Markdown

Contributor
@schwifty-brows Did this ever work for you with a different client?
@alexhancock
alexhancock
commented
Sep 10, 2025

Copy link


Copy Markdown

Contributor
@jokemanfire Do we want to rebase this one, and merge the example?
And then on the issues with progress notifications generally, @schwifty-brows last I looked it seemed to be an issue only with non rust-sdk clients. Have you verified if there is a client you can use that works with the server implementation of rust-sdk for sending progress notifications?
@jokemanfire
jokemanfire
commented
Sep 11, 2025

Copy link


Copy Markdown

MemberAuthor
@jokemanfire Do we want to rebase this one, and merge the example?
And then on the issues with progress notifications generally, @schwifty-brows last I looked it seemed to be an issue only with non rust-sdk clients. Have you verified if there is a client you can use that works with the server implementation of rust-sdk for sending progress notifications?
I will rebase it , providing richer examples can reduce the burden of development.

Regarding the differences in the implementation progress of the typescript SDK, I may not have time to take a look as I am not familiar with this language.
@github-actionsgithub-actionsBot
removed
the 
T-test
Testing related changes
label
Sep 12, 2025
@jokemanfire
chore(example): add example in progress
0e5abb0
Signed-off-by: jokemanfire <hu.dingyang@zte.com.cn>
@jokemanfire
jokemanfire
commented
Sep 12, 2025

Copy link


Copy Markdown

MemberAuthor
@alexhancock I will put most of the examples into system testing later when I have time.
@jokemanfire
jokemanfire
merged commit f8a747e
into
modelcontextprotocol:mainSep 13, 2025

11 checks passed

takumi-earth pushed a commit
to earthlings-dev/rmcp
that referenced
this pull request
Jan 27, 2026
@jokemanfire
chore(example): add example in progress (modelcontextprotocol#271)
6492d12
Signed-off-by: jokemanfire <hu.dingyang@zte.com.cn>
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@alexhancockalexhancockalexhancock approved these changes

Assignees


No one assigned


Labels

T-configConfiguration file changesT-dependenciesDependencies related changesT-documentationDocumentation improvementsT-examplesExample code changes

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

3 participants

@jokemanfire@schwifty-brows@alexhancock

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers");
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
example: add example in progress - #271
Merged
jokemanfire merged 1 commit into
modelcontextprotocol:mainfrom 
jokemanfire:progress
Sep 13, 2025
Merged
example: add example in progress#271
jokemanfire merged 1 commit into
modelcontextprotocol:mainfrom 
jokemanfire:progress
Conversation
@jokemanfire
@jokemanfirejokemanfire
commented
Jun 18, 2025

Copy link


Copy Markdown

Member
Motivation and Context
add a example to introduce progress
How Has This Been Tested?
Breaking Changes
Types of changes
  •  Bug fix (non-breaking change which fixes an issue)
  •  New feature (non-breaking change which adds functionality)
  •  Breaking change (fix or feature that would cause existing functionality to change)
  •  Documentation update
Checklist
  •  I have read the MCP Documentation
  •  My code follows the repository's style guidelines
  •  New and existing tests pass locally
  •  I have added appropriate error handling
  •  I have added or updated documentation as needed
Additional context
@github-actionsgithub-actionsBot
added

T-documentation
Documentation improvements
T-dependencies
Dependencies related changes
T-config
Configuration file changes
T-examples
Example code changes
labels
Jun 18, 2025
@jokemanfirejokemanfire
mentioned this pull request
Jun 18, 2025

Closed

@schwifty-brows
schwifty-brows
commented
Jun 18, 2025

Copy link


Copy Markdown

i see the "simualte getting from a stream" but to really test, i would create a stream and process the resulting stream
@schwifty-brows
schwifty-brows
commented
Jun 18, 2025

Copy link


Copy Markdown

after that is added and you run the test, you should be able to see the return inconsistency
alexhancock
alexhancock
previously approved these changes
Jun 20, 2025
View reviewed changes
@alexhancockalexhancock
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

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

LGTM
@alexhancock
alexhancock
commented
Jun 20, 2025

Copy link


Copy Markdown

Contributor
I was able to verify/successfully run the example @schwifty-brows via python3 progress_test_client.py in examples/clients/scripts
Screenshot 2025-06-20 at 11 49 45 AM
Were you running into something different than me?
@schwifty-brows
schwifty-brows
commented
Jun 20, 2025
via email 

Copy link


Copy Markdown

@github-actionsgithub-actionsBot
added
the 
T-test
Testing related changes
label
Jun 21, 2025
@jokemanfire
jokemanfire
commented
Jun 21, 2025•

edited

Loading

Copy link


Copy Markdown

MemberAuthor
I think it is not rmcp's problem , I think it should be your business flow problem @schwifty-brows . And I have tested all the transport.
The current example file structure is not very good. In fact, this example is better placed in an integration test. I will modify this structure in another pr. @alexhancock
@schwifty-brows
schwifty-brows
commented
Jun 21, 2025

Copy link


Copy Markdown

how should we be sending SSE messages back? the progress notification is meant to do this, but running a simple example does not consistently work
@jokemanfire
jokemanfire
commented
Jun 24, 2025

Copy link


Copy Markdown

MemberAuthor
how should we be sending SSE messages back? the progress notification is meant to do this, but running a simple example does not consistently work
I really find it difficult to reproduce the abnormal scenario you mentioned. In the example, I should have provided a relatively simple example to send progress notifications from the server and obtain notification messages from the client. If it is a problem with the basic components of MCP SDK, then I believe that integration testing can definitely reproduce it (after excluding business interference). Could you please try to provide test cases that can be reproduced after excluding business impact.
@schwifty-brows
schwifty-brows
commented
Jun 24, 2025•

edited

Loading

Copy link


Copy Markdown

maybe i am missing something (i probably am) but in the code example, i dont see anything like this
i have a tool definition like so

#[tool(description = "do something")]
async fn search_warhouse(
&self,
#[tool(param)]
#[schemars(description = "query")]
query: String,
ctx: RequestContext<RoleServer>
) -> Result<CallToolResult, ErrorData>

and in my example 
//inject some strings into query_results
let mut query_results: Vec<String> = vec![];
let mut counter = 0;
for i in 0..query_results.len() {
let t = query_results[i].to_string();
let progress_param = ProgressNotificationParam {
progress_token: ProgressToken(NumberOrString::Number(counter)),
progress: counter,
total: Some(query_results.len() as u32),
message: Some("test".to_string()),
};
match ctx.peer.notify_progress(progress_param).await {
Ok(_) => {
counter += 1;
debug!("progress notification sent");
}
Err(e) => {
return Err(rmcp::Error::internal_error(
format!("failed to notify progress: {}", e),
Some(e.to_string().parse().unwrap())
));
}
}
}

 ctx.peer.notify_progress is used to send the notification. This is the problem area in question i dont see this as part of the example and where i keep getting 1-n notifications. If this is not the recommended way, that might be the problem
@alexhancock
alexhancock
commented
Jun 24, 2025

Copy link


Copy Markdown

Contributor
This part of the example server here seems relevant, and very similar to the ctx.peer.notify_progress example you're looking for @schwifty-brows
Does that make sense? Or if not maybe it's just github communication tripping me up from understanding. I would be happy to jump on a quick video call if you want tomorrow to discuss/get clear and identify any required improvements at the SDK level.
@schwifty-brows
schwifty-brows
commented
Jun 24, 2025

Copy link


Copy Markdown

Hey @alexhancock i think that would be a great idea!
Let me know your availability and I can walk you through the real world use case here.
@alexhancock
alexhancock
commented
Jun 25, 2025•

edited

Loading

Copy link


Copy Markdown

Contributor
Hey @alexhancock i think that would be a great idea!
Let me know your availability and I can walk you through the real world use case here.
@schwifty-brows How about 10am US eastern tomorrow? Email me (address on my profile) and we can set a meet.
@jokemanfirejokemanfire
mentioned this pull request
Jun 25, 2025
 Merged

9 tasks
@alexhancock
alexhancock
commented
Jun 25, 2025

Copy link


Copy Markdown

Contributor
@schwifty-brows@jokemanfire I think it may be a client difference...
When I run cargo run --example clients_progress_test_client -- --transport sse it works
�[2m2025-06-25T14:36:54.750050Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m RMCP Progress Notification Test Client
�[2m2025-06-25T14:36:54.750186Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m ==========================================
�[2m2025-06-25T14:36:54.750220Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Testing SSE Transport
�[2m2025-06-25T14:36:54.750229Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m =========================
�[2m2025-06-25T14:36:54.750237Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m SSE URL: http://127.0.0.1:8000/sse
�[2m2025-06-25T14:36:55.779656Z�[0m �[32m INFO�[0m �[1mserve_inner�[0m�[2m:�[0m �[2mrmcp::service�[0m�[2m:�[0m Service initialized as client �[3mpeer_info�[0m�[2m=�[0mSome(InitializeResult { protocol_version: ProtocolVersion("2024-11-05"), capabilities: ServerCapabilities { experimental: None, logging: None, completions: None, prompts: None, resources: None, tools: Some(ToolsCapability { list_changed: None }) }, server_info: Implementation { name: "rmcp", version: "0.1.5" }, instructions: Some("This server demonstrates progress notifications during long-running operations. Use the tools to see real-time progress updates for batch processing") })
�[2m2025-06-25T14:36:55.779944Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Connected to server: "rmcp"
�[2m2025-06-25T14:36:55.781660Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Available tools: ["stream_processor"]
�[2m2025-06-25T14:36:55.781674Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Starting to process 10 records...
�[2m2025-06-25T14:36:55.782563Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(1)), progress: 1, total: None, message: Some("H") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.782662Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [1]: 1/0 - H (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.782745Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(2)), progress: 2, total: None, message: Some("e") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.782804Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [2]: 2/0 - e (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.782893Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(3)), progress: 3, total: None, message: Some("l") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.782944Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [3]: 3/0 - l (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783056Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(4)), progress: 4, total: None, message: Some("l") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783124Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [4]: 4/0 - l (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783177Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(5)), progress: 5, total: None, message: Some("o") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783216Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [5]: 5/0 - o (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783289Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(6)), progress: 6, total: None, message: Some(",") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783339Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [6]: 6/0 - , (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783409Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(7)), progress: 7, total: None, message: Some(" ") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783450Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [7]: 7/0 - (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783509Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(8)), progress: 8, total: None, message: Some("w") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783549Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [8]: 8/0 - w (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783598Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(9)), progress: 9, total: None, message: Some("o") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783636Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [9]: 9/0 - o (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783690Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(10)), progress: 10, total: None, message: Some("r") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783725Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [10]: 10/0 - r (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783777Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(11)), progress: 11, total: None, message: Some("l") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783811Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [11]: 11/0 - l (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783858Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(12)), progress: 12, total: None, message: Some("d") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783893Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [12]: 12/0 - d (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783941Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(13)), progress: 13, total: None, message: Some("!") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783973Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [13]: 13/0 - ! (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.784108Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Processing completed: Processed 13 records successfully
�[2m2025-06-25T14:36:55.784174Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m task cancelled
�[2m2025-06-25T14:36:55.784195Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m serve finished �[3mquit_reason�[0m�[2m=�[0mCancelled
�[2m2025-06-25T14:36:55.784352Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Total progress notifications received: 13
�[2m2025-06-25T14:36:55.784370Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Total time elapsed: 0.01s
�[2m2025-06-25T14:36:55.784383Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m SSE transport test completed successfully!

However when I use the MCP inspector as another client to test with by running
cargo run --example servers_progress_demo -- sse

and connect to it via
npx @modelcontextprotocol/inspector

I see this when I run the stream processor tool I only see one progress notification despite it processing 13 records. This is similar to what @schwifty-brows reproduces with his test client:
Screenshot 2025-06-25 at 10 36 08 AM
@jokemanfire Any ideas?
@jokemanfire
jokemanfire
commented
Jun 26, 2025

Copy link


Copy Markdown

MemberAuthor
It does seem to be related to the client, I will take a look at the inspector and compare the implementation differences.
@jokemanfire
jokemanfire
commented
Jun 26, 2025•

edited

Loading

Copy link


Copy Markdown

MemberAuthor
I used Wireshark to capture packets, and I can confirm that the notify packet for Rust SDK was sent. I may need to take a look at the inspector code now.
image
All the [PSH,ACK] is the data.
@jokemanfire
jokemanfire
commented
Jun 26, 2025•

edited

Loading

Copy link


Copy Markdown

MemberAuthor
I have add log in inspector , I can make sure the mcpProxy recived the progress data, the problem should in inspector's front end.
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":1,"progress":1,"total":13,"message":"H"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":1,"progress":1,"total":13,"message":"H"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":2,"progress":2,"total":13,"message":"e"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":2,"progress":2,"total":13,"message":"e"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":3,"progress":3,"total":13,"message":"l"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":3,"progress":3,"total":13,"message":"l"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":4,"progress":4,"total":13,"message":"l"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":4,"progress":4,"total":13,"message":"l"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":5,"progress":5,"total":13,"message":"o"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":5,"progress":5,"total":13,"message":"o"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":6,"progress":6,"total":13,"message":","}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":6,"progress":6,"total":13,"message":","}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":7,"progress":7,"total":13,"message":" "}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":7,"progress":7,"total":13,"message":" "}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":8,"progress":8,"total":13,"message":"w"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":8,"progress":8,"total":13,"message":"w"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":9,"progress":9,"total":13,"message":"o"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":9,"progress":9,"total":13,"message":"o"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":10,"progress":10,"total":13,"message":"r"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":10,"progress":10,"total":13,"message":"r"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":11,"progress":11,"total":13,"message":"l"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":11,"progress":11,"total":13,"message":"l"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":12,"progress":12,"total":13,"message":"d"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":12,"progress":12,"total":13,"message":"d"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":13,"progress":13,"total":13,"message":"!"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":13,"progress":13,"total":13,"message":"!"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","id":4,"result":{"content":[{"type":"text","text":"Processed 13 records successfully"}],"isError":false}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","id":4,"result":{"content":[{"type":"text","text":"Processed 13 records successfully"}],"isError":false}}

@jokemanfire
jokemanfire
commented
Jun 26, 2025

Copy link


Copy Markdown

MemberAuthor
Hello @olaservo If you have time, can you help me take a look?
@alexhancock
alexhancock
commented
Jun 27, 2025

Copy link


Copy Markdown

Contributor
So just to be clear, this is looking to everyone now like a client only issue?
@schwifty-brows Did you repro this only with inspector, or with a client in your actual codebase as well?
@jokemanfire
jokemanfire
commented
Jul 1, 2025

Copy link


Copy Markdown

MemberAuthor
Sorry for the update, the issue may be due to differences in the implementation of typescript-sdk.
@alexhancock
alexhancock
commented
Jul 3, 2025

Copy link


Copy Markdown

Contributor
@schwifty-brows Did this ever work for you with a different client?
@alexhancock
alexhancock
commented
Sep 10, 2025

Copy link


Copy Markdown

Contributor
@jokemanfire Do we want to rebase this one, and merge the example?
And then on the issues with progress notifications generally, @schwifty-brows last I looked it seemed to be an issue only with non rust-sdk clients. Have you verified if there is a client you can use that works with the server implementation of rust-sdk for sending progress notifications?
@jokemanfire
jokemanfire
commented
Sep 11, 2025

Copy link


Copy Markdown

MemberAuthor
@jokemanfire Do we want to rebase this one, and merge the example?
And then on the issues with progress notifications generally, @schwifty-brows last I looked it seemed to be an issue only with non rust-sdk clients. Have you verified if there is a client you can use that works with the server implementation of rust-sdk for sending progress notifications?
I will rebase it , providing richer examples can reduce the burden of development.

Regarding the differences in the implementation progress of the typescript SDK, I may not have time to take a look as I am not familiar with this language.
@github-actionsgithub-actionsBot
removed
the 
T-test
Testing related changes
label
Sep 12, 2025
@jokemanfire
chore(example): add example in progress
0e5abb0
Signed-off-by: jokemanfire <hu.dingyang@zte.com.cn>
@jokemanfire
jokemanfire
commented
Sep 12, 2025

Copy link


Copy Markdown

MemberAuthor
@alexhancock I will put most of the examples into system testing later when I have time.
@jokemanfire
jokemanfire
merged commit f8a747e
into
modelcontextprotocol:mainSep 13, 2025

11 checks passed

takumi-earth pushed a commit
to earthlings-dev/rmcp
that referenced
this pull request
Jan 27, 2026
@jokemanfire
chore(example): add example in progress (modelcontextprotocol#271)
6492d12
Signed-off-by: jokemanfire <hu.dingyang@zte.com.cn>
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@alexhancockalexhancockalexhancock approved these changes

Assignees


No one assigned


Labels

T-configConfiguration file changesT-dependenciesDependencies related changesT-documentationDocumentation improvementsT-examplesExample code changes

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

3 participants

@jokemanfire@schwifty-brows@alexhancock

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode");
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();

Skip to content
example: add example in progress - #271
Merged
jokemanfire merged 1 commit into
modelcontextprotocol:mainfrom 
jokemanfire:progress
Sep 13, 2025
Merged
example: add example in progress#271
jokemanfire merged 1 commit into
modelcontextprotocol:mainfrom 
jokemanfire:progress
Conversation
@jokemanfire
@jokemanfirejokemanfire
commented
Jun 18, 2025

Copy link


Copy Markdown

Member
Motivation and Context
add a example to introduce progress
How Has This Been Tested?
Breaking Changes
Types of changes
  •  Bug fix (non-breaking change which fixes an issue)
  •  New feature (non-breaking change which adds functionality)
  •  Breaking change (fix or feature that would cause existing functionality to change)
  •  Documentation update
Checklist
  •  I have read the MCP Documentation
  •  My code follows the repository's style guidelines
  •  New and existing tests pass locally
  •  I have added appropriate error handling
  •  I have added or updated documentation as needed
Additional context
@github-actionsgithub-actionsBot
added

T-documentation
Documentation improvements
T-dependencies
Dependencies related changes
T-config
Configuration file changes
T-examples
Example code changes
labels
Jun 18, 2025
@jokemanfirejokemanfire
mentioned this pull request
Jun 18, 2025

Closed

@schwifty-brows
schwifty-brows
commented
Jun 18, 2025

Copy link


Copy Markdown

i see the "simualte getting from a stream" but to really test, i would create a stream and process the resulting stream
@schwifty-brows
schwifty-brows
commented
Jun 18, 2025

Copy link


Copy Markdown

after that is added and you run the test, you should be able to see the return inconsistency
alexhancock
alexhancock
previously approved these changes
Jun 20, 2025
View reviewed changes
@alexhancockalexhancock
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

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

LGTM
@alexhancock
alexhancock
commented
Jun 20, 2025

Copy link


Copy Markdown

Contributor
I was able to verify/successfully run the example @schwifty-brows via python3 progress_test_client.py in examples/clients/scripts
Screenshot 2025-06-20 at 11 49 45 AM
Were you running into something different than me?
@schwifty-brows
schwifty-brows
commented
Jun 20, 2025
via email 

Copy link


Copy Markdown

@github-actionsgithub-actionsBot
added
the 
T-test
Testing related changes
label
Jun 21, 2025
@jokemanfire
jokemanfire
commented
Jun 21, 2025•

edited

Loading

Copy link


Copy Markdown

MemberAuthor
I think it is not rmcp's problem , I think it should be your business flow problem @schwifty-brows . And I have tested all the transport.
The current example file structure is not very good. In fact, this example is better placed in an integration test. I will modify this structure in another pr. @alexhancock
@schwifty-brows
schwifty-brows
commented
Jun 21, 2025

Copy link


Copy Markdown

how should we be sending SSE messages back? the progress notification is meant to do this, but running a simple example does not consistently work
@jokemanfire
jokemanfire
commented
Jun 24, 2025

Copy link


Copy Markdown

MemberAuthor
how should we be sending SSE messages back? the progress notification is meant to do this, but running a simple example does not consistently work
I really find it difficult to reproduce the abnormal scenario you mentioned. In the example, I should have provided a relatively simple example to send progress notifications from the server and obtain notification messages from the client. If it is a problem with the basic components of MCP SDK, then I believe that integration testing can definitely reproduce it (after excluding business interference). Could you please try to provide test cases that can be reproduced after excluding business impact.
@schwifty-brows
schwifty-brows
commented
Jun 24, 2025•

edited

Loading

Copy link


Copy Markdown

maybe i am missing something (i probably am) but in the code example, i dont see anything like this
i have a tool definition like so

#[tool(description = "do something")]
async fn search_warhouse(
&self,
#[tool(param)]
#[schemars(description = "query")]
query: String,
ctx: RequestContext<RoleServer>
) -> Result<CallToolResult, ErrorData>

and in my example 
//inject some strings into query_results
let mut query_results: Vec<String> = vec![];
let mut counter = 0;
for i in 0..query_results.len() {
let t = query_results[i].to_string();
let progress_param = ProgressNotificationParam {
progress_token: ProgressToken(NumberOrString::Number(counter)),
progress: counter,
total: Some(query_results.len() as u32),
message: Some("test".to_string()),
};
match ctx.peer.notify_progress(progress_param).await {
Ok(_) => {
counter += 1;
debug!("progress notification sent");
}
Err(e) => {
return Err(rmcp::Error::internal_error(
format!("failed to notify progress: {}", e),
Some(e.to_string().parse().unwrap())
));
}
}
}

 ctx.peer.notify_progress is used to send the notification. This is the problem area in question i dont see this as part of the example and where i keep getting 1-n notifications. If this is not the recommended way, that might be the problem
@alexhancock
alexhancock
commented
Jun 24, 2025

Copy link


Copy Markdown

Contributor
This part of the example server here seems relevant, and very similar to the ctx.peer.notify_progress example you're looking for @schwifty-brows
Does that make sense? Or if not maybe it's just github communication tripping me up from understanding. I would be happy to jump on a quick video call if you want tomorrow to discuss/get clear and identify any required improvements at the SDK level.
@schwifty-brows
schwifty-brows
commented
Jun 24, 2025

Copy link


Copy Markdown

Hey @alexhancock i think that would be a great idea!
Let me know your availability and I can walk you through the real world use case here.
@alexhancock
alexhancock
commented
Jun 25, 2025•

edited

Loading

Copy link


Copy Markdown

Contributor
Hey @alexhancock i think that would be a great idea!
Let me know your availability and I can walk you through the real world use case here.
@schwifty-brows How about 10am US eastern tomorrow? Email me (address on my profile) and we can set a meet.
@jokemanfirejokemanfire
mentioned this pull request
Jun 25, 2025
 Merged

9 tasks
@alexhancock
alexhancock
commented
Jun 25, 2025

Copy link


Copy Markdown

Contributor
@schwifty-brows@jokemanfire I think it may be a client difference...
When I run cargo run --example clients_progress_test_client -- --transport sse it works
�[2m2025-06-25T14:36:54.750050Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m RMCP Progress Notification Test Client
�[2m2025-06-25T14:36:54.750186Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m ==========================================
�[2m2025-06-25T14:36:54.750220Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Testing SSE Transport
�[2m2025-06-25T14:36:54.750229Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m =========================
�[2m2025-06-25T14:36:54.750237Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m SSE URL: http://127.0.0.1:8000/sse
�[2m2025-06-25T14:36:55.779656Z�[0m �[32m INFO�[0m �[1mserve_inner�[0m�[2m:�[0m �[2mrmcp::service�[0m�[2m:�[0m Service initialized as client �[3mpeer_info�[0m�[2m=�[0mSome(InitializeResult { protocol_version: ProtocolVersion("2024-11-05"), capabilities: ServerCapabilities { experimental: None, logging: None, completions: None, prompts: None, resources: None, tools: Some(ToolsCapability { list_changed: None }) }, server_info: Implementation { name: "rmcp", version: "0.1.5" }, instructions: Some("This server demonstrates progress notifications during long-running operations. Use the tools to see real-time progress updates for batch processing") })
�[2m2025-06-25T14:36:55.779944Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Connected to server: "rmcp"
�[2m2025-06-25T14:36:55.781660Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Available tools: ["stream_processor"]
�[2m2025-06-25T14:36:55.781674Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Starting to process 10 records...
�[2m2025-06-25T14:36:55.782563Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(1)), progress: 1, total: None, message: Some("H") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.782662Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [1]: 1/0 - H (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.782745Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(2)), progress: 2, total: None, message: Some("e") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.782804Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [2]: 2/0 - e (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.782893Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(3)), progress: 3, total: None, message: Some("l") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.782944Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [3]: 3/0 - l (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783056Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(4)), progress: 4, total: None, message: Some("l") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783124Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [4]: 4/0 - l (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783177Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(5)), progress: 5, total: None, message: Some("o") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783216Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [5]: 5/0 - o (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783289Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(6)), progress: 6, total: None, message: Some(",") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783339Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [6]: 6/0 - , (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783409Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(7)), progress: 7, total: None, message: Some(" ") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783450Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [7]: 7/0 - (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783509Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(8)), progress: 8, total: None, message: Some("w") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783549Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [8]: 8/0 - w (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783598Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(9)), progress: 9, total: None, message: Some("o") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783636Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [9]: 9/0 - o (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783690Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(10)), progress: 10, total: None, message: Some("r") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783725Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [10]: 10/0 - r (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783777Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(11)), progress: 11, total: None, message: Some("l") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783811Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [11]: 11/0 - l (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783858Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(12)), progress: 12, total: None, message: Some("d") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783893Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [12]: 12/0 - d (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.783941Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m received notification �[3mnotification�[0m�[2m=�[0mProgressNotification(Notification { method: ProgressNotificationMethod, params: ProgressNotificationParam { progress_token: ProgressToken(Number(13)), progress: 13, total: None, message: Some("!") }, extensions: Extensions })
�[2m2025-06-25T14:36:55.783973Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Progress update [13]: 13/0 - ! (elapsed: 0.0s)
�[2m2025-06-25T14:36:55.784108Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Processing completed: Processed 13 records successfully
�[2m2025-06-25T14:36:55.784174Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m task cancelled
�[2m2025-06-25T14:36:55.784195Z�[0m �[32m INFO�[0m �[2mrmcp::service�[0m�[2m:�[0m serve finished �[3mquit_reason�[0m�[2m=�[0mCancelled
�[2m2025-06-25T14:36:55.784352Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Total progress notifications received: 13
�[2m2025-06-25T14:36:55.784370Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m Total time elapsed: 0.01s
�[2m2025-06-25T14:36:55.784383Z�[0m �[32m INFO�[0m �[2mclients_progress_test_client�[0m�[2m:�[0m SSE transport test completed successfully!

However when I use the MCP inspector as another client to test with by running
cargo run --example servers_progress_demo -- sse

and connect to it via
npx @modelcontextprotocol/inspector

I see this when I run the stream processor tool I only see one progress notification despite it processing 13 records. This is similar to what @schwifty-brows reproduces with his test client:
Screenshot 2025-06-25 at 10 36 08 AM
@jokemanfire Any ideas?
@jokemanfire
jokemanfire
commented
Jun 26, 2025

Copy link


Copy Markdown

MemberAuthor
It does seem to be related to the client, I will take a look at the inspector and compare the implementation differences.
@jokemanfire
jokemanfire
commented
Jun 26, 2025•

edited

Loading

Copy link


Copy Markdown

MemberAuthor
I used Wireshark to capture packets, and I can confirm that the notify packet for Rust SDK was sent. I may need to take a look at the inspector code now.
image
All the [PSH,ACK] is the data.
@jokemanfire
jokemanfire
commented
Jun 26, 2025•

edited

Loading

Copy link


Copy Markdown

MemberAuthor
I have add log in inspector , I can make sure the mcpProxy recived the progress data, the problem should in inspector's front end.
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":1,"progress":1,"total":13,"message":"H"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":1,"progress":1,"total":13,"message":"H"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":2,"progress":2,"total":13,"message":"e"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":2,"progress":2,"total":13,"message":"e"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":3,"progress":3,"total":13,"message":"l"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":3,"progress":3,"total":13,"message":"l"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":4,"progress":4,"total":13,"message":"l"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":4,"progress":4,"total":13,"message":"l"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":5,"progress":5,"total":13,"message":"o"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":5,"progress":5,"total":13,"message":"o"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":6,"progress":6,"total":13,"message":","}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":6,"progress":6,"total":13,"message":","}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":7,"progress":7,"total":13,"message":" "}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":7,"progress":7,"total":13,"message":" "}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":8,"progress":8,"total":13,"message":"w"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":8,"progress":8,"total":13,"message":"w"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":9,"progress":9,"total":13,"message":"o"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":9,"progress":9,"total":13,"message":"o"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":10,"progress":10,"total":13,"message":"r"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":10,"progress":10,"total":13,"message":"r"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":11,"progress":11,"total":13,"message":"l"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":11,"progress":11,"total":13,"message":"l"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":12,"progress":12,"total":13,"message":"d"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":12,"progress":12,"total":13,"message":"d"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":13,"progress":13,"total":13,"message":"!"}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","method":"notifications/progress","params":{"progressToken":13,"progress":13,"total":13,"message":"!"}}
[mcpProxy] Received message from SERVER: {"jsonrpc":"2.0","id":4,"result":{"content":[{"type":"text","text":"Processed 13 records successfully"}],"isError":false}}
[mcpProxy] Forwarded message to CLIENT: {"jsonrpc":"2.0","id":4,"result":{"content":[{"type":"text","text":"Processed 13 records successfully"}],"isError":false}}

@jokemanfire
jokemanfire
commented
Jun 26, 2025

Copy link


Copy Markdown

MemberAuthor
Hello @olaservo If you have time, can you help me take a look?
@alexhancock
alexhancock
commented
Jun 27, 2025

Copy link


Copy Markdown

Contributor
So just to be clear, this is looking to everyone now like a client only issue?
@schwifty-brows Did you repro this only with inspector, or with a client in your actual codebase as well?
@jokemanfire
jokemanfire
commented
Jul 1, 2025

Copy link


Copy Markdown

MemberAuthor
Sorry for the update, the issue may be due to differences in the implementation of typescript-sdk.
@alexhancock
alexhancock
commented
Jul 3, 2025

Copy link


Copy Markdown

Contributor
@schwifty-brows Did this ever work for you with a different client?
@alexhancock
alexhancock
commented
Sep 10, 2025

Copy link


Copy Markdown

Contributor
@jokemanfire Do we want to rebase this one, and merge the example?
And then on the issues with progress notifications generally, @schwifty-brows last I looked it seemed to be an issue only with non rust-sdk clients. Have you verified if there is a client you can use that works with the server implementation of rust-sdk for sending progress notifications?
@jokemanfire
jokemanfire
commented
Sep 11, 2025

Copy link


Copy Markdown

MemberAuthor
@jokemanfire Do we want to rebase this one, and merge the example?
And then on the issues with progress notifications generally, @schwifty-brows last I looked it seemed to be an issue only with non rust-sdk clients. Have you verified if there is a client you can use that works with the server implementation of rust-sdk for sending progress notifications?
I will rebase it , providing richer examples can reduce the burden of development.

Regarding the differences in the implementation progress of the typescript SDK, I may not have time to take a look as I am not familiar with this language.
@github-actionsgithub-actionsBot
removed
the 
T-test
Testing related changes
label
Sep 12, 2025
@jokemanfire
chore(example): add example in progress
0e5abb0
Signed-off-by: jokemanfire <hu.dingyang@zte.com.cn>
@jokemanfire
jokemanfire
commented
Sep 12, 2025

Copy link


Copy Markdown

MemberAuthor
@alexhancock I will put most of the examples into system testing later when I have time.
@jokemanfire
jokemanfire
merged commit f8a747e
into
modelcontextprotocol:mainSep 13, 2025

11 checks passed

takumi-earth pushed a commit
to earthlings-dev/rmcp
that referenced
this pull request
Jan 27, 2026
@jokemanfire
chore(example): add example in progress (modelcontextprotocol#271)
6492d12
Signed-off-by: jokemanfire <hu.dingyang@zte.com.cn>
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@alexhancockalexhancockalexhancock approved these changes

Assignees


No one assigned


Labels

T-configConfiguration file changesT-dependenciesDependencies related changesT-documentationDocumentation improvementsT-examplesExample code changes

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

3 participants

@jokemanfire@schwifty-brows@alexhancock