Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PLEACH_HOMENoOverride the directory where pleach stores its data. Defaults to ~/.pleach/.

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
pleach_logA

The Claude Code session branch graph for this project: an ASCII git-style graph plus one record per session (id, name, parent, live, subject, merges), newest first. Start here to see what branches exist.

pleach_showA

Full detail for one session: lineage (parent, branch point, children), transcript path, entry count, merges it took part in, and the command to resume it.

pleach_grepA

Full-text search across session transcripts (conversation text, not tool dumps). Answers 'which branch was the one where we worked out X?'. Returns matching sessions newest-first with snippets.

pleach_exportA

A session's conversation rendered as readable markdown (tool dumps elided). Local and free. Long transcripts are truncated at max_chars; prefer pleach_summary for a whole-branch digest.

pleach_summaryA

Summarize what a branch attempted, what worked, what failed, and what was decided. Cached per branch head; a cache miss makes model calls (small cost, works at any transcript size).

pleach_branchA

Fork a session into a new tracked branch (copies the transcript under a new id, exactly like pleach branch). Returns the new session id and the claude --resume command to start working on it.

pleach_nameB

Label a session; labels show in the graph.

pleach_merge_planA

Dry-run a merge of two branches: branch point, merge-base method and confidence, and the exact prompt the merge agent would get. Dispatches nothing and writes nothing (summaries are computed, cached, small cost). Review this before calling pleach_merge.

pleach_mergeA

SIDE-EFFECTFUL: materializes a merge base and dispatches a background Claude agent to reconcile the two branches (read-only unless allow_writes). Use pleach_merge_plan first and confirm with the user before calling this.

pleach_statusB

What pleach is tracking for this project: session/fork counts, live sessions, observed vs inferred edges.

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/foudrayelias-ALPHA/pleach'

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