Skip to content

Conversation

@cliffhall
Copy link
Member

Description

In src/everything/server/roots.ts

  • refer to roots as optional in clientCapabilities

Server Details

  • Server: everything
  • Changes to: roots

Motivation and Context

Referring to clientCapabilities.roots causes an error if the client doesn't support roots.
See #2818

How Has This Been Tested?

As per the steps to reproduce in #2818
Screenshot 2026-01-10 at 5 35 42 PM

Breaking Changes

Nope.

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 Protocol Documentation
  • My changes follows MCP security best practices
  • I have updated the server's README accordingly
  • I have tested this with an LLM client
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have documented all environment variables and configuration options

Additional context

Fixes #2818

@cliffhall cliffhall requested a review from olaservo January 10, 2026 22:42
@cliffhall cliffhall changed the title In roots.ts, clientCapabilites.roots and response.roots are optional. Fix error when referring to roots Jan 10, 2026
@cliffhall cliffhall changed the title Fix error when referring to roots Everything server - Fix error when referring to roots Jan 10, 2026
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.

Built and tested locally in inspector to double check existing functionality.

@olaservo olaservo merged commit 861c11b into modelcontextprotocol:main Jan 11, 2026
18 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.

server/everything reports error when requesting tools

2 participants