retroachievements-mcp
The RetroAchievements MCP server exposes the RetroAchievements public API to MCP-compatible clients (like Claude Desktop, Claude Code, and Cursor), letting you query retro gaming achievement data conversationally.
Setup & Configuration
Check credential status and server setup (
ra_status)Save and validate a RetroAchievements username + Web API key for persistent access (
ra_save_credentials)Scaffold a local credentials file (
ra_prepare_credentials_file)
User Data
Profile & summary: Points, rank, motto, avatar, recent games/achievements, last activity, and award counts
Recent achievements: Achievements unlocked in the last N minutes
Recently played games: Games touched most recently with timestamps and per-game progress
Completion progress: All started games with completion %, hardcore status, and award level
User awards: Mastery, beaten, and event awards with dates
Date-range achievements: All achievements unlocked between two dates — great for weekly/monthly recaps
Game Data
Basic metadata: Title, console, developer, publisher, genre, release date, and box art
Extended info: Full achievement list with IDs, titles, descriptions, points, badges, unlock counts, and community ratings
Game + user progress combo: Game info alongside a specific user's unlock state in one call
Unlock distribution: Achievement unlock histograms and per-game leaderboard entries
Recent game awards: Latest masteries, completions, or beaten awards for a game
Console & Site-Wide Data
List all console IDs and browse all games for a given console (optionally filtered to sets with achievements)
Achievement of the Week with its unlock leaderboard
Site-wide top-ten ranked users by hardcore points
Which users unlocked a specific achievement, with timestamps
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@retroachievements-mcpShow me my recent achievements."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
retroachievements-mcp
A Model Context Protocol server that exposes the RetroAchievements public API to MCP-compatible clients like Claude Code, Claude Desktop, and Cursor.
Built on top of the official @retroachievements/api
TypeScript SDK.
What you can do with it
"What achievements did I unlock in the last hour?"
"Summarize my RetroAchievements activity this month."
"Show me the achievement list for Super Mario 64."
"Who are the top-ten ranked players right now?"
"How rare is each achievement in The Legend of Zelda: A Link to the Past?"
Related MCP server: MCP Chess Server
Requirements
Node.js 18+
A RetroAchievements account and Web API key (Settings → Keys)
Install
git clone https://github.com/Zach-Houston/retroachievements-mcp.git
cd retroachievements-mcp
npm install
npm run buildFirst-time setup
You have three ways to get the server credentials in place. Pick whichever fits.
Just start asking your MCP client questions like "Show me my RetroAchievements profile." The first call will fail with a structured "credentials not configured" message that gives the assistant two choices to offer you.
1A. In-chat paste (fastest)
You paste your username and Web API key into the chat. The assistant calls
ra_save_credentials, which validates the key against the live API and saves
it. Downside: the key is in your chat transcript.
1B. Edit a file the assistant scaffolds (key never touches chat)
The assistant calls ra_prepare_credentials_file, which writes a placeholder
credentials.env in your user config dir and returns a file:// link. You
click the link, paste your key in the file, save. The server picks it up on
the next tool call. Upside: key never appears in the transcript.
Either way, credentials end up at:
Windows:
%APPDATA%\retroachievements-mcp\credentials.envmacOS:
~/Library/Application Support/retroachievements-mcp/credentials.envLinux:
$XDG_CONFIG_HOME/retroachievements-mcp/credentials.env
The assistant can call ra_status at any time to see whether setup is done,
half-done (placeholder file waiting for a key), or not started.
2. Interactive CLI
npm run setupWalks you through getting an account (if needed), prompts for your Web API key, verifies against the API, and saves to the same user config dir.
3. Env vars in your MCP client config
Set RA_USERNAME and RA_API_KEY as env entries in your MCP client's server
config (see Use with Claude Code). The server reads
env vars first, then falls back to the stored file. Env vars never touch the
chat history.
Configure
The server reads two environment variables at startup:
Variable | Value |
| Your RetroAchievements username. |
| Your Web API key (find it at https://retroachievements.org/controlpanel.php). |
Pass the values as env entries in your MCP client config (see below) — those
take precedence over the stored credentials file.
If you launch the server without env vars set and no stored credentials, it
will still start and respond to MCP clients — but every tool call returns a
friendly error pointing the assistant at ra_save_credentials /
ra_prepare_credentials_file. A missing key never silently bricks the
connection.
Use with Claude Code
Add this to your Claude Code MCP config (~/.claude.json or via claude mcp add):
{
"mcpServers": {
"retroachievements": {
"command": "node",
"args": ["C:/Users/Z/projects/retroachievements-mcp/dist/index.js"],
"env": {
"RA_USERNAME": "YourUserName",
"RA_API_KEY": "your-web-api-key"
}
}
}
}Or, after npm link, you can use the retroachievements-mcp binary directly.
Use with Claude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"retroachievements": {
"command": "node",
"args": ["C:/Users/Z/projects/retroachievements-mcp/dist/index.js"],
"env": {
"RA_USERNAME": "YourUserName",
"RA_API_KEY": "your-web-api-key"
}
}
}
}Tools
Setup
Tool | Description |
| Reports configured / source (env, file, file-pending, none) / username / file path. |
| In-chat flow: validates a username + key the user typed, then writes them to the user config. |
| Out-of-chat flow: writes a placeholder file the user opens locally, pastes their key, and saves. |
User
Tool | Description |
| Basic profile (points, rank, motto, avatar). |
| Profile + recent games + recent achievements + awards. |
| Lightweight: just the user's hardcore + softcore point totals. |
| Achievements unlocked in the last N minutes. |
| Recently played games with progress. |
| All started games with completion %, hardcore status, award level. |
| Per-game progress for an arbitrary list of game IDs (bulk lookup). |
| Site awards earned (mastery, beaten, events). |
| The user's want-to-play wishlist. |
| Games the user has fully mastered (softcore and/or hardcore). |
| Achievements earned between two ISO dates. |
| Achievements earned on a single calendar day. |
| Game info + the user's per-game unlock state (one call instead of two). |
| Accounts the credentialed user follows. |
| Accounts following the credentialed user. |
Game
Tool | Description |
| Basic game metadata (title, console, developer, box art). |
| Full game info with the achievement list and unlock counts. |
| High-score holders OR latest masters for a game (pick via |
| Community star rating + number of votes. |
| Histogram: how many players have unlocked N achievements in this game. |
Console
Tool | Description |
| All consoles RA tracks. Use to translate names like "SNES" to a consoleId. |
| All games on a console, optionally filtered to those with achievement sets. |
Achievement
Tool | Description |
| Users who have unlocked a specific achievement, with timestamps and totals. |
Leaderboard
Tool | Description |
| Top entries for a leaderboard. |
| All leaderboards a user has placed on for a given game. |
Feed
Tool | Description |
| Currently featured achievement-of-the-week + leaderboard. |
| Site's top-ten ranked users by hardcore points. |
| Site-wide recent masteries / completions / beaten awards, filterable by kind. |
More are easy to add (comments, tickets, claims, hashes, game progression
list, set requests, per-user game rank) — see src/tools/ for the pattern.
Develop
npm run dev # tsx, no build step
npm run build # compile to dist/
npm start # run the compiled serverLicense
MIT
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Zach-Houston/retroachievements-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server