Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DISABLE_THOUGHT_LOGGINGNoSuppress stderr thought outputfalse

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
sequential_thinkingA

A detailed tool for dynamic and reflective problem-solving through thoughts. This tool helps analyze problems through a flexible thinking process that can adapt and evolve. Each thought can build on, question, or revise previous insights as understanding deepens.

When to use this tool:

  • Breaking down complex problems into steps

  • Planning and design with room for revision

  • Analysis that might need course correction

  • Problems where the full scope might not be clear initially

  • Problems that require a multi-step solution

  • Tasks that need to maintain context over multiple steps

  • Situations where irrelevant information needs to be filtered out

Key features:

  • You can adjust total_thoughts up or down as you progress

  • You can question or revise previous thoughts

  • You can add more thoughts even after reaching what seemed like the end

  • You can express uncertainty and explore alternative approaches

  • Not every thought needs to build linearly - you can branch or backtrack

  • Generates a solution hypothesis

  • Verifies the hypothesis based on the Chain of Thought steps

  • Repeats the process until satisfied

  • Provides a correct answer

Parameters explained:

  • thought: Your current thinking step, which can include:

    • Regular analytical steps

    • Revisions of previous thoughts

    • Questions about previous decisions

    • Realizations about needing more analysis

    • Changes in approach

    • Hypothesis generation

    • Hypothesis verification

  • nextThoughtNeeded: True if you need more thinking, even if at what seemed like the end

  • thoughtNumber: Current number in sequence (can go beyond initial total if needed)

  • totalThoughts: Current estimate of thoughts needed (can be adjusted up/down)

  • isRevision: A boolean indicating if this thought revises previous thinking

  • revisesThought: If is_revision is true, which thought number is being reconsidered

  • branchFromThought: If branching, which thought number is the branching point

  • branchId: Identifier for the current branch (if any)

  • needsMoreThoughts: If reaching end but realizing more thoughts needed

You should:

  1. Start with an initial estimate of needed thoughts, but be ready to adjust

  2. Feel free to question or revise previous thoughts

  3. Don't hesitate to add more thoughts if needed, even at the "end"

  4. Express uncertainty when present

  5. Mark thoughts that revise previous thinking or branch into new paths

  6. Ignore information that is irrelevant to the current step

  7. Generate a solution hypothesis when appropriate

  8. Verify the hypothesis based on the Chain of Thought steps

  9. Repeat the process until satisfied with the solution

  10. Provide a single, ideally correct answer as the final output

  11. Only set nextThoughtNeeded to false when truly done and a satisfactory answer is reached

deep_planningA

A structured planning tool that manages multi-phase planning sessions. Complements sequential_thinking by tracking planning state while the LLM reasons deeply.

Workflow: init → clarify → explore → evaluate → finalize

  • init: Define the problem, context, and constraints

  • clarify: Record clarifying questions and answers (repeatable)

  • explore: Record approach branches with pros/cons (repeatable)

  • evaluate: Score approaches on feasibility, completeness, coherence, risk (repeatable)

  • finalize: Select best approach and generate structured implementation plan

Each phase returns valid next phases to guide the workflow. Complex fields (pros, cons, steps, risks, constraints) are passed as JSON strings.

Use sequential_thinking for deep reasoning between phases. Use deep_planning to record conclusions and track planning state.

list_plansA

List saved planning sessions and discovered plan files. Supports optional filters:

  • status: "complete" (finalized plans) or "in-progress" (active sessions) — Yggdrasil only

  • keyword: Search in problem/title text (case-insensitive)

  • source: "yggdrasil" (default), "cc" (Claude Code orphans), or "all"

  • limit: Maximum results (default 20, max 50)

  • offset: Skip first N results (default 0)

Returns paginated results sorted by date (newest first).

get_planA

Retrieve a saved deep_planning session by its session ID. Returns the plan in the requested format:

  • "markdown": Rendered Markdown plan (default, only available for finalized plans)

  • "jsonl": Raw JSONL event log (full session history for reconstruction)

promote_planA

Promote a Claude Code plan file to the Yggdrasil plans index. Renames the file to YYYYMMDD-{name}.md format and adds it to the index for unified discovery. Only works on .md files not already tracked in the index.

archive_plansA

Archive old planning sessions by moving files to archive/YYYY/ subdirectory. Default mode is dry run (preview only). Set dryRun to false to execute. Removes archived entries from the Yggdrasil index.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/henrychong-ai/yggdrasil-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server