Skip to content

Commit d571830

Browse files
committed
patch up lingering ModelContextProtocol references
1 parent 72e07aa commit d571830

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

README.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -233,16 +233,16 @@ $ ruby examples/stdio_server.rb
233233

234234
## MCP Client
235235

236-
The `ModelContextProtocol::Client` module provides client implementations for interacting with MCP servers. Currently, it supports HTTP transport for making JSON-RPC requests to MCP servers.
236+
The `MCP::Client` module provides client implementations for interacting with MCP servers. Currently, it supports HTTP transport for making JSON-RPC requests to MCP servers.
237237

238238
**Note:** The client HTTP transport requires the `faraday` gem. Add `gem 'faraday', '>= 2.0'` to your Gemfile if you plan to use the client HTTP transport functionality.
239239

240240
### HTTP Client
241241

242-
The `ModelContextProtocol::Client::Http` class provides a simple HTTP client for interacting with MCP servers:
242+
The `MCP::Client::Http` class provides a simple HTTP client for interacting with MCP servers:
243243

244244
```ruby
245-
client = ModelContextProtocol::Client::Http.new(url: "https://api.example.com/mcp")
245+
client = MCP::Client::Http.new(url: "https://api.example.com/mcp")
246246

247247
# List available tools
248248
tools = client.tools
@@ -271,7 +271,7 @@ The HTTP client supports:
271271
By default, the HTTP client has no authentication, but it supports custom headers for authentication. For example, to use Bearer token authentication:
272272

273273
```ruby
274-
client = ModelContextProtocol::Client::Http.new(
274+
client = MCP::Client::Http.new(
275275
url: "https://api.example.com/mcp",
276276
headers: {
277277
"Authorization" => "Bearer my_token"
@@ -287,8 +287,8 @@ You can add any custom headers needed for your authentication scheme. The client
287287

288288
The client provides wrapper objects for tools returned by the server:
289289

290-
- `ModelContextProtocol::Client::Tool` - Represents a single tool with its metadata
291-
- `ModelContextProtocol::Client::Tools` - Collection of tools with enumerable functionality
290+
- `MCP::Client::Tool` - Represents a single tool with its metadata
291+
- `MCP::Client::Tools` - Collection of tools with enumerable functionality
292292

293293
These objects provide easy access to tool properties like name, description, and input schema.
294294

0 commit comments

Comments
 (0)