Feedback1

ai.feedback1Published by feedback1.aiOfficial publisherv1.1.0Updated Oct 24, 2026

Collect feedback and manage the product roadmap from AI agents.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Feedback1 is a remote MCP server that lets an AI assistant collect product feedback and manage a product roadmap.

What you can do
Collect feedback from AI agents into Feedback1, presumably as feedback items tied to a product or workspace. Manage the product roadmap from the assistant, so roadmap items can be handled in the same place as the feedback. The manifest lists no individual tools, so the exact operations are not documented here; the description only covers feedback collection and roadmap management.
When to use it
Useful when a team keeps product feedback and roadmap planning in Feedback1 and wants an assistant to capture feedback or work with roadmap items without leaving the conversation.
Requirements
A remote server reached at the provider's hosted endpoint over streamable HTTP. OAuth authentication is required, so the user needs a Feedback1 account and must complete the OAuth sign-in flow. No environment variables or headers are declared.
Before you install
The assistant can write feedback and change roadmap data in the connected Feedback1 account, so review what it records or edits. Access is granted through OAuth to the account's data; grant it only to assistants you trust and revoke access when no longer needed.

Installation

In SourceWeft

  1. Open Feedback1 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.feedback1%2Fmcp/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": {
    "feedback1": {
      "type": "http",
      "url": "https://app.feedback1.ai/api/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.1.0LatestSep 16, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.