BGG MCP: BoardGameGeek MCP API Server

Created By
kkjdaniela year ago
BGG MCP provides access to the BoardGameGeek API through the Model Context Protocol, enabling retrieval and filtering of board game data, user collections, and profiles.
Overview

what is BGG MCP?

BGG MCP is an API server that provides access to the BoardGameGeek API through the Model Context Protocol, allowing users to retrieve and filter board game data, user collections, and profiles.

how to use BGG MCP?

To use BGG MCP, you can either install it via Smithery or manually set it up by installing Go, building the application, and configuring it in your AI tool.

key features of BGG MCP?

  • Access to detailed board game information
  • User collection retrieval and filtering
  • Current BGG hotness tracking
  • User profile details lookup

use cases of BGG MCP?

  1. Finding specific board games by name.
  2. Filtering and retrieving user collections.
  3. Tracking trending board games based on BGG hotness.
  4. Accessing user profiles for board game enthusiasts.

FAQ from BGG MCP?

  • Is BGG MCP easy to set up?

Yes! You can set it up easily using Smithery or follow the manual setup instructions provided.

  • What programming language is BGG MCP built with?

BGG MCP is implemented in Go.

  • Can I contribute to the development of BGG MCP?

Yes! The project is under active development, and contributions are welcome.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kkjdaniel
Star
3
Language
Go
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago