FeedBear
for LuumenAI
Read FeedBear boards for context, then post updates as approved steps
Connect FeedBear and Luumen can read your boards, items, comments, statuses, and changelog entries whenever it needs product context. When a request warrants a change — a status move, a public reply, a new item filed from an incident — Luumen shows the exact edit first and waits for your approval before it touches the board. Authentication is an API key.
The FeedBear toolbox
10 tools: 6 read, 4 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet Board ItemGet the full details of one feedback item from a FeedBear board.
- ReadList Board ItemsList or search feedback items on a FeedBear board, with optional status and sort filters.
- ReadList BoardsList boards in the connected FeedBear project, optionally including private team-only boards.
- ReadList Changelog EntriesList published FeedBear changelog entries newest first.
- ReadList Item CommentsList non-spam comments on a FeedBear item, newest first, including reply relationships.
- ReadList StatusesList the statuses configured for the connected FeedBear project.
- WriteAdd Item CommentPublish a public comment on a FeedBear item as the API key creator. Approval by default
- WriteCreate Board ItemCreate a feedback item on a FeedBear board without notifying users. Approval by default
- WriteDelete Board ItemPermanently delete a FeedBear board item, with explicit force confirmation available for items with merged posts. Approval by default
- WriteUpdate Board ItemUpdate selected fields of an existing FeedBear board item without notifying voters. Approval by default
One prompt, start to finish
What a governed FeedBear run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — add item comment, create board item, delete board item, update board item — is shown as a plan and requires approval by default, including the 1 action classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to FeedBear — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Put FeedBear to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.