Structured Thinking MCP Server

Created By
Promptly-Technologies-LLCa year ago
A TypeScript Model Context Protocol (MCP) server to allow LLMs to programmatically construct mind maps to explore an idea space, with enforced "metacognitive" self-reflection
Overview

what is Structured Thinking MCP Server?

The Structured Thinking MCP Server is a TypeScript-based Model Context Protocol (MCP) server designed to enable large language models (LLMs) to programmatically create mind maps for exploring ideas, while incorporating metacognitive self-reflection.

how to use Structured Thinking MCP Server?

To use the server, configure it in an MCP client like Claude Desktop or Cursor by setting the tool configuration with the command to run the server.

key features of Structured Thinking MCP Server?

  • Thought Quality Scores to evaluate the quality of thoughts.
  • Thought Stages to manage the lifecycle of thinking processes.
  • Thought Branching to explore multiple lines of reasoning.
  • Memory Management for short-term and long-term thought storage.

use cases of Structured Thinking MCP Server?

  1. Assisting LLMs in structured problem-solving.
  2. Facilitating brainstorming sessions with multiple ideas.
  3. Enhancing creative thinking through guided thought processes.

FAQ from Structured Thinking MCP Server?

  • What is the purpose of Thought Quality Scores?

They help provide feedback to the LLM on how to improve its thinking process.

  • Can I visualize the mind map?

Currently, there is no user interface for visualization, but future updates may include this feature.

  • Is there a way to save thoughts?

Currently, thoughts are stored in memory and not persisted to a file or database.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Promptly-Technologies-LLC
Star
0
Language
TypeScript
License
MIT license
Tags

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago