Add audio content

[Yikuanzz]

To issues#243

• Add audio content in mcp/types.go and the exmaple in examples/everything/main.go

Audio type as a responsee:

{
  "type": "audio",
  "data": "base64-encoded-audio-data",
  "mimeType": "audio/wav"
}

Summary by CodeRabbit

• New Features
  • Introduced support for audio content, allowing audio data (with MIME type and base64 encoding) to be provided in responses.
  • Added a new tool for generating and returning audio content alongside text and images.
• Other Changes
  • Changed the server listening port from 8080 to 8081.

[coderabbitai]

Walkthrough

A new audio content type is introduced for use with LLMs, including a corresponding Go struct and handler. The example application registers a new audio tool, updates its handler logic to return audio content, and changes the SSE server port. Minor code cleanups and type generalizations are also included.

Changes

Files/Paths	Change Summary
examples/everything/main.go	Adds a GET_AUDIO tool and handler, introduces MCP_AUDIO constant, updates prompt handling to include audio content, changes SSE server port to 8081, performs minor type and formatting cleanups.
mcp/types.go	Adds AudioContent struct to represent audio data, implements the Content interface for audio, mirroring existing content types.

Possibly related PRs

• change to strong content type #26: Refactors the Content field to use the Content interface and adds parsing functions, which the new audio content type and handler directly build upon.

Suggested reviewers

• ezynda3

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f47e2bc and 6c6e37e.

📒 Files selected for processing (2)

• examples/everything/main.go (7 hunks)
• mcp/types.go (1 hunks)

🧰 Additional context used

🧬 Code Graph Analysis (1)

examples/everything/main.go (3)

mcp/tools.go (4)

• NewTool (161-183)
• WithDescription (204-208)
• CallToolRequest (44-59)
• CallToolResult (34-41)

mcp/prompts.go (2)

• Role (68-68)
• RoleUser (71-71)

mcp/types.go (5)

• Content (684-686)
• AudioContent (714-721)
• AudioContent (723-723)
• TextContent (690-695)
• TextContent (697-697)

🔇 Additional comments (7)

mcp/types.go (1)

712-723: Well-structured implementation of the AudioContent type

The AudioContent struct follows the same pattern as existing content types like TextContent and ImageContent, with appropriate JSON tags and field definitions. This ensures consistency throughout the codebase.

examples/everything/main.go (6)

22-22: LGTM: New audio tool constant added

This constant follows the existing naming convention for tools.

---

157-159: LGTM: Tool registration follows established pattern

The audio tool is registered consistently with other tools in the system.

---

286-293: LGTM: Audio content properly added to complex prompt

The audio content is correctly integrated into the complex prompt handler, properly using the MCP_AUDIO constant as its data source.

---

384-384: Use of 'any' type alias improves code readability

Replacing interface{} with any follows modern Go conventions (introduced in Go 1.18) and improves code readability.

---

493-494: SSE server port changed from 8080 to 8081

The SSE server now listens on port 8081 instead of 8080. Ensure this change is intentional and documented appropriately for users of the example.

---

504-507: LGTM: New MCP_AUDIO constant for minimal audio data

The implementation adds a base64-encoded minimal audio data constant that can be used throughout the codebase, similar to the existing MCP_TINY_IMAGE constant.

[dugenkui03]

hi @Yikuanzz, I believe this pr will not work, for example, you forget update ParseContent.

There is another pr for audio content type #250

[Yikuanzz]

hi @Yikuanzz, I believe this pr will not work, for example, you forget update ParseContent.

There is another pr for audio content type #250
Sure, I got it. Thanks for your reply, I had indeed forgotten that.