attempt to break up readme between server and client

Author: jcat4

README.md

@@ -10,34 +10,9 @@ Add this line to your application's Gemfile:
 gem 'mcp'
 ```
 
-### Optional Dependencies
+You may need to add additional dependencies depending on which features you wish to access.
 
-The MCP gem has different dependency requirements depending on your use case:
-
-**For Server-only usage:**
-```ruby
-gem 'mcp'
-```
-
-**For client HTTP transport usage:**
-```ruby
-gem 'mcp'
-gem 'faraday', '>= 2.0'
-```
-
-And then execute:
-
-```console
-$ bundle install
-```
-
-Or install it yourself as:
-
-```console
-$ gem install mcp
-```
-
-## MCP Server
+## Building an MCP Server
 
 The `MCP::Server` class is the core component that handles JSON-RPC requests and responses.
 It implements the Model Context Protocol specification, handling model context requests and responses.
@@ -231,67 +206,6 @@ $ ruby examples/stdio_server.rb
 {"jsonrpc":"2.0","id":"2","method":"tools/list"}
 ```
 
-## MCP Client
-
-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.
-
-**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.
-
-### HTTP Client
-
-The `MCP::Client::Http` class provides a simple HTTP client for interacting with MCP servers:
-
-```ruby
-client = MCP::Client::Http.new(url: "https://api.example.com/mcp")
-
-# List available tools
-tools = client.tools
-tools.each do |tool|
-  puts "Tool: #{tool.name}"
-  puts "Description: #{tool.description}"
-  puts "Input Schema: #{tool.input_schema}"
-end
-
-# Call a specific tool
-response = client.call_tool(
-  tool: tools.first,
-  input: { message: "Hello, world!" }
-)
-```
-
-The HTTP client supports:
-- Tool listing via the `tools/list` method
-- Tool invocation via the `tools/call` method
-- Automatic JSON-RPC 2.0 message formatting
-- UUID v7 request ID generation
-- Setting headers for things like authorization
-
-### HTTP Authorization
-
-By default, the HTTP client has no authentication, but it supports custom headers for authentication. For example, to use Bearer token authentication:
-
-```ruby
-client = MCP::Client::Http.new(
-  url: "https://api.example.com/mcp",
-  headers: {
-    "Authorization" => "Bearer my_token"
-  }
-)
-
-client.tools # will make the call using Bearer auth
-```
-
-You can add any custom headers needed for your authentication scheme. The client will include these headers in all requests.
-
-### Tool Objects
-
-The client provides wrapper objects for tools returned by the server:
-
-- `MCP::Client::Tool` - Represents a single tool with its metadata
-- `MCP::Client::Tools` - Collection of tools with enumerable functionality
-
-These objects provide easy access to tool properties like name, description, and input schema.
-
 ## Configuration
 
 The gem can be configured using the `MCP.configure` block:
@@ -659,6 +573,74 @@ end
 
 otherwise `resources/read` requests will be a no-op.
 
+## Building an MCP Client
+
+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.
+
+**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.
+
+### HTTP Transport Layer
+
+You'll need to add `faraday` as a dependency to use the HTTP transport layer.
+
+```ruby
+gem 'mcp'
+gem 'faraday', '>= 2.0'
+```
+
+The `MCP::Client::Http` class provides a simple HTTP client for interacting with MCP servers:
+
+```ruby
+client = MCP::Client::Http.new(url: "https://api.example.com/mcp")
+
+# List available tools
+tools = client.tools
+tools.each do |tool|
+  puts "Tool: #{tool.name}"
+  puts "Description: #{tool.description}"
+  puts "Input Schema: #{tool.input_schema}"
+end
+
+# Call a specific tool
+response = client.call_tool(
+  tool: tools.first,
+  input: { message: "Hello, world!" }
+)
+```
+
+The HTTP client supports:
+- Tool listing via the `tools/list` method
+- Tool invocation via the `tools/call` method
+- Automatic JSON-RPC 2.0 message formatting
+- UUID v7 request ID generation
+- Setting headers for things like authorization
+
+#### HTTP Authorization
+
+By default, the HTTP client has no authentication, but it supports custom headers for authentication. For example, to use Bearer token authentication:
+
+```ruby
+client = MCP::Client::Http.new(
+  url: "https://api.example.com/mcp",
+  headers: {
+    "Authorization" => "Bearer my_token"
+  }
+)
+
+client.tools # will make the call using Bearer auth
+```
+
+You can add any custom headers needed for your authentication scheme. The client will include these headers in all requests.
+
+### Tool Objects
+
+The client provides wrapper objects for tools returned by the server:
+
+- `MCP::Client::Tool` - Represents a single tool with its metadata
+- `MCP::Client::Tools` - Collection of tools with enumerable functionality
+
+These objects provide easy access to tool properties like name, description, and input schema.
+
 ## Releases
 
 This gem is published to [RubyGems.org](https://rubygems.org/gems/mcp)