Hosted MCP server/Productivity

FeedbackPulse Employee Surveys MCP server

Hosted at app.feedbackpulse.com·Streamable HTTP

FeedbackPulse Employee Surveys designs employee surveys with AI, including preview, prepare and save actions, through 19 documented tools. An Admin must enable MCP access for the organisation, and non-admin users need an Admin to grant access individually. Only Admins create personal API tokens, and only for their own account. Read tools need mcp:use; survey, template and draft creation need mcp:write and Admin. list_tokens and get_activity_log are Admin-only, and performance or recognition tools are plan-gated.

app.feedbackpulse.com Streamable HTTP Admin-enabled MCP access + personal API token (mcp:use; mcp:write for writes) Source checked Nov 12, 2026 Server responded when checked Reviewed 2026-11-16
About

Where it fits

HR teams that want to design and review employee surveys inside an AI assistant.

  • List my surveys with list_surveys (mcp:use).
  • Preview a survey before saving.
  • Create a survey draft (mcp:write, Admin).

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.

Setup

Install it in your client

Choose a client, run the command or use the one-click install, then verify the connection. The endpoint uses Streamable HTTP.

All client guides
  1. 01

    Run this command in your terminal

    This adds FeedbackPulse Employee Surveys as a remote Streamable HTTP server in Claude Code.

    Claude Code
    claude mcp add --transport http feedbackpulse-employee-surveys https://app.feedbackpulse.com/mcp/employee-surveys --header "Authorization: Bearer YOUR_FEEDBACKPULSE_TOKEN" --scope project
  2. 02

    Send the credential

    The provider expects the following header. Replace each placeholder with your own key or token before you connect.

    Required headers
    Authorization: Bearer YOUR_FEEDBACKPULSE_TOKEN
  3. 03

    Verify the connection

    Run claude mcp list, or open /mcp in a Claude Code session.

    Learn more about MCP in Claude Code

More clients, including project and global config files, are in the sidebar.

Connection

Endpoint and configuration

Endpoint
https://app.feedbackpulse.com/mcp/employee-surveys
Host
app.feedbackpulse.com · /mcp/employee-surveys
Transport
Streamable HTTP
Authentication
Admin-enabled MCP access + personal API token (mcp:use; mcp:write for writes)
Server name
feedbackpulse-employee-surveys
Listing type
Community or directory listing

The installer uses the server name feedbackpulse-employee-surveys. 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 feedbackpulse-employee-surveys appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: List my surveys with list_surveys (mcp:use). 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 responded when checked

We reached app.feedbackpulse.com when we checked. That only means the address answered; it does not prove the MCP connection, sign-in, or tools work. The provider page was available when we checked.

Provider page available on Nov 12, 2026. A response does not guarantee the server is safe or that sign-in and tools will work.

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.

  • Authentication returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
  • The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
  • 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.

FeedbackPulse Employee Surveys documentationhttps://feedbackpulse.com/help/integrations/mcp-overview/GitHub repositoryhttps://github.com/FeedbackPulseApp/employee-surveys-mcp