Skip to main content
Glama
BAM-DevCrew

MAXential Thinking MCP

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MAXENTIAL_DB_PATHNoPath to SQLite database file. Default: .maxential/thinking.db in working directory. Use :memory: for in-memory.
MAXENTIAL_LOG_FILENoPath to log file for error logging.

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
thinkA

Add a numbered thought to your reasoning chain. Each call persists to SQLite automatically. On first call, a new session is created. Use for any multi-step reasoning — analysis, debugging, design, research. Subsequent thoughts are appended to the active branch (main by default). Do not use for simple, single-step answers.

reviseA

Replace a previous thought with updated reasoning. The original thought is preserved in revision history. Use when earlier thinking was wrong, incomplete, or superseded by new information. Persists to SQLite. Do not use to add new thoughts — use think instead.

completeA

Mark the thinking chain as complete with a final conclusion. Sets the session status to 'complete'. Use when reasoning has reached a definitive answer. The session remains accessible via session_load and session_list. Do not call if you plan to continue thinking — you can always add more thoughts.

resetA

Clear the in-memory thinking state and start a fresh session. The previous session's data is NOT deleted — it remains in SQLite and can be loaded later with session_load. Destructive to in-memory state only. Returns confirmation. Use when switching to an unrelated problem where carrying the old context would be noise. Requires confirm=true to prevent accidental clearing.

branchA

Create a new reasoning branch and switch to it. Subsequent think calls go to this branch until you switch_branch. Use to explore an alternative approach without affecting the main thread. Each branch maintains its own thought sequence. Persists to SQLite. Use close_branch when a path is exhausted, or merge_branch to bring insights back to main.

switch_branchA

Switch which branch receives new thoughts. Omit branchId to return to main. After switching, all think and revise calls apply to the active branch. Read-only tools (get_thought, search, get_history) can access any branch regardless of which is active. Does not modify any data.

list_branchesA

List all reasoning branches in the current session. Read-only. Returns for each branch: branch ID, origin thought number, status (active/closed/merged), conclusion if set, thought count, and timestamps. Use to see what reasoning paths exist before switching, merging, or closing. The main branch is always included. No parameters — operates on the active session.

get_branchA

Retrieve a specific branch's metadata and full thought history. Read-only. Returns: branch ID, origin thought, status (active/closed/merged), conclusion if set, all thoughts in the branch with their numbers and content, and timestamps. Use to deeply inspect a branch's reasoning before deciding to merge, close, or continue it. Use list_branches first to get the branch ID.

close_branchA

Close a branch, marking it as no longer active. Optionally include a conclusion summarizing what was learned. Closed branches and their thoughts are preserved and remain readable. Use when a line of reasoning is exhausted or the answer is clear. Cannot be reopened. To bring findings back to main first, use merge_branch instead.

merge_branchA

Merge findings from a branch back into the main thread as a new thought on main. The branch is marked as merged afterward. Strategies: conclusion_only — adds only the branch conclusion to main; full_integration — adds all branch thoughts to main; summary — generates a condensed summary of the branch on main. Use after a branch has produced useful findings you want on the main thread.

get_thoughtA

Retrieve a specific thought by its number, including any tags and revision history. Read-only. Use to reference or review earlier reasoning without scrolling through the full history.

get_historyA

Retrieve the thought history for the current active session. Read-only. Returns thoughts in chronological order with their numbers, content, tags, branch assignments, and any revision links. Optionally filter to a specific branch with branchId, or cap results with limit. Use to review the full reasoning chain or to find context before adding the next thought.

tagA

Add or remove semantic tags on a thought. Tags are searchable via the search tool. Common tags: hypothesis, evidence, decision, finding, question, risk. Persists to SQLite. At least one of 'add' or 'remove' should be provided.

searchA

Search the current session's thoughts by text content, tags, or both. Text search is case-insensitive substring matching. Tag search requires all specified tags to be present. Optionally limit to a specific branch. Read-only. Returns matching thoughts with their numbers, content, and tags.

exportA

Export the current session's thinking chain as formatted text. Read-only. Markdown format produces a human-readable document with section headers per thought, branch headings, and tags as inline markers — suitable for handoffs or documentation. JSON format produces machine-parseable output including all thoughts, branches, tags, and metadata. Optionally export a single branch by providing branchId. Default format is markdown. Use when sharing reasoning with humans or other systems.

visualizeA

Generate a visual diagram of the thinking chain showing thoughts, branches, branch points, and revisions. Read-only. Returns a single text block ready to display. Mermaid format produces a graph for rendering in GitHub, Obsidian, or markdown documentation. ASCII format produces a plain-text tree for terminal or inline display in conversation. Default format is mermaid. Use to share the reasoning structure or to orient in a long chain. Set showContent=true to include thought preview text in nodes (default false for compactness).

session_saveA

Name and describe the active thinking session for later retrieval. The session and all its thoughts are already persisted to SQLite automatically — this only adds a human-readable name and optional description. Persists session metadata. Use when you want to find this session later via session_list. Without session_save, the session keeps an auto-generated timestamp name.

session_loadA

Restore a previously saved thinking session into memory, replacing the current in-memory state. All thoughts, branches, and tags from the saved session are loaded. The current session's data is not lost — it remains in SQLite and can be loaded later. Use after session_list to find the session UUID. Replaces current working state.

session_listA

List previously saved thinking sessions in the SQLite database. Read-only. Returns: session UUID, name, description, status (active/complete/archived), created/updated timestamps, thought count, branch count. Sorted by most recently updated first. Use to find a session UUID before calling session_load or session_summary. Filter by status to find specifically complete or archived work.

session_summaryA

Generate a compressed text summary of a saved session for token-efficient context loading. Read-only. Returns: session metadata, key findings extracted from conclusions and tagged thoughts, branch results, and final conclusion. Use when you want context from a previous session without loading the full thought history. For full restoration use session_load instead. Default summary length is 2000 characters, adjustable via maxLength.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/BAM-DevCrew/MAXential-Thinking-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server