You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/everything/README.md
+19Lines changed: 19 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -89,6 +89,13 @@ This MCP server attempts to exercise all the features of the MCP protocol. It is
89
89
- `structuredContent` field conformant to the output schema
90
90
- A backward compatible Text Content field, a SHOULD advisory in the specification
91
91
92
+
11. `listRoots`
93
+
- Lists the current MCP roots provided by the client
94
+
- Demonstrates the roots protocol capability even though this server doesn't access files
95
+
- No inputs required
96
+
- Returns: List of current roots with their URIs and names, or a message if no roots are set
97
+
- Shows how servers can interact with the MCP roots protocol
98
+
92
99
### Resources
93
100
94
101
The server provides 100 test resources in two formats:
@@ -129,6 +136,18 @@ Resource features:
129
136
- Returns: Multi-turn conversation with an embedded resource reference
130
137
- Shows how to include resources directly in prompt messages
131
138
139
+
### Roots
140
+
141
+
The server demonstrates the MCP roots protocol capability:
142
+
143
+
- Declares `roots: { listChanged: true }` capability to indicate support for roots
144
+
- Handles `roots/list_changed` notifications from clients
145
+
- Requests initial roots during server initialization
146
+
- Provides a `listRoots` tool to display current roots
147
+
- Logs roots-related events for demonstration purposes
148
+
149
+
Note: This server doesn't actually access files, but demonstrates how servers can interact with the roots protocol for clients that need to understand which directories are available for file operations.
150
+
132
151
### Logging
133
152
134
153
The server sends random-leveled log messages every 15 seconds, e.g.:
0 commit comments