BrewForge Docs

Tools: Community

Alle Tools des Toolsets community im BrewForge-MCP-Server und in der Actions-API, mit Zugriff, Berechtigung, Tariffunktion und Parametern.

Community, Rezepte teilen, Feedback, Support-Tickets, Posteingang und Changelog. Jedes Tool hier ist ein MCP-Tool auf https://brewforge.sh/api/mcp?toolsets=community und eine Action unter POST /api/v1/actions/<name>. Die Seite wird aus der API selbst erzeugt; Namen, Beschreibungen und Parameter sind deshalb auf Englisch. Wie du sie liest, steht in der Tool-Referenz.

browse_community

Browse the community feed or discover brewers

lesenBerechtigung: community:readAPI-Referenz

The BrewForge community. Without query/style: the feed of what the brewers the user follows brewed, packaged and shared (last 30 days, days for more), plus a few suggested brewers. With query and/or style (or view: "discover"): search other brewers' shared recipes by beer name, style or brewer name/handle (e.g. query "hopfenhans" or style "German Pilsner"), with suggested brewers. Use handles from the result with get_brewer_profile / interact_with_brewer, brew_id with cheer_brew, share_token with adopt_shared_recipe. Only brewers with an open profile appear.

Prop

Type

get_brewer_profile

Get a brewer's community profile

lesenBerechtigung: community:readAPI-Referenz

A brewer's community profile: bio, follower counts, whether the user follows them, the recipes they shared (share_token for adopt_shared_recipe) and their recent activity. Example: { "brewer": "hopfenhans" }. Without brewer: the user's OWN community profile with its settings (handle, visibility, bio, activity options; change them with update_community_profile), followers / following / blocked lists and recent community notices (follows, cheers, copies brewed).

Prop

Type

interact_with_brewer

Follow, unfollow, block or report a brewer

schreibenBerechtigung: community:writewiederholbarAPI-Referenz

Change the user's relation to another brewer: follow, unfollow, block (ends follows both ways), unblock, remove_follower (they stop following the user), or report (to the BrewForge team). Example: { "brewer": "hopfenhans", "action": "follow" }. Following needs the brewer's profile to be open. Reporting sends the user's complaint to the team: confirm the reason and wording with the user first and never report on your own initiative. Repeating follow/unfollow/block/unblock is harmless.

Prop

Type

cheer_brew

Cheer another brewer's beer

schreibenBerechtigung: community:writewiederholbarAPI-Referenz

Give (or take back) a Cheers on another brewer's beer, like the 🍻 button in the community feed. Example: { "brew_id": "<brew_id from browse_community>" }. brew_id comes from browse_community entries/recipes or get_brewer_profile. Pass cheered: false to take a Cheers back. Calling twice with the same value changes nothing.

Prop

Type

update_community_profile

Update the community profile and shared recipes

schreibenBerechtigung: community:writewiederholbarAPI-Referenz

Change the user's community profile: handle, who can see it (visibility), bio, location, brewing since, brewhouse, which activity is shown, notifications; list recipes on the profile (list_brews: other brewers can see and copy them) or take them off (unlist_brews), and hide single activity entries. Only the fields you pass change. Example: { "visibility": "members", "bio": "Lager nerd from Franconia", "list_brews": ["#12"] }. Making the profile or a recipe visible is public-facing: do it only when the user asked. Listing needs a visible profile (visibility members or public). Read the current settings with get_brewer_profile (no brewer).

Prop

Type

adopt_shared_recipe

Copy a shared recipe into the user's brews

schreibenBerechtigung: brews:writeAPI-Referenz

Save a recipe another brewer shared (share link or share_token from browse_community / get_brewer_profile) as a new brew idea in the user's own recipe book, like "Save to my recipes" on the share page. Example: { "share": "https://brewforge.sh/share/3f9a1c2b4d5e6f70" } or { "share": "3f9a1c2b4d5e6f70" }. Counts against the plan's brew limit. Returns the new brew's id; continue with the brewing tools (e.g. get_brew).

Prop

Type

find_feedback_threads

Find feedback threads (feature requests, questions, roadmap)

lesenBerechtigung: community:readAPI-Referenz

Search BrewForge's public Feedback board (brewforge.sh/feedback): feature requests and questions from all brewers, with votes and status. With query: the threads most similar to the text (full-text, finds rewordings), e.g. { "query": "water chemistry per mash step" }. ALWAYS search like this before post_feedback to avoid duplicates; results are the closest threads, not necessarily the same request, so compare titles (and read a thread when unsure). roadmap: true lists the feature requests on the roadmap (under_review, planned, in_progress, shipped); for what is coming next add status: ["planned", "in_progress"]. mine: "voted" / "commented" lists the user's own. Then get_feedback_thread for the full thread, react_to_feedback to vote.

Prop

Type

get_feedback_thread

Read a feedback thread

lesenBerechtigung: community:readAPI-Referenz

One Feedback thread with its status, votes, the original post, replies (10 per page, newest last), the team's summary and brief, open questionnaires and what the user may do (vote, reply). Example: { "thread": 33 }. Long posts are cut; pass full_post_id to get one post in full. Use the post ids with react_to_feedback / edit_feedback_post / delete_feedback_post, and questionnaire ids with answer_feedback_questionnaire.

Prop

Type

post_feedback

Post a feature request, question or reply in Feedback

schreibenBerechtigung: community:writeAPI-Referenz

Write in BrewForge's public Feedback board under the user's public username. PUBLIC: show the user the exact title and text and get their OK before calling; never post on your own initiative. New thread: category ("feature" or "question"), title and body. The tool first checks for similar existing threads: when it finds some it does NOT post and returns them, so you can vote there instead (react_to_feedback) or call again with skip_duplicate_check: true if the user still wants a new thread. Reply: pass thread (number) and body, e.g. { "thread": 33, "body": "+1, I need this for decoction mashes." }. Posting limits: accounts younger than 7 days cannot post; free plan 3 threads / 10 replies per month, paid plans 3 threads / 30 replies per day.

Prop

Type

edit_feedback_post

Edit the user's own Feedback post

schreibenBerechtigung: community:writewiederholbarAPI-Referenz

Change the text of one of the user's own posts in Feedback (a thread's original post or a reply). Thread titles are curated by the team once a thread is published; only a held thread's title can still change. Get post ids from get_feedback_thread (original_post.id, replies[].id where yours is true). Example: { "post_id": "abc123", "body": "Updated: also for step mashes." }. PUBLIC: confirm the new text with the user first. The edit is checked like a new post and may wait for review before it shows.

Prop

Type

delete_feedback_post

Delete the user's own Feedback post

löschendBerechtigung: community:writeAPI-Referenz

Delete one of the user's own Feedback posts (a reply, or the original post of their thread). It then shows as "deleted by the author"; votes and other replies stay. Without confirm: true it only shows which post would be deleted. Only when the user asked for it.

Braucht confirm: true; ohne ändert sich nichts und die Antwort zeigt, was entfernt würde.

Prop

Type

react_to_feedback

Vote, follow, accept an answer or report in Feedback

schreibenBerechtigung: community:writewiederholbarAPI-Referenz

Everything except writing posts, in one call: upvote a feature request ({ "thread": 33, "vote": true }; false removes the vote), follow a thread for notifications (subscribe), vote on a reply (reply_id + reply_vote 1 / -1 / 0), mark a reply as the accepted answer of the user's own question (accept_answer_post_id), suggest that the thread duplicates another (duplicate_of), or report a post to the moderators (report_post_id + report_reason). Pass only what you want to change. Voting on feature requests needs a paid plan (Basic+). Reports and duplicate suggestions go to the team: only when the user asked.

Prop

Type

answer_feedback_questionnaire

Answer a feedback questionnaire

schreibenBerechtigung: community:writewiederholbarAPI-Referenz

Submit (or change) the user's answers to the open questionnaire of a feature request, which the BrewForge team uses to decide how to build it. First read the questions and option ids with get_feedback_thread (questionnaires[]), ask the user, then pass one answer per question. Example: { "thread": 33, "answers": [{ "question_id": "q1", "option_ids": ["per-step"] }, { "question_id": "q2", "option_ids": [], "other": "only for decoction" }] }. Every question needs an answer; single-choice questions take exactly one option (or other). The result shows the totals so far.

Prop

Type

contact_support

Report a problem to support, or reply on a ticket

schreibenBerechtigung: community:writeAPI-Referenz

Support tickets are for bugs: something in BrewForge is broken or wrong. Feature wishes go to Feedback (post_feedback), questions on how to use BrewForge too. New bug report: title, details, severity, e.g. { "title": "Brew day timer stops when the phone locks", "details": "Steps: ...", "severity": "medium" }. Reply on an existing ticket: ticket + message, e.g. { "ticket": 412, "message": "It happens on Android too." }. The BrewForge team reads every ticket and answers in the inbox (get_inbox). Confirm the text with the user before sending. Limit: 5 reports per hour, 10 per day. Screenshots can't be attached here; the user can add them in the app.

Prop

Type

get_inbox

Inbox: support tickets, team messages and notifications

lesenBerechtigung: community:readAPI-Referenz

The user's inbox: how many things need attention, their support tickets (open by default) with unread team replies, messages from the BrewForge team, Feedback notifications (replies and status changes on followed threads) and community notices (new followers, cheers). Answers "did support answer my ticket?". With ticket (e.g. { "ticket": 412 }): that ticket with the whole conversation. Reading does not mark anything as read; use mark_inbox_read for that, and contact_support to reply on a ticket.

Prop

Type

mark_inbox_read

Mark inbox items as read or archive messages

schreibenBerechtigung: community:writewiederholbarAPI-Referenz

Mark things in the user's inbox as read, like opening them in the app: team messages (by id, or all), a ticket's replies, Feedback notifications (by id, or all) and community notices; archive team messages. Pass only what to change. Example: { "ticket": 412, "all_feedback_notifications": true }. Ids come from get_inbox. Only do this when the user has seen the items or asked for it.

Prop

Type

get_changelog

What's new in BrewForge

lesenBerechtigung: community:readAPI-Referenz

BrewForge's changelog: new features and bug fixes, newest first. Answers "what's new in BrewForge this month?" ({ "since": "2026-11-01" }) or "was the timer bug fixed?" ({ "query": "timer" }). Entries are one-line English descriptions with a date.

Prop

Type

get_account_overview

Plan, limits, bounty points and referrals

lesenBerechtigung: community:readAPI-Referenz

The user's BrewForge plan (name; renews_on or ends_on for a paid subscription, else period_note says why there is no date), brew limit and usage, which plan features are on, the bounty point balance (points from bug reports, codes and referrals, worth discounts) and the referral link with its stats. Read only: plan changes, checkout and discounts happen in the app (brewforge.sh/subscriptions, /bounty). include: ["bounty_history"] adds the last point transactions.

Prop

Type

redeem_bounty_code

Redeem a bounty code

schreibenBerechtigung: community:writeAPI-Referenz

Redeem a printed or emailed BrewForge bounty code (e.g. from a beer festival card) for bounty points. Example: { "code": "K7MX9PQR" }. Each code works once per user. Returns the points gained and the new balance; spending points on a discount happens in the app (/bounty).

Prop

Type

export_my_data

Export the user's account data (JSON)

lesenBerechtigung: readAPI-Referenz

The full data export of the account (the same JSON as Settings → Account → Export data), in pieces because it can be several MB. Without section: the export's sections with how many records each holds. Then ask for one section at a time, e.g. { "section": "profiles" }; list sections (brews, messages, bjcpEvaluations, ...) come in pages: { "section": "brews", "limit": 5, "cursor": "..." }. Raw records with internal field names; for working with brews prefer the brewing tools. Use this for backups or when the user asks for their data. Needs a token with the full "read" scope.

Prop

Type

Auf dieser Seite