MCP Untappd Server MCP Server

A Model Context Protocol server. That is what the mcp untappd server mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

This is a simple MCP server written in node to query the Untappd API. Unfortunately they are no longer accepting registrations for new API keys.

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

The tools it exposes

The server publishes 4 tools. What each one is for:

• search_beer — This will search Untappd for a beer
• get_beer_info — This get's the detailed beer info via the beer_id returned from a search
• get_user_checkins — currently does not work This will return a users checkin's
• Debugging — Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Untappd Server's toolset — search_beer, get_beer_info, get_user_checkins and 1 more — is a fair guide to whether it matches your workflow. It is maintained by jtucker; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.