1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
//! Handler traits for extensible MCP protocol support
//!
//! This module provides trait definitions for handling various MCP protocol
//! features including elicitation, completion, resource templates, and ping.
//!
//! ## Handler Types
//!
//! ### [`ElicitationHandler`]
//! Handle server-initiated user input requests. Useful for asking users for
//! additional information during tool execution.
//!
//! ### [`CompletionProvider`]
//! Provide argument completion suggestions for tools and commands. Implements
//! autocomplete functionality in MCP clients.
//!
//! ### [`ResourceTemplateHandler`]
//! Manage dynamic resource templates with parameter substitution. Enables
//! pattern-based resource access (e.g., `file:///{path}`).
//!
//! ### [`PingHandler`]
//! Handle bidirectional ping/pong for connection health monitoring.
//!
//! ## Example: Implementing an Elicitation Handler
//!
//! ```rust
//! use turbomcp_protocol::{ElicitationHandler, ElicitationContext, ElicitationResponse};
//! use turbomcp_protocol::Result;
//! use std::collections::HashMap;
//! use std::future::Future;
//! use std::pin::Pin;
//!
//! struct MyElicitationHandler;
//!
//! impl ElicitationHandler for MyElicitationHandler {
//! fn handle_elicitation(
//! &self,
//! context: &ElicitationContext
//! ) -> Pin<Box<dyn Future<Output = Result<ElicitationResponse>> + Send + '_>> {
//! let can_handle = self.can_handle(context);
//! Box::pin(async move {
//! // Check if we can handle this elicitation type
//! if !can_handle {
//! return Ok(ElicitationResponse {
//! accepted: false,
//! content: None,
//! decline_reason: Some("Unsupported elicitation type".to_string()),
//! });
//! }
//!
//! // Process the elicitation (e.g., prompt user)
//! let mut response_data = HashMap::new();
//! response_data.insert(
//! "user_input".to_string(),
//! serde_json::json!("User provided value")
//! );
//!
//! Ok(ElicitationResponse {
//! accepted: true,
//! content: Some(response_data),
//! decline_reason: None,
//! })
//! })
//! }
//!
//! fn can_handle(&self, context: &ElicitationContext) -> bool {
//! // Check if elicitation has required input
//! context.required && !context.message.is_empty()
//! }
//!
//! fn priority(&self) -> i32 {
//! 100 // Higher priority than default (0)
//! }
//! }
//! ```
//!
//! ## Example: Implementing a Completion Provider
//!
//! ```rust
//! use turbomcp_protocol::{CompletionProvider, CompletionContext, CompletionItem};
//! use turbomcp_protocol::Result;
//! use std::future::Future;
//! use std::pin::Pin;
//!
//! struct FilePathCompletionProvider;
//!
//! impl CompletionProvider for FilePathCompletionProvider {
//! fn provide_completions(
//! &self,
//! context: &CompletionContext
//! ) -> Pin<Box<dyn Future<Output = Result<Vec<CompletionItem>>> + Send + '_>> {
//! Box::pin(async move {
//! // Provide file path completions
//! let completions = vec![
//! CompletionItem {
//! value: "/home/user/documents".to_string(),
//! label: Some("Documents".to_string()),
//! documentation: Some("User documents folder".to_string()),
//! sort_priority: Some(1),
//! insert_text: None,
//! metadata: Default::default(),
//! },
//! CompletionItem {
//! value: "/home/user/downloads".to_string(),
//! label: Some("Downloads".to_string()),
//! documentation: Some("Downloads folder".to_string()),
//! sort_priority: Some(2),
//! insert_text: None,
//! metadata: Default::default(),
//! },
//! ];
//!
//! Ok(completions)
//! })
//! }
//!
//! fn can_provide(&self, context: &CompletionContext) -> bool {
//! // Only provide completions for "path" arguments
//! context.argument_name.as_deref() == Some("path")
//! }
//! }
//! ```
use Value;
use HashMap;
use Future;
use Pin;
use crateResult;
use crate;
/// Handler for server-initiated elicitation requests
/// Response to an elicitation request
/// Provider for argument completion
/// A single completion item
/// Handler for resource templates
/// Resource template definition
/// Template parameter definition
/// Resolved resource from template
/// Handler for bidirectional ping requests
/// Response to a ping request
/// Capabilities for server-initiated features
/// Handler capability tracking
/// Handler for JSON-RPC requests - Core abstraction for MCP protocol implementation
///
/// This trait provides a transport-agnostic interface for handling MCP JSON-RPC requests.
/// Implementations of this trait can work seamlessly across all transport layers
/// (HTTP, STDIO, WebSocket, etc.) without transport-specific code.
///
/// # Architecture
///
/// The `JsonRpcHandler` trait serves as the bridge between:
/// - **Protocol Logic**: Tools, resources, prompts dispatch (typically macro-generated)
/// - **Transport Layer**: HTTP, STDIO, WebSocket protocol details
///
/// This separation enables:
/// - Clean, testable handler implementations
/// - Transport-agnostic server code
/// - Full current MCP compliance in the transport layer
/// - Compile-time dispatch optimizations in handlers
///
/// # Example: Macro-Generated Implementation
///
/// ```rust,ignore
/// use turbomcp_protocol::JsonRpcHandler;
/// use serde_json::Value;
///
/// #[derive(Clone)]
/// struct WeatherServer;
///
/// impl JsonRpcHandler for WeatherServer {
/// async fn handle_request(&self, req: Value) -> Value {
/// // Parse method and dispatch
/// let method = req["method"].as_str().unwrap_or("");
/// match method {
/// "initialize" => { /* ... */ },
/// "tools/call" => { /* dispatch to tools */ },
/// "resources/read" => { /* dispatch to resources */ },
/// _ => serde_json::json!({"error": "method not found"}),
/// }
/// }
///
/// fn server_info(&self) -> ServerInfo {
/// ServerInfo {
/// name: "Weather Server".to_string(),
/// version: "1.0.0".to_string(),
/// }
/// }
/// }
/// ```
///
/// # Usage with Transports
///
/// ```rust,ignore
/// // HTTP Transport
/// use turbomcp_transport::streamable_http::StreamableHttpTransport;
///
/// let handler = Arc::new(WeatherServer);
/// let transport = StreamableHttpTransport::new(config, handler);
/// transport.run().await?;
///
/// // STDIO Transport
/// use turbomcp_transport::stdio::StdioTransport;
///
/// let handler = Arc::new(WeatherServer);
/// let transport = StdioTransport::new(handler);
/// transport.run().await?;
/// ```
/// Server metadata information