FeedbackPulse
com.feedbackpulsePublished by feedbackpulse.comOfficial publisherv1.0.0Updated Oct 26, 2026
Employee surveys, performance reviews, recognition, and team pulse for AI assistants.
Overview
Remote FeedbackPulse MCP endpoint that lets an AI assistant work with employee surveys, performance reviews, recognition and team pulse data.
- What you can do
- Connect an assistant to a FeedbackPulse workspace covering employee surveys, performance reviews, recognition and team pulse.
- No tool list is published, so the exact actions available are not documented here; expect the assistant to read and work with the survey, review and recognition data the account exposes.
- Access is authenticated per user through OAuth or a personal API token.
- When to use it
- Worth adding when you want an assistant to help with employee engagement, review or recognition work inside an existing FeedbackPulse account, for example drafting or summarizing survey and review material.
- Requirements
- A FeedbackPulse account and access to the remote endpoint at app.feedbackpulse.com over streamable HTTP. Authentication is required: OAuth is preferred for Claude Desktop and Claude.ai, or an Authorization header carrying a Bearer personal API token created in Settings > Integrations by an Admin.
Installation
In SourceWeft
- Open FeedbackPulse in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- 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/com.feedbackpulse%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.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"feedbackpulse": {
"type": "http",
"url": "https://app.feedbackpulse.com/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestSep 28, 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.