Sequential Thinking MCP Server by arben-adm: Setup for Claude, Cursor and Other Apps

• Starts a new notes session with a title

  Creates a session to hold the notes for one task. Each write carries a request ID, so a repeated call does not create a duplicate.

  Try: “Start a notes session called 'Choose a local database'.”

  Write · create_session

• Adds a note to a session

  Saves one note, tagged as a note, observation, evidence, assumption, option, risk, decision or next action. A note can replace an earlier one or start a named branch.

  Try: “Add a decision to the session: use SQLite for storage.”

  Write · add_step

• Finds sessions by title or status

  Lists saved sessions so you can find one again after a restart, for example when you lost its ID.

  Try: “Find my session about the database choice.”

  Read · list_sessions

• Reads back a session's notes

  Shows the active notes with decisions first, or the full history with filters. Long sessions come back in pages.

  Try: “Resume my 'Choose a local database' session and tell me what is still open.”

  Read · read_session

• Closes a session with a stored outcome

  Saves the final outcome and the IDs of the notes that support it. No more notes can be added afterwards.

  Try: “Finalize the session with the outcome 'SQLite chosen' and link the decision note.”

  Write · finalize_session

• Deletes a session's records from the database

  Removes one session's rows from the local database. Exports and backups you made earlier stay, and the README says this is not secure erasure.

  Try: “Delete the finished 'Old planning' session.”

  Delete · delete_session

• Writes a session to a JSON file

  Saves one session as an archive file inside the exports folder under the storage directory. Paths outside that folder are rejected.

  Try: “Export the database-choice session to db-choice.json.”

  Write · export_session

• Loads a session from an exported file

  Reads an archive from the exports folder and adds it as a session. Without a session ID it replaces the old single shared history instead.

  Try: “Import db-choice.json from the exports folder.”

  Delete · import_session

• Legacy: records one numbered step of reasoning

  Older tool that stores a numbered note with a stage such as Research or Analysis in one shared history. It is marked deprecated in favor of sessions.

  Try: “Record step 1 of 5 in the Research stage.”

  Write · process_thought

• Legacy: summarizes the shared history

  Builds a deterministic summary of the legacy history from the recorded notes, with excerpts per stage and open branches. It does not create new reasoning.

  Try: “Summarize the legacy notes recorded so far.”

  Read · generate_summary

• Legacy: erases the shared history

  Deletes every record in the single legacy session and reports how many were removed. Exports and backups stay.

  Try: “Clear the legacy thought history.”

  Delete · clear_history

Watch out for

• Notes are saved as plain text on disk

  Anything the assistant writes lands unencrypted in a SQLite file. Keep passwords and keys out of your notes, or run with the memory-only flag. github.com

• It can delete saved notes

  delete_session and clear_history remove only the notes this server stored in its own local database. They cannot touch other files or systems. The README says deletion is not secure erasure, and exports and backups are kept. Export first if you need a copy. github.com

• Import replaces the old shared history

  import_session without a session ID replaces the legacy history. Files must sit in the exports folder under the storage directory. github.com

• Web modes are experimental and local by default

  The server uses stdio by default. The sse and streamable-http options bind to 127.0.0.1 and need an extra flag to listen elsewhere, with no sign-in. github.com

Security advisories