Feedback

ai.b77Published by b77.aiOfficial publisherv1.0.0Updated Oct 30, 2026

Capture feature requests and bug reports from chat into a searchable, AI-categorized backlog.

The publisher's own server: feedback.tools

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Remote MCP server that lets an assistant capture feature requests and bug reports from chat into a searchable, AI-categorized backlog.

What you can do
  • Capture feature requests and bug reports raised in a conversation and file them into a backlog.
  • Search that backlog to find existing items, presumably before adding duplicates.
  • Rely on AI categorization of incoming items so the backlog stays organized.
  • No tool list is published, so the exact operations available are not documented.
When to use it
Useful when a team discusses product ideas or defects in chat and wants them turned into tracked backlog items without leaving the conversation, or when an assistant should check whether a request already exists before filing it.
Requirements
A remote endpoint at feedback.b77.ai over streamable HTTP; OAuth authentication is required. No environment variables or headers are declared.
Before you install
The server writes into a shared backlog, so items an assistant files become visible to others and may be hard to remove. It requires OAuth sign-in to a third-party service, and the content of captured requests and reports is sent to that service for storage and AI categorization.

Installation

In SourceWeft

  1. Open Feedback in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.b77%2Ffeedback/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "feedback": {
      "type": "http",
      "url": "https://feedback.b77.ai/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Feedback integrations