v0.2.1: Add tests, retry logic, input validation, TimeoutError, README badges

Made-with: Cursor

Author: TMHSDigital

.gitignore

@@ -5,3 +5,14 @@ dist/
 !.env.example
 *.ssfn
 config.vdf
+
+# OS
+.DS_Store
+Thumbs.db
+
+# IDE
+.vscode/
+.idea/
+
+# Test coverage
+coverage/

CLAUDE.md

@@ -2,7 +2,7 @@
 
 ## What is this?
 
-An MCP (Model Context Protocol) server that exposes Steam Web API endpoints as structured tools for AI-powered IDEs. It is the companion server for the [Steam Developer Tools](https://github.com/TMHSDigital/Steam-Cursor-Plugin) Cursor plugin, which provides 14 skills and 3 rules for Steam/Steamworks development.
+An MCP (Model Context Protocol) server that exposes Steam Web API endpoints as structured tools for AI-powered IDEs. It is the companion server for the [Steam Developer Tools](https://github.com/TMHSDigital/Steam-Cursor-Plugin) Cursor plugin, which provides 14 skills and 4 rules for Steam/Steamworks development.
 
 The plugin's skills reference these MCP tools to fetch live data from Steam - player stats, store info, workshop items, leaderboards, and more.
 
@@ -24,7 +24,7 @@ src/
 **Key patterns:**
 
 - Each tool is a self-contained module that exports `register(server: McpServer)`.
-- `steam-api.ts` provides `steamFetch()` which handles timeouts (15s via AbortController), HTTP error detection (429 rate limits, 5xx unavailable), and JSON parsing.
+- `steam-api.ts` provides `steamFetch()` which handles timeouts (15s via AbortController with `TimeoutError`), HTTP error detection (429 rate limits with up to 2 retries and exponential backoff, 5xx unavailable), and JSON parsing.
 - `errorResponse()` formats errors as MCP-compatible `{ isError: true }` responses.
 - Tools that need an API key call `requireApiKey()` which reads `STEAM_API_KEY` from env and throws `MissingApiKeyError` with setup instructions if missing.
 - No-auth tools (getAppDetails, searchApps, getPlayerCount, getAchievementStats, getWorkshopItem) work without any configuration.
@@ -40,7 +40,16 @@ npm run dev       # tsx watch for development
 
 ## How to test
 
-Manual testing via MCP inspector or by configuring as an MCP server in Cursor:
+**Automated tests (vitest):**
+
+```bash
+npm test            # single run
+npm run test:watch  # watch mode
+```
+
+Tests cover error classes, `steamFetch` behavior (mocked fetch), retry logic, and Zod input validation for all 10 tools.
+
+**Manual testing** via MCP inspector or by configuring as an MCP server in Cursor:
 
 ```json
 {

README.md

@@ -1,5 +1,9 @@
 # Steam MCP Server
 
+[![npm](https://img.shields.io/npm/v/@tmhs/steam-mcp)](https://www.npmjs.com/package/@tmhs/steam-mcp)
+[![license](https://img.shields.io/npm/l/@tmhs/steam-mcp)](LICENSE)
+[![node](https://img.shields.io/node/v/@tmhs/steam-mcp)](package.json)
+
 MCP (Model Context Protocol) server for Steam and Steamworks APIs. Provides structured tools for querying Steam store data, player statistics, achievements, workshop items, leaderboards, and player profiles from AI-powered IDEs.
 
 Built as the companion MCP server for the [Steam Developer Tools](https://github.com/TMHSDigital/Steam-Cursor-Plugin) Cursor plugin.
@@ -143,6 +147,13 @@ These require `STEAM_API_KEY` to be set:
 | `IPublishedFileService/QueryFiles/v1` | API key |
 | `ISteamLeaderboards/GetLeaderboardEntries/v1` | Publisher key + IP allowlist |
 
+## Testing
+
+```bash
+npm test          # Run all tests (vitest)
+npm run test:watch  # Watch mode
+```
+
 ## Development
 
 ```bash