mcp-ps-store
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PSN_NPSSO | No | NPSSO cookie. An alternative to `psn-login`: if set, the server signs in by itself. | |
| PSN_MCP_HOST | No | Bind address for the HTTP transports. | 127.0.0.1 |
| PSN_MCP_PORT | No | Port for the HTTP transports. | 8000 |
| PSN_CACHE_TTL | No | How long PSN responses are reused, in seconds. | 600 |
| PSN_TOKENS_PATH | No | Where tokens are cached. | ~/.mcp-ps-store/tokens.json |
| PSN_STORE_LOCALE | No | Locale used in store.playstation.com links. | en-us |
| PSN_MCP_TRANSPORT | No | `stdio`, `streamable-http` or `sse`. | stdio |
| PSN_REQUEST_TIMEOUT | No | HTTP timeout for PSN requests, in seconds. | 30 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| psn_taste_profileA | One-shot digest of the account's gaming taste: totals, playtime habits, top games by hours, favourite franchises, platinums, games close to completion, games bounced off after a short try, and unplayed purchases. Start here for any recommendation request. |
| psn_libraryA | Filtered, sorted list of games on the account, joining playtime with trophy progress. Use it to answer questions like 'what did I play most in 2024', 'what have I nearly finished', 'what did I drop quickly'. Store page: https://store.playstation.com//concept/. |
| psn_game_trophiesA | Full trophy list for a single game with earned status, earn dates and rarity. Pass a title (fuzzy match against the account's games) or an exact np_communication_id. Useful for 'what's left to platinum' and for judging how deeply the user engaged with a game. |
| psn_owned_gamesA | Games the account has bought or claimed (including PS Plus monthly claims), with hours played where known. Check this before recommending anything so you do not suggest a game the user already owns, and to surface unplayed purchases. |
| psn_recently_playedB | The account's most recently launched games, newest first. |
| psn_refreshA | Drops the cached PSN responses so the next call re-reads live data. Use after the user has just played something. |
| psn_profileB | Online ID, PS Plus status, trophy level and lifetime trophy counts. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| recommend_games | Pulls the PSN taste profile and asks for personalised recommendations grounded in it. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Most tools are distinct, but psn_taste_profile, psn_library, and psn_owned_games overlap in what they surface: playtime habits, nearly-finished games, dropped games, and unplayed purchases are all claimed by more than one tool. The descriptions somewhat clarify their intents (digest vs. queryable list vs. ownership check), but an agent could easily pick the wrong one for a given user question.
All tools share a consistent psn_ prefix and snake_case convention, which makes them recognizable as a family. The primary deviation is that psn_refresh is verb-first while the rest are noun phrases (psn_library, psn_profile, psn_owned_games), but the overall pattern is still predictable.
Seven tools is a well-scoped set for a PSN account insights server. Each tool covers a meaningful slice of the domain—profile, library, owned games, recent activity, trophies, taste digest, and cache refresh—without feeling padded or redundant at the count level.
The core domain of account-level PSN data is well covered: profile, catalog, ownership, recency, trophies, and an aggregate taste digest are all present. Minor gaps exist, such as no direct store/game-details lookup or cross-game trophy comparison, but the set supports the stated recommendation and account-insight workflows without major dead ends.