home / mcp / feedbackbasket mcp server
mcp server to get feedback reports from feedbackbasket.com
Configuration
View docs{
"mcpServers": {
"deifos-feedbackbasket-mcp": {
"command": "npx",
"args": [
"-y",
"@feedbackbasket/mcp-server@latest",
"--api-key",
"fb_key_your_api_key_here"
],
"env": {
"FEEDBACKBASKET_API_KEY": "fb_key_your_api_key_here"
}
}
}
}You can interact with your FeedbackBasket data through an MCP server that lets AI assistants query projects, fetch feedback and bug reports, search content, and see rich statistics. This server keeps read-only access with project-level controls, so you can safely power intelligent assistants without risking data modifications.
Use an MCP client to connect to the FeedbackBasket MCP server. After you configure the client with your API key, you can perform practical tasks such as listing all your projects, retrieving feedback with filters, fetching bug reports with severity, and performing text searches across feedback content. Focus on concrete goals like reviewing recent feedback for a specific project or locating high-severity bug reports to triage.
Prerequisites: Node.js installed on your machine. You will also need an API key from your FeedbackBasket account.
Step 1: Install the MCP server execution configuration in your editor or environment. Use the following configuration snippet to run the MCP server via npx with your API key.
{
"mcpServers": {
"feedbackbasket": {
"command": "npx",
"args": ["-y", "@feedbackbasket/mcp-server@latest", "--api-key", "fb_key_your_api_key_here"]
}
}
}You can also run the MCP server using an environment variable as an alternative to passing the key on the command line.
{
"mcpServers": {
"feedbackbasket": {
"command": "npx",
"args": ["-y", "@feedbackbasket/mcp-server@latest"],
"env": {
"FEEDBACKBASKET_API_KEY": "fb_key_your_api_key_here"
}
}
}
}Access is read-only and controlled by API keys with project-level permissions. Each key can be revoked, and usage is tracked in your dashboard. Ensure keys are kept secure and only granted access to the necessary projects.
If you encounter authentication issues, verify that your API key starts with fb_key_ and that it is active and has access to at least one project. If you see authentication failures, confirm the key has not been revoked and the format is correct (71 characters, starts with fb_key_). If you run into installation problems, ensure Node.js is installed and try clearing the npx cache with npx clear-npx-cache. Check your internet connection for package downloads.
Manage API keys from your FeedbackBasket dashboard: create new keys, adjust project access, monitor usage, and revoke keys as needed.
If you run into issues, open issues on the appropriate platform for assistance and consult the FeedbackBasket documentation for guidance.
Lists all projects accessible by your API key with summary statistics.
Retrieves feedback with optional filtering by project, category, status, sentiment, and text search.
Fetches bug reports with computed severity and optional filters for project, status, and severity.
Searches feedback content across all accessible projects with a text query and optional filters.