Skip to content

Conversation

@morinokami
Copy link
Contributor

Motivation and Context

Added completions to ServerCapabilitiesSchema in accordance with spec update #173, which introduced the completions capability.

Related: #268

How Has This Been Tested?

Confirmed visually that completions is present in the ServerCapabilities type. As this is an optional property, it is not expected to introduce a breaking change.

Breaking Changes

N/A

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

Copy link
Member

@jspahrsummers jspahrsummers left a comment

Choose a reason for hiding this comment

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

Thanks!

@jspahrsummers jspahrsummers merged commit 39e6ec5 into modelcontextprotocol:main Apr 7, 2025
2 checks passed
Pizzaface pushed a commit to RewstApp/mcp-inspector that referenced this pull request May 2, 2025
…protocol#269)

- Add logging for initialize request and response in useConnection.connect
- Include server capabilities, version, and instructions in history
Pizzaface pushed a commit to RewstApp/mcp-inspector that referenced this pull request May 2, 2025
…w-initialize-request-in-history

feat: Show initialize request/response in History panel (modelcontextprotocol#269)
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