Skip to content

Add Content::Audio class for audio content type#243

Merged
koic merged 1 commit intomodelcontextprotocol:mainfrom
koic:add_content_audio
Mar 1, 2026
Merged

Add Content::Audio class for audio content type#243
koic merged 1 commit intomodelcontextprotocol:mainfrom
koic:add_content_audio

Conversation

@koic
Copy link
Member

@koic koic commented Feb 27, 2026

Motivation and Context

The MCP spec defines an audio content type, but the SDK only had Content::Text and Content::Image. Add Content::Audio with the same structure as Content::Image.

https://modelcontextprotocol.io/specification/2025-11-25/server/tools#audio-content

How Has This Been Tested?

Pass the newly added tests.

Breaking Changes

None.

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

atesgoral
atesgoral previously approved these changes Mar 1, 2026
The MCP spec defines an audio content type, but the SDK only had
`Content::Text` and `Content::Image`. Add `Content::Audio` with the
same structure as `Content::Image`.

https://modelcontextprotocol.io/specification/2025-11-25/server/tools#audio-content
@koic
Copy link
Member Author

koic commented Mar 1, 2026

There were conflicts in the source code, so it has been rebased onto the latest main branch. Could you review it again?

@koic koic merged commit 2fc4f5e into modelcontextprotocol:main Mar 1, 2026
10 checks passed
@koic koic deleted the add_content_audio branch March 1, 2026 16:30
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