Skip to main content
Glama
spences10

mcp-sequentialthinking-tools

by spences10

mcp-sequentialthinking-tools

built with vite+ tested with vitest

A lightweight MCP server for recording sequential reasoning steps. It is a scratchpad with history, branching, revision metadata, and optional validation for model-authored tool plans.

It does not discover your other MCP tools and it does not choose tools for the model. If you pass available_tools and recommended_tools, the server validates that the recommended names exist and stores the step.

Why use it?

Use this when a task benefits from explicit, inspectable reasoning:

  • breaking a messy problem into steps;

  • revising or branching a plan;

  • keeping a small reasoning history by session;

  • validating tool-plan names against a supplied tool list;

  • clearing or inspecting reasoning history during a long agent run.

Do not use it for trivial requests. It adds overhead.

Related MCP server: Sequential-Thinking

Tools

sequentialthinking_tools

Records one thought.

Required parameters:

  • thought — current reasoning step

  • thought_number — current step number

  • total_thoughts — current estimate; automatically raised if lower than thought_number

  • next_thought_needed — whether another thought is needed

Optional parameters:

  • session_id — history bucket; defaults to default

  • is_revision, revises_thought

  • branch_from_thought, branch_id

  • needs_more_thoughts

  • available_tools — array of tool names or { name, description } objects

  • recommended_tools — model-authored recommendations to validate/store

  • remaining_steps — short list of upcoming steps

Example:

{
	"session_id": "svelte-debug",
	"thought": "First inspect the route files, then run the failing check.",
	"thought_number": 1,
	"total_thoughts": 3,
	"next_thought_needed": true,
	"available_tools": ["read", "bash"],
	"recommended_tools": [
		{
			"tool_name": "read",
			"confidence": 0.9,
			"rationale": "Need to inspect the relevant files before editing.",
			"priority": 1
		}
	]
}

If recommended_tools contains a name not present in available_tools, the call returns isError: true and does not store the thought.

Security posture

The server treats thought text, tool descriptions, rationales, and remaining-step text as untrusted input. Prompt-injection-like text is scanned and redacted before it is stored or returned in history. Calls with redactions include security_warnings showing which fields matched.

This is defensive filtering, not a guarantee that arbitrary adversarial text is safe. Do not put secrets in thoughts or tool descriptions.

get_thinking_history

Returns stored thoughts for a session.

Parameters:

  • session_id — defaults to default

  • branch_id — optional branch filter

  • limit — max records to return; default 50, max 500

clear_thinking_history

Clears one session or every session.

Parameters:

  • session_id — defaults to default

  • all_sessions — clear all history buckets

Prompt

sequential-thinking-guidance

A short prompt that tells the model how to use this server honestly: as a scratchpad and validator, not as an external reasoning engine.

Configuration

Claude Desktop / compatible MCP clients

{
	"mcpServers": {
		"mcp-sequentialthinking-tools": {
			"command": "npx",
			"args": ["-y", "mcp-sequentialthinking-tools"],
			"env": {
				"MAX_HISTORY_SIZE": "1000"
			}
		}
	}
}

MAX_HISTORY_SIZE is per session and defaults to 1000.

The server uses tmcp and includes a small stdio transport that accepts both standard Content-Length framed MCP messages and newline-delimited JSON used by older tmcp tooling.

Development

pnpm install
pnpm test
pnpm build
pnpm check

This project uses vite-plus for build, test, format, and lint orchestration.

Publishing

pnpm changeset
pnpm changeset version
pnpm release

License

MIT License — see LICENSE.

Acknowledgments

Available Tools

1 tool
sequentialthinking_toolsA detailed tool for dynamic and reflective problem-solving through thoughts. This tool helps analyze problems through a flexible thinking process that can adapt and evolve. Each thought can build on, question, or revise previous insights as understanding deepens. IMPORTANT: This server facilitates sequential thinking with MCP tool coordination. The LLM analyzes available tools and their descriptions to make intelligent recommendations, which are then tracked and organized by this server. When to use this tool: - Breaking down complex problems into steps - Planning and design with room for revision - Analysis that might need course correction - Problems where the full scope might not be clear initially - Problems that require a multi-step solution - Tasks that need to maintain context over multiple steps - Situations where irrelevant information needs to be filtered out - When you need guidance on which tools to use and in what order Key features: - You can adjust total_thoughts up or down as you progress - You can question or revise previous thoughts - You can add more thoughts even after reaching what seemed like the end - You can express uncertainty and explore alternative approaches - Not every thought needs to build linearly - you can branch or backtrack - Generates a solution hypothesis - Verifies the hypothesis based on the Chain of Thought steps - Recommends appropriate tools for each step - Provides rationale for tool recommendations - Suggests tool execution order and parameters - Tracks previous recommendations and remaining steps Parameters explained: - available_mcp_tools: Array of MCP tool names that are available for use (e.g., ["mcp-omnisearch", "mcp-turso-cloud"]) - thought: Your current thinking step, which can include: * Regular analytical steps * Revisions of previous thoughts * Questions about previous decisions * Realizations about needing more analysis * Changes in approach * Hypothesis generation * Hypothesis verification * Tool recommendations and rationale - next_thought_needed: True if you need more thinking, even if at what seemed like the end - thought_number: Current number in sequence (can go beyond initial total if needed) - total_thoughts: Current estimate of thoughts needed (can be adjusted up/down) - is_revision: A boolean indicating if this thought revises previous thinking - revises_thought: If is_revision is true, which thought number is being reconsidered - branch_from_thought: If branching, which thought number is the branching point - branch_id: Identifier for the current branch (if any) - needs_more_thoughts: If reaching end but realizing more thoughts needed - current_step: Current step recommendation, including: * step_description: What needs to be done * recommended_tools: Tools recommended for this step * expected_outcome: What to expect from this step * next_step_conditions: Conditions to consider for the next step - previous_steps: Steps already recommended - remaining_steps: High-level descriptions of upcoming steps You should: 1. Start with an initial estimate of needed thoughts, but be ready to adjust 2. Feel free to question or revise previous thoughts 3. Don't hesitate to add more thoughts if needed, even at the "end" 4. Express uncertainty when present 5. Mark thoughts that revise previous thinking or branch into new paths 6. Ignore information that is irrelevant to the current step 7. Generate a solution hypothesis when appropriate 8. Verify the hypothesis based on the Chain of Thought steps 9. Consider available tools that could help with the current step 10. Provide clear rationale for tool recommendations 11. Suggest specific tool parameters when appropriate 12. Consider alternative tools for each step 13. Track progress through the recommended steps 14. Provide a single, ideally correct answer as the final output 15. Only set next_thought_needed to false when truly done and a satisfactory answer is reachedA

A detailed tool for dynamic and reflective problem-solving through thoughts. This tool helps analyze problems through a flexible thinking process that can adapt and evolve. Each thought can build on, question, or revise previous insights as understanding deepens.

IMPORTANT: This server facilitates sequential thinking with MCP tool coordination. The LLM analyzes available tools and their descriptions to make intelligent recommendations, which are then tracked and organized by this server.

When to use this tool:

  • Breaking down complex problems into steps

  • Planning and design with room for revision

  • Analysis that might need course correction

  • Problems where the full scope might not be clear initially

  • Problems that require a multi-step solution

  • Tasks that need to maintain context over multiple steps

  • Situations where irrelevant information needs to be filtered out

  • When you need guidance on which tools to use and in what order

Key features:

  • You can adjust total_thoughts up or down as you progress

  • You can question or revise previous thoughts

  • You can add more thoughts even after reaching what seemed like the end

  • You can express uncertainty and explore alternative approaches

  • Not every thought needs to build linearly - you can branch or backtrack

  • Generates a solution hypothesis

  • Verifies the hypothesis based on the Chain of Thought steps

  • Recommends appropriate tools for each step

  • Provides rationale for tool recommendations

  • Suggests tool execution order and parameters

  • Tracks previous recommendations and remaining steps

Parameters explained:

  • available_mcp_tools: Array of MCP tool names that are available for use (e.g., ["mcp-omnisearch", "mcp-turso-cloud"])

  • thought: Your current thinking step, which can include:

  • Regular analytical steps

  • Revisions of previous thoughts

  • Questions about previous decisions

  • Realizations about needing more analysis

  • Changes in approach

  • Hypothesis generation

  • Hypothesis verification

  • Tool recommendations and rationale

  • next_thought_needed: True if you need more thinking, even if at what seemed like the end

  • thought_number: Current number in sequence (can go beyond initial total if needed)

  • total_thoughts: Current estimate of thoughts needed (can be adjusted up/down)

  • is_revision: A boolean indicating if this thought revises previous thinking

  • revises_thought: If is_revision is true, which thought number is being reconsidered

  • branch_from_thought: If branching, which thought number is the branching point

  • branch_id: Identifier for the current branch (if any)

  • needs_more_thoughts: If reaching end but realizing more thoughts needed

  • current_step: Current step recommendation, including:

  • step_description: What needs to be done

  • recommended_tools: Tools recommended for this step

  • expected_outcome: What to expect from this step

  • next_step_conditions: Conditions to consider for the next step

  • previous_steps: Steps already recommended

  • remaining_steps: High-level descriptions of upcoming steps

You should:

  1. Start with an initial estimate of needed thoughts, but be ready to adjust

  2. Feel free to question or revise previous thoughts

  3. Don't hesitate to add more thoughts if needed, even at the "end"

  4. Express uncertainty when present

  5. Mark thoughts that revise previous thinking or branch into new paths

  6. Ignore information that is irrelevant to the current step

  7. Generate a solution hypothesis when appropriate

  8. Verify the hypothesis based on the Chain of Thought steps

  9. Consider available tools that could help with the current step

  10. Provide clear rationale for tool recommendations

  11. Suggest specific tool parameters when appropriate

  12. Consider alternative tools for each step

  13. Track progress through the recommended steps

  14. Provide a single, ideally correct answer as the final output

  15. Only set next_thought_needed to false when truly done and a satisfactory answer is reached

ParametersJSON Schema
NameRequiredDescriptionDefault
available_mcp_toolsYesArray of MCP tool names available for use (e.g., ["mcp-omnisearch", "mcp-turso-cloud"])
thoughtYesYour current thinking step
next_thought_neededYesWhether another thought step is needed
thought_numberYesCurrent thought number
total_thoughtsYesEstimated total thoughts needed
is_revisionNoWhether this revises previous thinking
revises_thoughtNoWhich thought is being reconsidered
branch_from_thoughtNoBranching point thought number
branch_idNoBranch identifier
needs_more_thoughtsNoIf more thoughts are needed
current_stepNoCurrent step recommendation
previous_stepsNoSteps already recommended
remaining_stepsNoHigh-level descriptions of upcoming steps

TDQS

A3.9/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes the tool's dynamic nature (e.g., adjusting thoughts, revising, branching), its role in MCP tool coordination, and expected behaviors like hypothesis generation and verification. However, it lacks details on error handling, performance limits, or authentication needs, which are minor gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is overly verbose and repetitive, with sections like 'Parameters explained' and 'You should' that could be condensed. While well-structured with clear headings, it includes redundant information (e.g., repeating tool features in multiple sections), reducing efficiency. Every sentence adds value, but many could be more concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's high complexity (13 parameters, nested objects, no output schema, and no annotations), the description is exceptionally complete. It covers purpose, usage, features, parameter explanations, and detailed instructions, providing all necessary context for an agent to understand and invoke the tool correctly without relying on structured fields.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 100% schema description coverage, the description adds significant value by explaining parameter semantics in detail. It provides context for each parameter (e.g., 'thought' can include revisions, questions, hypotheses; 'current_step' includes tool recommendations with rationale), clarifies usage patterns, and offers examples, going well beyond the schema's basic descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tautological: description restates name/title.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit 'When to use this tool' with 8 bullet points covering scenarios like complex problems, planning with revision, unclear scope, multi-step solutions, and tool guidance. It also includes a 'You should' section with 15 detailed instructions on how to use the tool effectively, offering comprehensive guidance on when and how to apply it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev1.0.0
    • Changedsequentialthinking_tools7 fields changed
      • addedInput schema / $schema
        Added value: +"http://json-schema.org/draft-07/schema#"
      • changedInput schema / properties / branch_from_thought / type
        Previous value: -"integer"New value: +"number"
      • addedInput schema / properties / current_step / properties / recommended_tools / items / properties / suggested_inputs / additionalProperties
        Added value: +{}
      • addedInput schema / properties / previous_steps / items / properties / recommended_tools / items / properties / suggested_inputs / additionalProperties
        Added value: +{}
      • changedInput schema / properties / revises_thought / type
        Previous value: -"integer"New value: +"number"
      • changedInput schema / properties / thought_number / type
        Previous value: -"integer"New value: +"number"
      • changedInput schema / properties / total_thoughts / type
        Previous value: -"integer"New value: +"number"
  2. 1 tool update
    • First observedsequentialthinking_tools

TDQS

A3.8/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap with other tools. The tool 'sequentialthinking_tools' has a singular, clearly defined purpose for dynamic problem-solving, so an agent cannot misselect between non-existent alternatives.

Naming Consistency5/5

Since there is only one tool, naming consistency is inherently perfect. The tool name uses a consistent snake_case format, and there are no other tools to compare it against, so no inconsistencies can arise.

Tool Count2/5

A single tool is too few for the server's stated purpose of facilitating sequential thinking with MCP tool coordination. The tool description implies a need for interaction with multiple tools, but the server only provides one meta-tool, which feels thin and limits functionality for the intended scope.

Completeness2/5

The server is severely incomplete for its domain. It lacks direct tools for the actual operations it coordinates (e.g., search, data retrieval, execution), relying solely on a meta-tool for recommendations. This creates a significant gap, as agents cannot perform the underlying tasks without external tools, leading to potential dead ends in workflows.

Maintenance

ActivityMaintained
ResponsivenessWithin a week

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

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/spences10/mcp-sequentialthinking-tools'

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