Hosted MCP server/Productivity

feedback.tools MCP server

Hosted at feedback.tools·Streamable HTTP

feedback.tools brings customer feedback to an AI assistant, including CSAT, NPS, and CES scores, response search, and AI themes. OAuth authentication is required, and the server uses HTTP transport. The provider documents that Cursor and VS Code cannot connect yet because it does not support Dynamic Client Registration, so use a client that can complete the OAuth flow.

feedback.tools Streamable HTTP OAuth Server not checked yet Reviewed 2026-11-16
About

Where it fits

Support and product teams reviewing CSAT, NPS, and CES feedback with OAuth access and AI themes.

  • Review CSAT, NPS, and CES scores
  • Search customer feedback responses quickly
  • Identify AI-generated themes in feedback

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Connect from Claude or ChatGPT

The provider says Cursor and VS Code cannot connect yet because it does not support Dynamic Client Registration. Use Claude or another client that can complete the OAuth flow.

  1. Add the endpoint in a supported client

    Use Claude Code, Claude.ai or ChatGPT. Cursor and VS Code one-click installs are unsupported until the provider adds DCR.

  2. Complete OAuth

    Sign in and approve access in the browser.

Follow the provider's setup steps above, then connect the server in your client. The provider controls the endpoint, required credentials, and permissions.

Connection

Endpoint and configuration

Endpoint
https://feedback.tools/mcp
Host
feedback.tools · /mcp
Transport
Streamable HTTP
Authentication
OAuth
Server name
feedback-tools
Listing type
Community or directory listing

The installer uses the server name feedback-tools. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that feedback-tools appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Review CSAT, NPS, and CES scores. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • The sign-in window closes without returning. Allow pop-ups and finish the provider login in the same browser.
  • The server connects but its tools are missing. Remove it, add it again, and approve the scopes the provider lists.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

feedback.tools documentationhttps://feedback.tools/docs/mcp