Labsco
MCP SERVER

DeepLucid3D UCPF Server

by MushroomFleet

Run a problem through a structured cognitive framework — assumptions challenged, knowns and unknowns mapped, alternative perspectives generated, with optional session memory.

Reasoning Scaffolds & Agent Workflow EnginesVerified
Summary
A fixed procedure, so the same questions get asked every time.

The value is not that a model can think about your problem — it can already — but that this asks the same structural questions in the same order: what am I assuming, what do I know versus what is knowable, what would the opposite framing look like. Session state is worth enabling for anything that runs past one call, because the accumulated analysis is readable afterwards as its own resource rather than being scattered through the transcript.

What it is

An MCP server implementing the Unified Cognitive Processing Framework: a fixed procedure for taking a problem apart. It assesses the thinking state a problem is being approached from, maps what is known against what is knowable, asks recursive questions that challenge the framing, and produces alternative perspectives — optionally keeping the analysis across a session.

What you get
  • A problem statement run through the whole framework — cognitive state assessment, knowledge mapping across awareness, content and accessibility, recursive questions that challenge the initial assumptions, and structured perspectives — at a normal or detailed level — `analyze_problem`
  • Novel viewpoints and metaphors on a topic, with the number of perspectives you want and constraints you supply to keep them relevant — `creative_exploration`
  • Session persistence turned on, off, reset or inspected, so a multi-step analysis keeps its context — `manage_state`
  • The framework itself readable as resources: `ucpf://framework/overview`, `ucpf://framework/cognitive-states` and `ucpf://framework/knowledge-dimensions`, plus a session's accumulated analysis at `ucpf://session/{sessionId}/analysis`
Requirements

No account and no key — the configuration block has an empty `env`. Node.js v14 or higher and npm v6 or higher. The npm package name is `DeepLucid3D` (0.1.0) and it is marked private, so build from a clone with `npm install` and `npm run build`, then point your client at the built `index.js`. State is off unless you enable it, so pass a session id and switch it on when you want an analysis to accumulate across calls.

Setup effort

One command — npx -y github:MushroomFleet/DeepLucid3D-MCP