Untappd MCP

What untappd-mcp MCP server does

The untappd-mcp MCP server gives an MCP client access to Untappd through the mobile application’s v4 API. It can search for beers, breweries, and venues; retrieve beer, venue, user, check-in, badge, friendship, wishlist, and activity information; and inspect notifications, trending results, and local check-ins.

Write tools cover posting check-ins, toasts, and comments, changing wishlists, deleting comments or check-ins, and adding, accepting, rejecting, or removing friends. Every write is subject to a confirmation flow before the request is sent.

The server also includes a local check-in cache. It can synchronize a user’s distinct beers or detailed check-ins, then answer questions about beers the user has had, has not had, or should consider from a supplied list without making another Untappd API request.

How it works

Authentication follows Untappd’s mobile xauth flow when a username and password are supplied. The resulting token is cached in memory and refreshed when needed. An existing access token can be provided instead, which skips login and can support read operations without the mobile client credentials.

Read and write requests send the token in an HTTP Bearer authorization header. Writes also use the mobile client credentials in the query string. The implementation is unofficial and uses Untappd’s private mobile API, so it is not affiliated with or endorsed by Untappd.

Cache synchronization is resumable. Each call processes a bounded number of pages, saves progress after each page, and reports whether another run is needed. The distinct-beers synchronization is intended for broad “has had” coverage, while check-in synchronization provides detailed venue, date, and comment data. Other users’ check-in history may be limited to recent results by Untappd.

Setup and configuration

For local use, copy .env.example to .env. Configure either UNTAPPD_ACCESS_TOKEN or UNTAPPD_USERNAME and UNTAPPD_PASSWORD. Login and write operations also require UNTAPPD_CLIENT_ID and UNTAPPD_CLIENT_SECRET; these values are obtained from the mobile app’s xauth request and should be kept private.

Optional settings control the device identifier, API version, user agent, timezone, photo directory, and SQLite cache path. UNTAPPD_TIMEZONE is useful when the server runs in a different timezone from the person making a check-in. Photo attachments are restricted to configured directories.

Confirmation behavior can be adjusted with MCP_CONFIRM_MODE, MCP_CONFIRM_ELICITATION, MCP_CONFIRM_TTL_SECONDS, and MCP_CONFIRM_SECRET. A client without an interactive confirmation prompt receives a preview and one-time token before a write is performed.

Tools and capabilities

The untappd-mcp MCP server exposes read tools such as untappd_search_beer, untappd_beer_info, untappd_search_brewery, untappd_search_venue, untappd_user_checkins, untappd_user_wishlist, untappd_activity_feed, and untappd_notifications.

Cache tools include untappd_sync_user_beers, untappd_sync_checkins, untappd_cache_has_had, untappd_cache_has_had_many, untappd_cache_not_had, untappd_cache_query, and untappd_top_not_had. Write tools include untappd_checkin, untappd_toast, untappd_add_comment, wishlist actions, and friendship actions.

Limitations and notes

The service depends on an unofficial private API and Untappd’s rate and pagination behavior. Full check-in backfills are available for the authenticated user, but check-in history for other accounts may be truncated. The SQLite cache is local; its default path and permission protections apply to local or stdio use. Write confirmations reduce accidental changes but should still be reviewed before approval.