Echo MCP Server

- Echo any message back to the client
- Customizable message format through configuration
- Built on the Model Context Protocol standard

- .NET 9.0 (for local development/deployment)
- Docker (for container deployment)

To configure Claude Desktop to use a locally installed Echo server:

1. Add the server configuration to the mcpServers section in your Claude Desktop configuration:
``json
"echo": {
"command": "dotnet",
"args": [
"YOUR_PATH_TO_DLL\\Core.Infrastructure.McpServer.dll"
],
"env": {
"MessageFormat": "Claude says: {message}"
}
}
`

2. Save the file and restart Claude Desktop

To add the echo server to Claude Code, use the following command:

`bash
claude mcp add echo -- docker run -i --rm -e MessageFormat="Claude says: {message}" aadversteeg/echo-mcp-server:latest
`

You can customize the message format by modifying the MessageFormat environment variable.

To use a custom configuration file from your host system:

1. Create a custom configuration file on your host machine (e.g., echo-appsettings.json):
`json
{
"MessageFormat": "My Custom Format: {message}",
"Logging": {
"LogLevel": {
"Default": "Information",
"Microsoft": "Warning"
}
}
}
`

2. Update the Claude Desktop configuration to mount this file:
`json
"echo": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"-v", "C:/path/to/echo-appsettings.json:/app/appsettings.json",
"echo-mcp-server:latest"
]
}
`

Important Notes:
- The configuration file must exist on your host system before starting the container
- You can use any filename on the host (e.g., echo-appsettings.json), but it must be mounted to /app/appsettings.json` inside the container
- Make sure the path is correct for your operating system (Windows uses backslashes or forward slashes, Linux/macOS use forward slashes)
- After changing the configuration file, restart Claude Desktop to apply the changes

3. Save the file and restart Claude Desktop