Sequential Thinking MVP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP server port | 3000 |
| NODE_ENV | No | Environment (development/production) | |
| ALLOWED_ORIGINS | No | Comma-separated list of allowed CORS origins (default: all in dev, none in prod) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sequential_thinkingC | Facilitates a detailed, step-by-step thinking process for problem-solving and analysis. Break down complex problems into manageable steps, revise and refine thoughts as understanding deepens, and branch into alternative paths of reasoning. |
| get_thought_sequenceC | Retrieves the complete sequence of thoughts for the current or specified session |
| get_thought_branchC | Retrieves a specific branch of alternative reasoning paths |
| reset_thinking_sessionB | Starts a new thinking session, clearing the current thought sequence |
| get_session_summaryC | Gets a summary of the current or specified thinking session |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
The tools have overlapping purposes that could cause confusion. get_session_summary, get_thought_sequence, and get_thought_branch all retrieve session-related data, with unclear boundaries between summary, sequence, and branch. sequential_thinking is distinct as it facilitates the thinking process, but the retrieval tools are ambiguous.
Tool names follow a consistent verb_noun pattern, with all using snake_case. However, sequential_thinking deviates slightly by using an adjective-noun format instead of a verb, which is a minor inconsistency in an otherwise predictable naming scheme.
With 5 tools, the count is well-scoped for a thinking session server. This number is appropriate for managing sessions, retrieving data, and facilitating thinking processes, with each tool earning its place without feeling too heavy or thin.
The tool surface covers core CRUD-like operations for thinking sessions: create (reset_thinking_session), read (get_* tools), and process (sequential_thinking). A minor gap exists in update or delete operations for sessions or thoughts, but agents can work around this with resets.