AI Assistant Integration

Connect BetaHub with AI-powered development assistants to manage feedback using natural language.

Overview

The BetaHub MCP Server enables AI assistants like Claude to interact with your BetaHub projects through the Model Context Protocol (MCP). This integration allows you to query bugs, feature requests, and project information using natural language - directly from your development environment.

Key Benefits:

• Query feedback without leaving your IDE or terminal
• Use natural language instead of remembering API syntax
• Spot patterns and cluster related issues quickly
• Stay in flow while managing your testing process

What is MCP?

The Model Context Protocol (MCP) is an open standard that connects AI assistants to external data sources and tools. The BetaHub MCP Server implements this protocol, giving AI assistants secure access to your BetaHub data.

Prerequisites

Before setting up the integration, ensure you have:

• Node.js v18 or higher - Download from nodejs.org
• A BetaHub account with at least one project
• Personal Access Token - Create one here

Installation

The BetaHub MCP Server is available as an npm package:

npm install -g betahub-mcp-server

Quick Start

Choose your AI assistant and follow the setup:

Claude Code (CLI)

# Install and configure in one step
claude mcp add betahub npx betahub-mcp-server -- --token=pat-your-token-here

# Verify it works
claude -p "Show me my BetaHub projects"

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS):

{
  "mcpServers": {
    "betahub": {
      "command": "npx",
      "args": ["betahub-mcp-server", "--token=pat-your-token-here"]
    }
  }
}

Cline (VS Code)

In VS Code settings, search for “Cline MCP Servers” and add:

{
  "cline.mcpServers": {
    "betahub": {
      "command": "npx",
      "args": ["betahub-mcp-server", "--token=pat-your-token-here"]
    }
  }
}

Gemini

Add to your Gemini configuration:

{
  "mcpServers": {
    "betahub": {
      "command": "npx",
      "args": ["betahub-mcp-server", "--token=pat-your-token-here"]
    }
  }
}

Remember: Replace pat-your-token-here with your actual Personal Access Token.

Detailed Configuration

Claude Code

Add the BetaHub MCP server to Claude Code with a single command:

# Replace pat-your-token-here with your actual token
claude mcp add betahub npx betahub-mcp-server -- --token=pat-your-token-here

Verify the connection:

# List configured MCP servers
claude mcp list

# Test the integration
claude -p "What BetaHub MCP tools are available?"

Alternative: Using Environment Variable

If you prefer environment variables:

claude mcp add-json betahub '{
  "command": "npx",
  "args": ["betahub-mcp-server"],
  "env": {
    "BETAHUB_TOKEN": "pat-your-token-here"
  }
}'

Claude Desktop App

Add to your Claude Desktop configuration file:

Configuration File Locations:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json
• Linux: ~/.config/claude/claude_desktop_config.json

{
  "mcpServers": {
    "betahub": {
      "command": "npx",
      "args": ["betahub-mcp-server", "--token=pat-your-token-here"]
    }
  }
}

Cline (VS Code Extension)

1. Open VS Code settings (Cmd/Ctrl + ,)
2. Search for “Cline MCP Servers”
3. Add the BetaHub server configuration:

{
  "cline.mcpServers": {
    "betahub": {
      "command": "npx",
      "args": ["betahub-mcp-server", "--token=pat-your-token-here"]
    }
  }
}

Gemini

Add the BetaHub MCP server to your Gemini configuration:

{
  "mcpServers": {
    "betahub": {
      "command": "npx",
      "args": ["betahub-mcp-server", "--token=pat-your-token-here"]
    }
  }
}

Generic MCP Clients

For any MCP-compatible client:

• Transport Type: stdio
• Command: npx betahub-mcp-server --token=pat-your-token-here
• Authentication: Token can be passed as --token=pat-xxx argument or via BETAHUB_TOKEN environment variable

Usage Examples

Once configured, interact with BetaHub through natural language queries to your AI assistant.

Project Discovery

Get an overview of your BetaHub projects:

"Show me all my BetaHub projects"
"Which projects have the most bug reports?"
"What's the status of my racing game project?"

Daily Workflow

Check what needs attention:

"What critical bugs need attention in SuperCraft?"
"Show me in-progress issues in my racing game"
"List unresolved bugs reported this week"
"What new feedback came in today?"

Pattern Detection & Clustering

Find related issues and spot trends:

"Show me all bugs related to multiplayer mode"
"Find feature requests about level 3"
"What feedback mentions 'connection issues'?"
"Are there bugs reported about the tutorial?"
"Find similar bugs to issue 456"
"Are there other reports about crashing on startup?"
"Show me suggestions similar to 789"
"What issues mention the shop system?"

Planning & Prioritization

Prepare for sprints and releases:

"What are the top 10 most requested features in my game?"
"Show me high priority bugs that haven't been addressed"
"List feature requests about multiplayer functionality"
"What bugs should we tackle first?"

Release Planning

Track progress and blockers:

"What bugs were resolved since last release?"
"Show me features under moderation for next sprint"
"List all critical issues blocking release in my project"
"Are we ready to ship the new update?"

Community Insights

Understand player feedback:

"What features are users requesting most this month?"
"Show me feedback trends about the combat system"
"Are players having trouble with the tutorial?"
"What do testers think about the new level design?"

Specific Lookups

Get details on individual items:

"Find bug report 456"
"Show me details for feature request 789"
"What's the status of issue 123?"
"Who reported bug 234?"

Available Tools

The BetaHub MCP Server provides the following tools:

Project Management:

• list_projects - View all accessible BetaHub projects

Feature Requests (Suggestions):

• list_feature_requests - Browse suggestions with filtering and sorting
• search_feature_requests - Search by text or find by ID

Issues (Bug Reports):

• list_issues - Browse bugs with filtering and sorting
• search_issues - Search by text or find by ID

Filtering Options:

• Status: new, in_progress, resolved, closed, under_moderation
• Priority: low, medium, high, critical
• Sorting: newest, oldest, most_voted

Best Practices

Security

• Protect Your Token - Never commit tokens to version control
• Use Environment Variables - For shared configurations, use env vars instead of hardcoded tokens
• Rotate Regularly - Create new tokens periodically and revoke old ones
• Scope Appropriately - Only grant necessary permissions to your tokens

Efficient Queries

• Be Specific - Use project names to narrow results
• Filter Early - Specify status or priority to reduce noise
• Combine Conditions - “Show critical bugs in MyGame that are unresolved”
• Follow Up - Ask follow-up questions to drill into details

Workflow Integration

• Morning Standup - “What new bugs came in overnight?”
• Sprint Planning - “Show me high priority items for next sprint”
• Release Preparation - “Are there any critical blockers?”
• Community Check - “What are users saying about the latest update?”

Troubleshooting

Connection Failed

Verify Installation:

npm list -g betahub-mcp-server

Test Token Directly:

export BETAHUB_TOKEN="pat-your-token-here"
npx betahub-mcp-server

Check Configuration:

# For Claude Code
claude mcp list

Authentication Errors

• Verify your token hasn’t expired in API Access settings
• Ensure you’re using the correct token format (pat- prefix)
• Try generating a new token
• Check that the token has appropriate permissions

No Results Returned

• Verify the project name is correct
• Check that you have access to the specified project
• Try broadening your search criteria
• Confirm the project has data to query

Version Issues

Install a specific version if needed:

# Install specific version
npm install -g betahub-mcp-server@0.0.4

# Use specific version in configuration
npx betahub-mcp-server@0.0.4 --token=pat-your-token-here

Development and Contribution

Building from Source

To contribute or customize the server:

# Clone the repository
git clone https://github.com/betahub-io/betahub-mcp-server.git
cd betahub-mcp-server

# Install dependencies
npm install

# Build the project
npm run build

# Test locally
export BETAHUB_TOKEN="pat-your-token-here"
./build/index.js

Using Local Build in Claude Code

For development:

claude mcp add betahub-dev /absolute/path/to/betahub-mcp-server/build/index.js -- --token=pat-your-token-here

Resources

• NPM Package: npmjs.com/package/betahub-mcp-server
• GitHub Repository: github.com/betahub-io/betahub-mcp-server
• Issues & Support: GitHub Issues
• API Documentation: BetaHub API Access
• Model Context Protocol: modelcontextprotocol.io

Next Steps

• Create a Personal Access Token if you haven’t already
• Explore Webhook Integrations for automated workflows
• Learn about External Tools for project management integration