A structured, persistent reasoning workspace for AI. 20 tools for thought chains, branching, revision, search, and session persistence across context
Connect Maxential Thinking MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. A structured, persistent reasoning workspace for AI. 20 tools for thought chains, branching, revision, search, and session persistence across context resets. The maxential thinking mcp mcp server is what makes that connection.
A structured, persistent reasoning workspace for AI. Provides 20 tools for building thought chains, exploring alternatives through branching, revising earlier thinking, searching reasoning history, and persisting sessions across context window resets and server restarts.
npm on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Branching — The Branching tool exposed by this serverNavigation — The Navigation tool exposed by this serverOrganization — The Organization tool exposed by this serverPersistence — Session data is stored in SQLite. By default, the database is created at .maxential/thinking.db in the working directoryLogging — The Logging tool exposed by this serverConfiguration is passed through the environment: MAXENTIAL_DB_PATH, MAXENTIAL_LOG_FILE. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the database access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Maxential Thinking MCP's toolset — Branching, Navigation, Organization and 2 more — is a fair guide to whether it matches your workflow. It is maintained by bam-devcrew; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Branching | The Branching tool exposed by this server. |
| Navigation | The Navigation tool exposed by this server. |
| Organization | The Organization tool exposed by this server. |
| Persistence | Session data is stored in SQLite. By default, the database is created at .maxential/thinking.db in the working directory. |
| Logging | The Logging tool exposed by this server. |
{
"mcpServers": {
"maxential-thinking": {
"command": "node",
"args": ["/path/to/MAXential-Thinking-MCP/dist/src/index.js"]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| MAXENTIAL_DB_PATH | Filesystem location the server is allowed to use. | Optional |
| MAXENTIAL_LOG_FILE | Configuration value read at startup. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.