
Thinkstep
io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Oct 29, 2026
Step-by-step reflective thinking: record, revise, and branch thought chains.
Overview
Local MCP server with one tool that records a step-by-step chain of thoughts, including revisions and named branches, for the session.
- What you can do
- Record one thinking step at a time, with its position in the chain and an estimated total
- Revise an earlier thought while keeping the original in the history
- Fork a named branch from an earlier thought to explore an alternative route
- Get back a JSON summary of the chain: current position, whether more steps are needed, open branch ids and history length
- When to use it
- Useful for multi-step reasoning where a first idea gets contradicted, revisited or split into alternative routes, and you want the thread of revisions and branches kept straight instead of lost in a single pass.
- Requirements
- Runs locally over stdio, either via npx with the npm package or via the Docker image. No accounts, API keys, environment variables or headers are declared. State lives only in the server process for the session.
Installation
In SourceWeft
- Open Thinkstep in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
thinkstep
Think in steps, out loud, with a server keeping the thread.
Some problems do not yield to a single pass. You form a first idea, poke at it, realise the second step contradicts the first, double back, try a different route from an earlier point, and only then see the shape of the answer. thinkstep is the notebook for that process: an MCP server with one tool, sequentialthinking, that records a chain of thoughts one step at a time and keeps the whole history — revisions and side branches included — straight for you.
Each call adds one thought. You say where you are (thoughtNumber), roughly how far you think you have to go (totalThoughts), and whether you need another step. If the chain outgrows your estimate, the server raises the total for you instead of complaining. When a step rethinks an earlier one, flag it as a revision and point at the thought it reconsiders. When you want to explore a different route without losing the main line, fork a named branch from an earlier thought; every response lists the branch ids created so far, so you always know which threads are open.
State lives in the server process for the length of the session. Nothing is written to disk, nothing leaves the machine, and closing the session closes the notebook.
Usage
MCP server
MCP client config:
Docker
The tool
sequentialthinking
Record one thinking step and get back a summary of the chain.
A branch is tracked when a thought carries both branchFromThought and branchId. A revision is recorded with isRevision: true and revisesThought set to the number of the thought it rethinks; the original stays in the history.
Every accepted thought returns a JSON summary:
thoughtNumber/totalThoughts— where the chain stands. IfthoughtNumberexceeds the estimatedtotalThoughts, the total is raised tothoughtNumber.nextThoughtNeeded— whether the chain continues. SendingneedsMoreThoughts: truealso reports this astrue.branches— the id of every branch created so far, in creation order.thoughtHistoryLength— how many thoughts the server has recorded, including this one.
Missing or mistyped fields are refused with an error result (isError) naming the offending field; nothing is recorded for a rejected call.
Development
License
MIT — see LICENSE.
Source: README.md at commit 3c77675
Tools
0Version history
1- v0.1.0LatestOct 29, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts