Skip to main content

​
Common Issues

Possible causes and solutions:
  • Verify you are using the correct server URL: https://mcp.feedspace.io/mcp
  • Make sure you have completed the OAuth sign-in flow in your browser when prompted
  • Try removing and re-adding the MCP server in your client settings
  • Check that your Feedspace account is active at app.feedspace.io
  • Clear your MCP client’s cached credentials and re-authenticate
Possible causes and solutions:
  • You must have at least one workspace in your Feedspace account
  • Sign in to app.feedspace.io and create a workspace if needed
  • Ensure you authenticated with the correct Feedspace account
  • If you were recently added to a workspace, the owner may need to verify your access
Possible causes and solutions:
  • Restart your MCP client (Claude Desktop, Cursor, etc.)
  • Verify the server URL in your client is exactly https://mcp.feedspace.io/mcp with no trailing slash or extra path
  • Ensure you are using Streamable HTTP as the transport type
Possible causes and solutions:
  • Your role in the workspace may not have sufficient permissions
  • Admins have full access; Editors can modify forms, pages, and widgets; Viewers have read-only access
  • Contact the workspace Admin to adjust your role
  • Use list_team_members to check your current role in the workspace
Possible causes and solutions:
  • Make sure you are passing the correct feed_identifier values (format: feed-{type}-item-{id})
  • Use get_feeds or filter_feeds to get the exact identifiers
  • Verify the reviews exist and belong to the correct workspace
  • Check that the reviews have not been soft-deleted
Possible causes and solutions:
  • If fetching large datasets, use pagination parameters (page, perPage) to limit results
  • For bulk operations on many reviews, use batch_update_feeds rather than individual calls
  • If the issue persists, try again after a few moments

​
Frequently Asked Questions

No. The Feedspace MCP server intentionally excludes all delete operations to prevent accidental data loss from AI assistants. To delete reviews, forms, widgets, or pages, use the Feedspace dashboard directly.The only “removal” operations available are unassign_labels (removes a label association, not the review itself) and unfavourite (removes the favourite flag).
Any client that supports the Model Context Protocol with Streamable HTTP transport. This includes:
  • Claude Desktop
  • Claude Code
  • Cursor
  • Windsurf
  • ChatGPT (via MCP plugins)
  • Any other MCP-compatible client
Yes. Authentication uses OAuth 2.1 with PKCE, the industry standard for secure authorization. Your Feedspace credentials are never shared with the AI assistant. The bearer token is scoped to your account and transmitted over HTTPS.
Yes. Each team member authenticates with their own Feedspace account. Their access level is determined by their role in the workspace (Admin, Editor, or Viewer).
You can revoke OAuth tokens from your Feedspace account settings. The MCP server will require re-authentication on the next use. Any active sessions will be terminated.
The MCP server works with your existing Feedspace account. Tool availability depends on your Feedspace plan features. There is no additional charge for MCP access.

​
Getting Help

Contact Support

Reach out to the Feedspace team for help with any issues.

Feedspace Dashboard

Sign in to manage your reviews, forms, and settings directly.