BGG MCP provides access to the BoardGameGeek API through the Model Context Protocol, enabling retr…
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Average 3.7/5 across 10 of 10 tools scored. Lowest: 2.8/5.
Each tool has a clearly distinct purpose with no ambiguity. For example, bgg-collection retrieves a user's collection, bgg-details provides deep game information, bgg-hot shows trending games, and bgg-rules searches rules forums—all serve unique functions without overlap. The descriptions explicitly differentiate use cases, such as bgg-details for deep dives after basic results from other tools, ensuring agents can easily select the correct tool.
All tool names follow a consistent 'bgg-' prefix with descriptive suffixes in snake_case, such as bgg-collection, bgg-details, and bgg-hot. This pattern is uniform across all 10 tools, making them predictable and easy to parse. There are no deviations in naming conventions, which enhances readability and agent usability.
With 10 tools, the server is well-scoped for interacting with BoardGameGeek, covering key aspects like collections, details, search, recommendations, rules, and user interactions. Each tool earns its place by addressing a specific need in the domain, avoiding bloat while providing comprehensive functionality. This count is ideal for the server's purpose, similar to high-calibration examples.
The tool set offers strong coverage for the BoardGameGeek domain, including CRUD-like operations (e.g., querying collections, getting details, searching) and specialized functions (e.g., recommendations, price checks, trade finding). Minor gaps exist, such as no explicit tools for updating user data or managing forum posts, but core workflows are fully supported, and agents can work around these limitations without significant failures.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
