Skip to content

Conversation

pavan-mellamputi-socure
Copy link
Contributor

It shoud be notifications/progress not notification/progress (not singular).

This matches the latest spec.

https://modelcontextprotocol.io/specification/2025-06-18/basic/utilities/progress

Fixed a typo that displayed the method name as notification/progress (singular) instead of notifications/progress (plural) in Server Notifications section.

Motivation and Context

The typo led me to start looking to fastmcp python code as I thought that there was bug in fastmcp code.

How Has This Been Tested?

I verified it in the inspector UI.

Breaking Changes

It is a very minor change. Not a breaking change.

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

N/A

It shoud be `notifications/progress` not `notification/progress` (not singular).

This matches the latest spec.

https://modelcontextprotocol.io/specification/2025-06-18/basic/utilities/progress
Copy link
Member

@olaservo olaservo left a comment

Choose a reason for hiding this comment

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

Thanks!

@olaservo olaservo merged commit 2441094 into modelcontextprotocol:main Sep 1, 2025
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants