Troubleshoot FeedbackPulse MCP Connection

Use this page when an AI assistant cannot connect to FeedbackPulse, cannot authenticate, or returns permission and data-access errors. Find the exact error message below, then apply the listed fix steps in order.

”Your account does not have MCP access”

Cause: Your user account has not been granted MCP access by an Admin.

Solution:

1. Ask your Admin to go to Settings > Integrations
2. Find your name in the user list and toggle MCP Access on
3. Reconnect your AI assistant

Note

Admins always have MCP access automatically and cannot be toggled off. This error only applies to non-admin users.

”MCP access is not enabled for your organisation”

Cause: The AI Integrations feature has not been enabled for your organisation.

Solution:

1. Ask your Admin to go to Settings > Features
2. Enable the AI Integration toggle and save
3. Your Admin will also need to grant you access in Settings > Integrations, unless you are an Admin yourself (Admins have access automatically)

“Invalid or expired token” / 401 error

Cause: The API token used by your AI assistant has been revoked, or the token was entered incorrectly.

Solution:

1. Only Admins can view and manage tokens in Settings > Integrations. An Admin should check whether the token is still listed.
2. If it was revoked, an Admin should create a new token and share the update with you to put in your AI client configuration
3. For Claude Code, re-run the claude mcp add command with the new token
4. For OAuth connections (Claude Desktop, Claude.ai), disconnect and reconnect to trigger a new authorization

OAuth authorization fails or loops back to the login page

Cause: A browser cookie or session conflict, or the authorization was denied partway through.

Solution:

1. Clear your browser cookies and try again
2. Make sure you are signed in to the correct FeedbackPulse account before starting the OAuth flow
3. Complete the authorization in a single browser session. Do not switch tabs or accounts mid-flow.
4. If the problem persists, disconnect the FeedbackPulse integration in your AI assistant and reconnect from scratch
5. If it still fails, contact support with the exact error text and which AI client you are using

”You don’t have permission to view this”

Cause: Your FeedbackPulse role does not allow access to the requested data. For example, Managers can see review and employee data for their direct and indirect reports, but Managers have no access to survey results or recognition data through MCP at all, even for their own reports.

Rule: MCP access follows the same permissions as the web application. It does not grant additional access.

Solution:

1. Confirm which role your account has in Settings > Team Members
2. If you are a Manager asking about survey or recognition data, this is expected: Managers cannot access these through MCP, and an Admin will need to help instead
3. Ask your Admin if you need access to additional data
4. Admins have the broadest access and can see all organisation data via MCP

Survey results show no text responses

Cause: The survey is configured as anonymous and the number of responses is below the privacy threshold. Individual text responses are intentionally withheld to protect respondent anonymity.

Rule: This is expected behaviour and cannot be bypassed. It applies in the web application as well as via MCP.

Workaround: Ask your AI assistant to retrieve the AI-generated survey summary instead:

“Get the AI summary for survey [name]”

The summary surfaces themes and patterns without revealing individual responses.

”Survey not found” for a valid survey ID

Cause: The survey belongs to a different organisation, or the survey has been deleted.

Solution:

1. Use the list_surveys tool to retrieve current survey IDs. Do not hardcode IDs from previous sessions.
2. Confirm the survey has not been deleted in Surveys
3. If you are testing across multiple accounts, ensure you are authenticated as the correct user

”This action requires the mcp:write scope” / 403 error

Cause: You asked your AI assistant to create or update a survey template, or create a survey draft, but your current connection doesn’t include the mcp:write scope. This happens whenever you’re connected over OAuth (Claude Desktop, Claude.ai), since those connections always use mcp:use only and never include mcp:write.

Solution:

1. Confirm you are an Admin. Only Admins can create or update survey templates and drafts, regardless of scope.
2. If you’re connected over OAuth, switch to a personal API token instead: an Admin creates one in Settings > Integrations and connects it through a token-based client such as Claude Code. There is no scope selector to configure; a token created by an Admin automatically includes both mcp:use and mcp:write.
3. Update your AI client configuration with the new token (for Claude Code, re-run the claude mcp add command)

Note

Only Admins can create survey templates and drafts. If you are not an Admin, this action is not available to you regardless of connection type.

Note

OAuth connections (Claude Desktop, Claude.ai) always use mcp:use. Template and draft management via these clients is not supported; use a personal API token instead.

”Rate limit exceeded” / 429 error

Cause: Your AI client sent too many requests to the MCP server in a short period.

Solution:

1. Wait briefly, then retry
2. If this happens frequently, reduce the frequency of automated or scheduled queries
3. If the issue continues, contact support and include the time of the error and the client you used

The AI assistant cannot find FeedbackPulse tools

Cause: The MCP server was not registered correctly, or the connection was lost.

Solution:

1. Verify the server URL is exactly https://app.feedbackpulse.com/mcp
2. For Claude Code, run claude mcp list to confirm the server is registered
3. For Claude Desktop and Claude.ai, check Settings > Connections or Integrations to confirm the FeedbackPulse server is listed and shows as connected
4. If missing, follow the setup steps again: Claude Desktop, Claude.ai, Claude Code

Still need help?

If your issue is not listed here, contact our support team with a description of the error message and the AI client you are using.