Data as of

mcp-sequentialthinking-tools for Cursor: Setup & Config

Cursor: mcp-sequentialthinking-tools records stepwise reasoning with session history, branches, and revision metadata.

What you can do with mcp-sequentialthinking-tools in Cursor

Pick it for inspectable session-based planning with honest, limited tool-name validation.

  • Validate proposed tool names against an explicitly supplied list
  • Inspect or clear history during a long agent workflow

Before you start: mcp-sequentialthinking-tools in Cursor

  • npx
  • An MCP-compatible client

The history limit is per session and defaults to 1000. Its stdio transport accepts Content-Length framing and newline-delimited JSON used by older tmcp tooling.

mcp-sequentialthinking-tools Cursor configuration

  1. Choose Cursor configuration scope

    For mcp-sequentialthinking-tools, open Project: .cursor/mcp.json User: ~/.cursor/mcp.json. Merge into mcpServers at project or user scope.

  2. Add mcp-sequentialthinking-tools to Cursor

    Use the mcp-sequentialthinking-tools entry below in mcpServers. Keep mcp-sequentialthinking-tools's documented stdio connection fields and your other Cursor entries.

  3. Check mcp-sequentialthinking-tools in Cursor

    mcp-sequentialthinking-tools: Enable in Cursor’s MCP settings; inspect tools.

Config file · Project: .cursor/mcp.json

User: ~/.cursor/mcp.json

JSON
{
  "mcpServers": {
    "mcp-sequentialthinking-tools": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-sequentialthinking-tools"
      ],
      "env": {
        "MAX_HISTORY_SIZE": "<maximum recorded steps per session; default 1000>"
      }
    }
  }
}

mcp-sequentialthinking-tools tools available to Cursor

mcp-sequentialthinking-tools's stored tool list documents 3 tools; compare it with Cursor's connected tool list, because the stored list is not a live check.

sequentialthinking_tools

Find sequentialthinking_tools under mcp-sequentialthinking-tools in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Record one reasoning step and optionally validate model-proposed tools against a supplied list.

get_thinking_history

Find get_thinking_history under mcp-sequentialthinking-tools in Cursor's MCP settings; inspect its arguments when the agent requests a call.

clear_thinking_history

Find clear_thinking_history under mcp-sequentialthinking-tools in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Delete one session history or clear all session histories.

mcp-sequentialthinking-tools: full stored tool descriptions

Troubleshooting mcp-sequentialthinking-tools in Cursor

  • Cursor must find npx mcp-sequentialthinking-tools (Node.js/npm) for mcp-sequentialthinking-tools. Enable the project/user entry in MCP settings and inspect its tools.
  • Review MAX_HISTORY_SIZE for mcp-sequentialthinking-tools before sharing project .cursor/mcp.json; project scope travels with the repository.
  • mcp-sequentialthinking-tools uses stdio here: Cursor must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
  • Known limitation: Does not discover available tools or select tools for the model
  • Known limitation: Adds unnecessary overhead for trivial requests
  • Known limitation: Text filtering is not a guarantee against adversarial input
  • General Cursor troubleshooting lives in the /clients/cursor guide.

mcp-sequentialthinking-tools — details. Cursor guide

Frequently asked questions

Cursor's mcp-sequentialthinking-tools entry belongs under mcpServers in .cursor/mcp.json (project) or ~/.cursor/mcp.json (user). Confirm the active scope in MCP settings.

Cursor's mcp-sequentialthinking-tools example uses stdio.

mcp-sequentialthinking-tools's Cursor configuration invokes npx mcp-sequentialthinking-tools (Node.js/npm).

Cursor's mcp-sequentialthinking-tools example references MAX_HISTORY_SIZE. Check these names if startup or authentication fails; the example alone does not distinguish required from optional values.

mcp-sequentialthinking-tools's stored list contains 3 tools, including sequentialthinking_tools, get_thinking_history, clear_thinking_history. Compare those names with Cursor's connected tool list; the stored list is not a live check.

Yes. session_id selects a history bucket, with default used when no session is provided.

No. The README says filtering is defensive rather than guaranteed and instructs users not to include secrets.