mcp server
BrainFlow
AI-powered ticket triage and workflow automation
Description as published by the maintainer. Source
- version 0.0.1
- active
- workflow automation
active — Registry entry last updated 2026-05-31. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
12 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
connect-provider(provider)- Internal — initiate an OAuth connection flow for a provider. Required: provider.
fetch-analysis(ticketId)- Fetch LLM analysis (findings + solutions) for a ticket. Required: ticketId.
get-agent-config(role)- Internal — load saved agent.md content for a role. Required: role.
get-connection-status- Internal — get current connection status for all providers.
hitl-execute(repo, notes, owner, source, platform, ticket_id, solution_id, solution_risk, solution_title, solution_effort, jira_project_key, solution_summary)- Internal — approve a candidate solution and create issues on the target platform (Jira stories or GitHub issues). Required: platform, source, ticket_id, solution_id.
hitl-reject(reason, source, ticket_id)- Internal — reject a BrainFlow HITL item with a rework reason. Required: source, ticket_id, reason.
list-github-repos- Internal — list the user's GitHub repositories for repo selection.
list-jira-projects- Internal — list the user's Jira projects for project selection.
open-ticket(role, ticketId)- Open a specific ticket to see its details, MCP findings, and candidate solutions. Required: ticketId.
save-agent-config(role, content)- Internal — save agent.md content for a role. Required: role, content.
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.
triage(sources, jira_project)- 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.
Last successful function declaration observed on . Source: https://alpichack-3c740d01.alpic.live. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://alpichack-3c740d01.alpic.live.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 0.0.1 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-05-31 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-05-31 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 12 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | alpichack-3c740d01.alpic.live | |
| mcp endpoint status | ok | The server listed 12 functions when asked. | as of probe | alpichack-3c740d01.alpic.live |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json