live.alpic.alpichack-3c740d01/alpichack

Official12 tools

BrainFlow

AI-powered ticket triage and workflow automation

AI-powered ticket triage and workflow automation system.

Captured live from the server via tools/list.

setup

Open the BrainFlow onboarding wizard. Use this when the user wants to configure BrainFlow, connect a task system (GitHub, Jira, or Slack), or change their role. Guides the user through role selection and OAuth connection in a step-by-step widget.

No parameters.

triage

Show open tickets from connected task systems with triage classification. When the user asks for tickets from a specific system (e.g. 'show Jira tickets' or 'GitHub issues'), pass the matching source in the sources array.

Parameters (2)

sourcesarray
Filter tickets to specific sources. Pass ['jira'] for Jira only, ['github'] for GitHub only, etc. Omit to show tickets from all connected sources.
jira_projectstring
Jira project/space key to filter tickets (e.g. KAN). Only used when sources includes jira.

open-ticket

Open a specific ticket to see its details, MCP findings, and candidate solutions.

Parameters (2)

ticketIdstringrequired
The ticket ID to open, e.g. sc-1842 or GH-123. Use the id field from triage results.
rolestring
User role — determines Jira tickets (PM) or GitHub issues (engineer)

get-agent-config

Internal — load saved agent.md content for a role.

Parameters (1)

rolestringrequired
Role identifier, e.g. 'engineer' or 'pm'

save-agent-config

Internal — save agent.md content for a role.

Parameters (2)

rolestringrequired
Role identifier, e.g. 'engineer' or 'pm'
contentstringrequired
The agent.md content to save

connect-provider

Internal — initiate an OAuth connection flow for a provider.

Parameters (1)

providerstringrequired
Provider to connect

fetch-analysis

Fetch LLM analysis (findings + solutions) for a ticket.

Parameters (1)

ticketIdstringrequired
The ticket source_id, e.g. KAN-1

get-connection-status

Internal — get current connection status for all providers.

No parameters.

hitl-execute

Internal — approve a candidate solution and create issues on the target platform (Jira stories or GitHub issues).

Parameters (12)

platformstringrequired
Target platform. 'jira' for PM creating Jira stories, 'github' for engineer creating GitHub issues.
sourcestringrequired
Source system the ticket came from
ticket_idstringrequired
The ticket identifier
solution_idstringrequired
The chosen solution id
solution_titlestring
Title of the chosen solution
solution_summarystring
Summary of the chosen solution
solution_riskstring
Risk level (Jira only)
solution_effortstring
Effort estimate (Jira only)
notesstring
PM/engineer notes
jira_project_keystring
Jira project key, e.g. KAN (Jira only)
ownerstring
GitHub repo owner (required when platform=github)
repostring
GitHub repo name (required when platform=github)

hitl-reject

Internal — reject a BrainFlow HITL item with a rework reason.

Parameters (3)

sourcestringrequired
The source system the ticket came from
ticket_idstringrequired
The ticket identifier, e.g. GH-123 or sc-1842
reasonstringrequired
Short explanation of why all candidate solutions were rejected and what needs to change

list-github-repos

Internal — list the user's GitHub repositories for repo selection.

No parameters.

list-jira-projects

Internal — list the user's Jira projects for project selection.

No parameters.

Install

claude_desktop_config.json

{
  "mcpServers": {
    "alpichack": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://alpichack-3c740d01.alpic.live"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.