Chess MCP Server
by bkoseda
README.md
To run the MCP server using the provided configuration, follow these steps:
1. **Install prerequisites**
Ensure you have [uvx](https://github.com/your-uvx-link) installed on your system.
2. **Clone and start the server**
The configuration below will start the MCP server from a GitHub repository using `uvx`.
The command pulls the server code and launches the `mcp-server` entry point.
```json
{
"mcpServers": {
"GithubHostedExample": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/bkoseda/mcpchesssampleserver.git",
"chess"
]
}
}
}
```
3. **Run the server**
Execute the following command in your terminal:
```sh
uvx --from git+https://github.com/bkoseda/mcpserverexample.git mcp-server
```
This will download the MCP server from the specified GitHub repository and start it locally.
Refer to the repository's documentation for additional configuration or usage details.TDQS
A3.5/5.0
Scored across 2 tools
Disambiguation5/5
The two tools have clearly distinct purposes: one retrieves a player's public profile, the other retrieves their stats. There is no overlap or ambiguity.
Naming Consistency5/5
Both tools follow the exact same pattern: get_chess_player_ followed by a specific noun (profile, stats). This is consistent and predictable.
Tool Count3/5
With only two tools, the server feels thin. While they cover a focused player-info domain, the broader chess context suggests more tools could be expected, making the count borderline.
Completeness3/5
The tools cover the main player profile and stats endpoints, but the server is named 'Chess MCP Server,' implying a wider scope. Missing tools for games, tournaments, or other chess data create notable gaps.
Maintenance
ActivityInactive
ResponsivenessNo issues