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
//! MCP Server Composition
//!
//! This module provides the `FoundationClient` trait and implementations for
//! domain servers to call foundation servers in a deployment-agnostic way.
//!
//! # Overview
//!
//! MCP Server Composition enables domain-tier servers to orchestrate calls to
//! foundation-tier servers. The `FoundationClient` trait provides a unified
//! interface that works across different deployment targets:
//!
//! - **Local development**: HTTP transport to local servers
//! - **pmcp.run deployment**: Lambda direct invocation via `CompositionClient`
//! - **Other platforms**: Custom implementations
//!
//! # Example
//!
//! ```rust,ignore
//! use pmcp::composition::{FoundationClient, McpFoundationClient, FoundationConfig};
//! use std::sync::Arc;
//!
//! // Load configuration from foundations.toml
//! let config = FoundationConfig::from_file("foundations.toml")?;
//!
//! // Create client for foundation server
//! let client = McpFoundationClient::new(config).await?;
//!
//! // Call a tool on the foundation server
//! let result = client.call_tool(
//! "calculator",
//! "add",
//! &serde_json::json!({"a": 5, "b": 3})
//! ).await?;
//! ```
//!
//! # Configuration
//!
//! Foundation server endpoints are configured in a `foundations.toml` file,
//! typically generated during schema export:
//!
//! ```toml
//! [foundations.calculator]
//! url = "http://localhost:8080"
//!
//! [foundations.database]
//! url = "http://localhost:8081"
//! ```
pub use ;
pub use CompositionError;
pub use McpFoundationClient;
pub use ;
use async_trait;
use DeserializeOwned;
/// Trait for calling foundation servers from domain servers.
///
/// This trait provides a deployment-agnostic interface for domain servers
/// to call foundation servers. Implementations include:
///
/// - `McpFoundationClient`: Uses the MCP client over HTTP for local/generic deployments
/// - `CompositionClient` (in pmcp-composition): Uses Lambda direct invocation for pmcp.run
///
/// # Example
///
/// ```rust,ignore
/// use pmcp::composition::FoundationClient;
///
/// async fn use_calculator(client: &impl FoundationClient) -> Result<f64, pmcp::composition::CompositionError> {
/// let result = client.call_tool(
/// "calculator",
/// "add",
/// &serde_json::json!({"a": 10, "b": 5})
/// ).await?;
///
/// // Parse the result
/// let value: serde_json::Value = serde_json::from_str(&result)?;
/// Ok(value["result"].as_f64().unwrap_or(0.0))
/// }
/// ```
/// Extract text content from a resource result.
///
/// This is a utility function for extracting text from resource content.
///
/// # Example
///
/// ```rust,ignore
/// let content = client.read_resource("calculator", "calculator://help/guide").await?;
/// let text = pmcp::composition::extract_resource_text(&content)?;
/// println!("Guide: {}", text);
/// ```