An MCP server implementation that provides a tool for dynamic and reflective problem-solving through a structured thinking process which automatically writes sequential thinking logs to Recall associated with each thought session.
The Sequential Thinking MCP provides the following capabilities:
IMPORTANT: PRIVATE KEY PROTECTION
This MCP server requires a private key for Recall operations. To protect this sensitive information:
cat .env
)chmod 600 .env
This server implements several layers of security to keep your private key safe:
[REDACTED]
This MCP server includes integration with Recall, allowing you to store sequential thinking logs securely on-chain. All thinking steps for each query are automatically saved to your Recall bucket.
To use the Recall integration, you need to provide the following environment variables:
RECALL_PRIVATE_KEY
(required): Your Recall private keyRECALL_NETWORK
(optional): The network to connect to (testnet or mainnet, defaults to testnet)RECALL_BUCKET_ALIAS
(optional): The alias for the bucket where logs will be stored (defaults to 'sequential-thinking-logs')RECALL_LOG_PREFIX
(optional): The prefix for log files stored in the bucket (defaults to 'sequential-')Each thought is stored individually with its metadata, and complete thinking sessions are stored when finished. This allows you to:
The Sequential Thinking MCP server uses the following order of precedence for environment variables:
shell
npm install
The recommended approach is to provide environment variables directly in your Cursor or Claude Desktop configuration. This is more secure and eliminates the need for a .env file.
If you prefer to use a .env file, or are running the server directly without Cursor/Claude, you can create one:
.env
file with your private key:RECALL_PRIVATE_KEY=your_private_key_here
RECALL_NETWORK=testnet
RECALL_BUCKET_ALIAS=sequential-thinking-logs
RECALL_LOG_PREFIX=sequential-
shell
chmod 600 .env
Note: The private key can be provided with or without the "0x" prefix - both formats work.
The server exposes the following MCP tools:
Tool Name | Description | Parameters |
---|---|---|
sequentialthinking |
Process step-by-step thinking and store in Recall | thought : String, nextThoughtNeeded : Boolean, thoughtNumber : Integer, totalThoughts : Integer, plus optional parameters |
recallstatus |
Get the status of the Recall integration | check : Boolean |
listsessions |
List all sequential thinking sessions | includePortalLinks? : Boolean |
getsession |
Get a specific thinking session | key : String |
Facilitates a detailed, step-by-step thinking process for problem-solving and analysis.
Inputs:
thought
(string): The current thinking stepnextThoughtNeeded
(boolean): Whether another thought step is neededthoughtNumber
(integer): Current thought numbertotalThoughts
(integer): Estimated total thoughts neededisRevision
(boolean, optional): Whether this revises previous thinkingrevisesThought
(integer, optional): Which thought is being reconsideredbranchFromThought
(integer, optional): Branching point thought numberbranchId
(string, optional): Branch identifierneedsMoreThoughts
(boolean, optional): If more thoughts are neededOutput: When the final thought is submitted (nextThoughtNeeded
= false), the tool returns:
recallInfo
with:txHash
: The transaction hash on the Recall networksuccess
: Whether storage was successfulkey
: The session file nameviewUrl
: A direct link to view the session in the Recall portalGet the status of the Recall integration.
Inputs:
check
(boolean): Set to true to check the statusOutput:
List all sequential thinking session objects stored in your Recall bucket.
Inputs:
includePortalLinks
(boolean, optional): Whether to include portal links for each sessionOutput:
Retrieve the contents of a specific sequential thinking session file.
Inputs:
key
(string): The key/filename of the session to retrieveOutput:
The Sequential Thinking tool is designed for:
npm run build
npm run start
npm run dev
When developing the MCP server, use console.error()
instead of console.log()
for all debugging and logging. The Claude Desktop app communicates with the server via stdout, so any console.log()
statements will interfere with this communication and cause JSON parsing errors.
To add this MCP server to Cursor:
npm run build
Sequential Thinking MCP
(or any name you prefer)command
node
/path/to/sequential-thinking-recall/dist/index.js
(replace with your actual path)RECALL_PRIVATE_KEY
: Your private key (with or without "0x" prefix)RECALL_NETWORK
: testnet
(or mainnet
if needed)RECALL_BUCKET_ALIAS
: sequential-thinking-logs
RECALL_LOG_PREFIX
: sequential-
For more security, you can configure Cursor via the .cursor/mcp.json
file in your home directory:
{
"mcpServers": {
"sequential-thinking-mcp": {
"command": "node",
"args": [\
"/Users/yourusername/sequential-thinking-recall/dist/index.js"\
],
"env": {
"RECALL_PRIVATE_KEY": "your-private-key-here",
"RECALL_NETWORK": "testnet",
"RECALL_BUCKET_ALIAS": "sequential-thinking-logs",
"RECALL_LOG_PREFIX": "sequential-"
}
}
}
}
This approach eliminates the need for a .env file.
To add this MCP server to Claude Desktop:
npm run build
~/Library/Application Support/Claude/claude_desktop_config.json
%APPDATA%\Claude\claude_desktop_config.json
~/.config/Claude/claude_desktop_config.json
claude_desktop_config.json
file with the following content:json
{
"mcpServers": {
"sequential-thinking-mcp": {
"command": "node",
"args": [\
"/path/to/sequential-thinking-recall/dist/index.js"\
],
"env": {
"RECALL_PRIVATE_KEY": "your-private-key-here",
"RECALL_NETWORK": "testnet",
"RECALL_BUCKET_ALIAS": "sequential-thinking-logs",
"RECALL_LOG_PREFIX": "sequential-"
}
}
}
}
4. Replace /path/to/sequential-thinking-recall/dist/index.js
with the full path to your compiled server file
- Example: /Users/username/sequential-thinking-recall/dist/index.js
5. For the RECALL_PRIVATE_KEY
, you can provide it with or without the "0x" prefix - both formats work
6. Save the configuration file and restart Claude Desktop
This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.
An MCP server that enables dynamic, reflective problem-solving by structuring thought processes and automatically logging each session to Recall.
No releases published
No packages published