Skip to main content
Glama
brandikun

opencritic-mcp

by brandikun
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

opencritic-mcp

An MCP (Model Context Protocol) server that gives AI assistants access to OpenCritic game review scores via the official OpenCritic API on RapidAPI.

Search for games and retrieve aggregated critic scores, review tiers, and individual reviews — all without scraping. For full API endpoints and response specs, see the OpenCritic API Documentation.

Tools

Tool

Parameters

Description

search_game

query (string)

Search by game title — returns up to 10 matches with IDs

get_game

id (number), platform? (string)

Get critic score, % recommended, tier, developer, publisher, platforms, genres, loot boxes, and box art. Filter by platform (e.g. 'PC', 'PS5', 'Xbox').

get_game_reviews

id (number), platform? (string), limit? (number)

Get individual critic reviews (outlet, score, author, language, platform tags, excerpt, link). Filter by platform.

Related MCP server: IGDB MCP Server

Prerequisites

  • Node.js v18 or later

  • A free RapidAPI key for the OpenCritic API

Getting a RapidAPI key

  1. Go to rapidapi.com/opencritic/api/opencritic-api

  2. Sign up or log in (free)

  3. Subscribe to the Basic plan (free tier: 200 requests/day, 25 searches/day)

  4. Copy your X-RapidAPI-Key from the dashboard

Your key is only ever used locally. It is read from an environment variable at runtime and never stored in the package.

Installation

Option A — npx (no install required)

{
  "mcpServers": {
    "opencritic": {
      "command": "npx",
      "args": ["-y", "opencritic-mcp"],
      "env": {
        "RAPIDAPI_KEY": "your_rapidapi_key_here"
      }
    }
  }
}

Option B — Clone and build locally

git clone https://github.com/brandikun/opencritic-mcp.git
cd opencritic-mcp
npm install
npm run build

Then add to your MCP config:

{
  "mcpServers": {
    "opencritic": {
      "command": "node",
      "args": ["/absolute/path/to/opencritic-mcp/dist/index.js"],
      "env": {
        "RAPIDAPI_KEY": "your_rapidapi_key_here"
      }
    }
  }
}

MCP Client Config Locations

Client

Config file

Antigravity / AGY

~/.gemini/antigravity-cli/settings.json

Claude Desktop

~/Library/Application Support/Claude/claude_desktop_config.json (macOS)

Claude Desktop (Windows)

%APPDATA%\Claude\claude_desktop_config.json

Example usage

Once connected, you can ask your AI assistant things like:

  • "Search for Hollow Knight on OpenCritic"

  • "What's the critic score for Disco Elysium?"

  • "Show me the top critic reviews for Elden Ring"

  • "Cross-reference my Steam library with OpenCritic scores" (when paired with a Steam MCP)

Security notes

  • Your RAPIDAPI_KEY is passed via environment variable — it never appears in source code or gets committed to git

  • The server uses only Node's built-in fetch and the official MCP SDK — no third-party HTTP clients

  • If RAPIDAPI_KEY is missing, the server exits immediately with a clear error message

Free tier limits & Caching

Limit

Value

Requests per day

200

Searches per day

25

Requests per second

4

Built-in Caching: To protect your daily RapidAPI quota, responses are cached in memory for 1 hour. Repeated detail or review queries cost 0 API requests.

License

MIT

Available Tools

3 tools
get_gameA

Get full details and critic scores for a game by its OpenCritic ID. Includes critic score, % recommended, tier, developer, publisher, platforms, genres, loot box status, and box art. Optionally filter by platform name (e.g. 'PC', 'PS5', 'Xbox').

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe OpenCritic game ID (obtained from search_game)
platformNoOptional platform name to filter (e.g. 'PC', 'PS5', 'Xbox', 'Switch')

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden of behavioral disclosure. It transparently lists the included data fields and the optional platform filter, making clear what the tool returns. It does not mention error handling or response structure, but the safety profile (read-only) is implicitly evident.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences: first states the core function, second lists included fields and the optional filter. No filler, all information earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Although there is no output schema, the description enumerates the return content (critic score, developer, etc.), making the tool's output comprehensible. The optional platform filter adds contextual detail, but ambiguity remains about how filtering affects the response (e.g., whether it affects the platforms array).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description reinforces the optional platform filter with examples already present in the schema, but adds no new parameter semantics beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves full details and critic scores for a game by its OpenCritic ID, naming specific fields. This distinguishes it from siblings like search_game (searching) and get_game_reviews (reviews), which is evident from the context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage after obtaining an OpenCritic ID from search_game (via the schema's parameter description and the text 'by its OpenCritic ID'). It also clarifies when the optional platform filter applies, but does not explicitly mention when to use alternatives like get_game_reviews.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_game_reviewsA

Get individual critic reviews for a game by its OpenCritic ID. Returns reviews including outlet, score, author, language, platforms, excerpt, and a link to the full review. Optionally filter by platform name (e.g. 'PC', 'PS5').

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe OpenCritic game ID (obtained from search_game)
limitNoNumber of reviews to return (default: 10, max: 20)
platformNoOptional platform name to filter (e.g. 'PC', 'PS5', 'Xbox')

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden. It discloses what the tool returns (outlet, score, author, language, platforms, excerpt, link) and the optional platform filter. As a 'get' operation, it implies read-only behavior, but it does not explicitly state safety profile or error behavior. Still, for a simple retrieval, this is adequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loaded with the primary action and clearly structured. Every sentence adds value: the first states the core purpose and return fields, the second explains the optional filter. No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description lists the return fields. The schema covers parameters, defaults, and limits. The ID source is noted in the schema. For a simple read tool, the description together with schema provides sufficient context for an agent to use it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds the platform filter context and ID origin, but these are already present in the schema. No additional parameter semantics are provided beyond what the structured fields contain.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function with a specific verb and resource: 'Get individual critic reviews for a game by its OpenCritic ID.' It distinguishes itself from siblings (get_game, search_game) by focusing on reviews rather than general game info or search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the usage context (retrieve reviews for a known game ID) and the schema's id description explicitly says the ID comes from search_game. However, no explicit alternatives or exclusions are stated, though the purpose itself differentiates it from sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

search_gameA

Search for a game by name on OpenCritic. Returns up to 10 matches with their IDs, which can be passed to get_game or get_game_reviews.

ParametersJSON Schema
NameRequiredDescriptionDefault
queryYesThe game title to search for (e.g. 'Hollow Knight', 'Disco Elysium')

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must disclose behavior itself. It reveals that the search returns up to 10 matches with IDs, which is useful for understanding the output. It doesn't explain matching semantics, pagination, or error states, but the note about passing IDs to get_game/get_game_reviews offers practical behavioral context that goes beyond a bare search definition.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences long, with the function stated immediately. The second sentence provides essential output information without unnecessary elaboration. It is concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple with one parameter and no output schema, but the description conveys the essential context: the result format (up to 10 matches with IDs) and how to use those results with sibling tools. This makes it complete for an agent to know when to use it and what to expect, despite the absence of an output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already fully describes the only parameter 'query' with examples, so the schema coverage is 100%. The description adds no further parameter details beyond what's already in the schema. Therefore, no extra value is added from the description for parameter understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function: 'Search for a game by name on OpenCritic.' The verb 'search' and the resource 'game by name' make it distinct from sibling tools like get_game and get_game_reviews, which are presumably for fetching specific details or reviews once an ID is known.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use this tool: when you have a game title but need its OpenCritic ID. It explicitly states the IDs 'can be passed to get_game or get_game_reviews,' which guides the follow-up workflow. However, it doesn't explicitly say 'use this instead of X' or provide exclusion criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 3 tool updatesv1.0.1
    • First observedget_game
    • First observedget_game_reviews
    • First observedsearch_game
Deploy Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.5/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a distinct purpose: search_game finds games by name, get_game retrieves full details for a specific game, and get_game_reviews fetches individual critic reviews. There is no overlap in functionality, and the descriptions clearly indicate when to use each.

Naming Consistency5/5

All tool names follow the same verb_noun pattern with lowercase snake_case: get_game, search_game, get_game_reviews. The pattern is consistent and predictable, making it easy to guess the function of each tool.

Tool Count5/5

With only three tools, the server is well-scoped for its purpose of accessing OpenCritic data. Each tool covers a necessary step in the workflow (search, details, reviews), and no redundant or superfluous tools are present.

Completeness5/5

The toolset provides a complete read-only workflow: search to find a game, then retrieve either its full details or its individual reviews. There are no obvious gaps, and the filter options add flexibility for platform-specific queries.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • IGDB MCP Server

    bielacki
    A
    license
    B
    quality
    C
    maintenance
    Provides access to the Internet Game Database (IGDB) API, enabling users to search for video games, retrieve detailed game information including ratings and platforms, and discover trending and anticipated titles.
    4
    4
    MIT

  • Video Games MCP Server

    BaranDev
    A
    license
    Not graded
    quality
    D
    maintenance
    Provides direct access to the RAWG gaming database, allowing users to search for games, retrieve detailed metadata, and explore genres within Claude. It streamlines game research by offering information on ratings, platforms, and release dates through natural language queries.
    3
    MIT

  • Metacritic MCP Server

    MrCherry
    F
    license
    Not graded
    quality
    D
    maintenance
    Exposes Metacritic game, movie, TV, and music review data through MCP tools and resources, enabling LLM hosts to search and retrieve reviews with optional filters.
    1
    -