chore: add markdownlint on pre-commit hook and lint md files (#996)

Co-authored-by: Marcelo Trylesinski <marcelotryle@gmail.com>

examples/clients/simple-auth-client/README.md

@@ -47,7 +47,7 @@ The client will open your browser for authentication. After completing OAuth, yo
 
 ## Example
 
-```
+```markdown
 🔐 Simple MCP Auth Client
 Connecting to: http://localhost:3001
 

examples/clients/simple-chatbot/README.MD

@@ -25,11 +25,12 @@ This example demonstrates how to integrate the Model Context Protocol (MCP) into
    ```plaintext
    LLM_API_KEY=your_api_key_here
    ```
+
    **Note:** The current implementation is configured to use the Groq API endpoint (`https://api.groq.com/openai/v1/chat/completions`) with the `llama-3.2-90b-vision-preview` model. If you plan to use a different LLM provider, you'll need to modify the `LLMClient` class in `main.py` to use the appropriate endpoint URL and model parameters.
 
 3. **Configure servers:**
 
-   The `servers_config.json` follows the same structure as Claude Desktop, allowing for easy integration of multiple servers. 
+   The `servers_config.json` follows the same structure as Claude Desktop, allowing for easy integration of multiple servers.
    Here's an example:
 
    ```json
@@ -46,9 +47,11 @@ This example demonstrates how to integrate the Model Context Protocol (MCP) into
      }
    }
    ```
+
    Environment variables are supported as well. Pass them as you would with the Claude Desktop App.
 
    Example:
+
    ```json
    {
      "mcpServers": {
@@ -72,7 +75,7 @@ This example demonstrates how to integrate the Model Context Protocol (MCP) into
    ```
 
 2. **Interact with the assistant:**
-   
+
    The assistant will automatically detect available tools and can respond to queries based on the tools provided by the configured servers.
 
 3. **Exit the session:**
@@ -86,6 +89,7 @@ This example demonstrates how to integrate the Model Context Protocol (MCP) into
 - **Server Integration**: Supports any MCP-compatible server, tested with various server implementations including Uvicorn and Node.js.
 
 ### Class Structure
+
 - **Configuration**: Manages environment variables and server configurations
 - **Server**: Handles MCP server initialization, tool discovery, and execution
 - **Tool**: Represents individual tools with their properties and formatting
@@ -107,5 +111,3 @@ This example demonstrates how to integrate the Model Context Protocol (MCP) into
      - If it's a direct response → return to user
    - Tool results are sent back to LLM for interpretation
    - Final response is presented to user
-
-

examples/servers/simple-auth/README.md

@@ -4,7 +4,6 @@ This example demonstrates OAuth 2.0 authentication with the Model Context Protoc
 
 ---
 
-
 ## Running the Servers
 
 ### Step 1: Start Authorization Server
@@ -18,6 +17,7 @@ uv run mcp-simple-auth-as --port=9000
 ```
 
 **What it provides:**
+
 - OAuth 2.0 flows (registration, authorization, token exchange)
 - Simple credential-based authentication (no external provider needed)  
 - Token introspection endpoint for Resource Servers (`/introspect`)
@@ -38,7 +38,6 @@ uv run mcp-simple-auth-rs --port=8001 --auth-server=http://localhost:9000  --tra
 
 ```
 
-
 ### Step 3: Test with Client
 
 ```bash
@@ -47,15 +46,16 @@ cd examples/clients/simple-auth-client
 MCP_SERVER_PORT=8001 MCP_TRANSPORT_TYPE=streamable_http uv run mcp-simple-auth-client
 ```
 
-
 ## How It Works
 
 ### RFC 9728 Discovery
 
 **Client → Resource Server:**
+
 ```bash
 curl http://localhost:8001/.well-known/oauth-protected-resource
 ```
+
 ```json
 {
   "resource": "http://localhost:8001",
@@ -64,9 +64,11 @@ curl http://localhost:8001/.well-known/oauth-protected-resource
 ```
 
 **Client → Authorization Server:**
+
 ```bash
 curl http://localhost:9000/.well-known/oauth-authorization-server
 ```
+
 ```json
 {
   "issuer": "http://localhost:9000",
@@ -75,7 +77,6 @@ curl http://localhost:9000/.well-known/oauth-authorization-server
 }
 ```
 
-
 ## Legacy MCP Server as Authorization Server (Backwards Compatibility)
 
 For backwards compatibility with older MCP implementations, a legacy server is provided that acts as an Authorization Server (following the old spec where MCP servers could optionally provide OAuth):
@@ -88,6 +89,7 @@ uv run mcp-simple-auth-legacy --port=8002
 ```
 
 **Differences from the new architecture:**
+
 - **MCP server acts as AS:** The MCP server itself provides OAuth endpoints (old spec behavior)
 - **No separate RS:** The server handles both authentication and MCP tools
 - **Local token validation:** Tokens are validated internally without introspection
@@ -103,6 +105,7 @@ MCP_SERVER_PORT=8002 MCP_TRANSPORT_TYPE=streamable_http uv run mcp-simple-auth-c
 ```
 
 The client will:
+
 1. Try RFC 9728 discovery at `/.well-known/oauth-protected-resource` (404 on legacy server)
 2. Fall back to direct OAuth discovery at `/.well-known/oauth-authorization-server`
 3. Complete authentication with the MCP server acting as its own AS
@@ -112,6 +115,7 @@ This ensures existing MCP servers (which could optionally act as Authorization S
 ## Manual Testing
 
 ### Test Discovery
+
 ```bash
 # Test Resource Server discovery endpoint (new architecture)
 curl -v http://localhost:8001/.well-known/oauth-protected-resource
@@ -121,6 +125,7 @@ curl -v http://localhost:9000/.well-known/oauth-authorization-server
 ```
 
 ### Test Token Introspection
+
 ```bash
 # After getting a token through OAuth flow:
 curl -X POST http://localhost:9000/introspect \

examples/servers/simple-streamablehttp-stateless/README.md

@@ -10,7 +10,6 @@ A stateless MCP server example demonstrating the StreamableHttp transport withou
 - Task lifecycle scoped to individual requests
 - Suitable for deployment in multi-node environments
 
-
 ## Usage
 
 Start the server:
@@ -35,7 +34,6 @@ The server exposes a tool named "start-notification-stream" that accepts three a
 - `count`: Number of notifications to send (e.g., 5)
 - `caller`: Identifier string for the caller
 
-
 ## Client
 
-You can connect to this server using an HTTP client. For now, only the TypeScript SDK has streamable HTTP client examples, or you can use [Inspector](https://github.com/modelcontextprotocol/inspector) for testing.
+You can connect to this server using an HTTP client. For now, only the TypeScript SDK has streamable HTTP client examples, or you can use [Inspector](https://github.com/modelcontextprotocol/inspector) for testing.

examples/servers/simple-streamablehttp/README.md

@@ -40,16 +40,14 @@ This server includes resumability support through the InMemoryEventStore. This e
 - Reconnect to the server after a disconnection
 - Resume event streaming from where they left off using the Last-Event-ID header
 
-
 The server will:
+
 - Generate unique event IDs for each SSE message
 - Store events in memory for later replay
 - Replay missed events when a client reconnects with a Last-Event-ID header
 
 Note: The InMemoryEventStore is designed for demonstration purposes only. For production use, consider implementing a persistent storage solution.
 
-
-
 ## Client
 
-You can connect to this server using an HTTP client, for now only Typescript SDK has streamable HTTP client examples or you can use [Inspector](https://github.com/modelcontextprotocol/inspector)
+You can connect to this server using an HTTP client, for now only Typescript SDK has streamable HTTP client examples or you can use [Inspector](https://github.com/modelcontextprotocol/inspector)