ultrabrain-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ultrabrain_startB | Create a branded LCV Ultrabrain reasoning session and optionally seed the first thought. |
| ultrabrain_thinkA | Canonical LCV reasoning gate for code work, branching, revisions, quality metrics, bias checks, confidence, and meta checkpoints. Protocol: state evidence and assumptions before conclusions; set step_type honestly (analysis, hypothesis, verification, conclusion...); attach evidence[] for any factual claim; branch when a materially different path exists and revise when an earlier step was wrong; adjust total_thoughts when scope changes instead of forcing a fit; only set next_thought_needed to false once a verification step has checked the conclusion. Close each step by asking: what am I missing or need to reconsider? |
| ultrabrain_updateB | Update an existing thought with stronger evidence, confidence, risks, actions, or quality metrics. |
| ultrabrain_branchB | Create or continue an Ultrabrain branch from a prior thought. |
| ultrabrain_mergeB | Merge one or more branch insights into a synthesis, best-evidence path, or decision note. |
| ultrabrain_validateB | Check a reasoning session for evidence, alternatives, verification, bias, and closure gaps. |
| ultrabrain_analyzeB | Analyze quality, confidence, bias counts, label counts, unresolved questions, and recommendations. |
| ultrabrain_reviewC | Render a reasoning session as a summary, linear chain, tree, markdown, or JSON. |
| ultrabrain_statusA | Return session status, thought count, branches, and latest quality score. |
| ultrabrain_historyA | Return recent normalized thought records for a session. |
| ultrabrain_exportA | Export a session as markdown, text, or JSON. |
| ultrabrain_metricsA | Return aggregate session, thought, branch, quality, confidence, bias, mode, and step metrics. |
| ultrabrain_templatesA | List LCV Ultrabrain prompt templates for common engineering reasoning workflows. |
| ultrabrain_resetA | Reset one Ultrabrain session, or all sessions when all_sessions is true. |
| ultrabrain_server_infoA | Return runtime information for the local Ultrabrain MCP server, including version, release date, capabilities, tool surface, data directory, and active limits. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| ultrabrain_problem_breakdown | Break a technical problem into evidence, assumptions, hypotheses, verification, and risks. |
| ultrabrain_critical_review | Review an implementation or decision with counterexamples, residual risk, and verification checks. |
| ultrabrain_synthesis | Synthesize several branches or findings into a decision and next action list. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Ultrabrain Sessions | Current Ultrabrain sessions. |
TDQS
Scored across 15 tools
The tools share a common session/thought subject and the analytics/reporting cluster (metrics, analyze, validate, status, review, export) overlaps in what it returns. Descriptions do help, but an agent could easily pick the wrong inspection tool for a given task.
All tools consistently share the ultrabrain_ prefix and use snake_case, creating a predictable surface. However, the suffixes mix bare verbs (think, merge, validate) with nouns (metrics, history, status), so it is not a strict verb_noun pattern.
Fifteen tools is at the high end of a reasonable scope for a reasoning-session server. Most tools serve a distinct lifecycle purpose, though the analytics/reporting cluster could be consolidated without losing much capability.
The toolset covers session creation, thought progression, branching, merging, validation, analysis, export, and reset. Minor gaps exist, such as no obvious way to list all available sessions or a dedicated delete operation, but reset and server_info partially compensate.