Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SCAR_TISSUE_DIRNoExplicitly specifies the storage path for ScarTissue on the server side. If unset, the MCP Server automatically detects the Git repository root and uses <git-root>/.scartissue.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Before editing any file, ALWAYS call check_scar_tissue(target_file, planned_change) to check if your planned approach matches a previously reverted dead end. Whenever a git revert happens or a test fails 3 times before succeeding, call record_dead_end to immunize future sessions.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
record_dead_endC

Record a proven dead-end code change (Anti-Memory / Scar Tissue).

Extracts {attempted_change + error_root_cause + dead_end_approach + safe_pivot}, encodes a 16-dimensional latent scar vector (Memorilla-inspired gatekeeper), and compiles a strictly <= 50 character Contrastive Pivot redline alert.

check_scar_tissueA

Mandatory pre-edit Gatekeeper: Check historical dead ends before modifying target_file.

Instead of dumping thousands of lines of CLAUDE.md history into the context window, returns strictly <= 50-char high-priority redline alerts ONLY when the target file, symbol, or 16-dim semantic intent matches a historical minefield.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 2 tools

Disambiguation5/5

The two tools are clearly distinct: record_dead_end writes a new scar, while check_scar_tissue reads historical scars. There is no overlap or ambiguity in their purposes.

Naming Consistency5/5

Both names follow a consistent snake_case verb_noun pattern (record_dead_end, check_scar_tissue), making the set predictable and easy to parse.

Tool Count3/5

Two tools is thin for a memory system; while record and check cover the core loop, additional operations like listing or deleting scars would be expected for a robust surface.

Completeness3/5

Core create and query operations exist, but there is no way to list, update, or delete recorded dead ends, leaving notable management gaps that could cause dead ends to become unmanageable.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues