Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
VAULT_PATHNoPath to knowledge vault~/Vaults/ai
MAX_INJECT_TOKENSNoMax tokens for context injection1500
SESSION_TTL_HOURSNoSession heartbeat TTL2

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}
prompts
{}
resources
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
readA

Read a file or directory listing from the AI knowledge vault.

writeC

Write or append to a file in the AI knowledge vault.

searchB

Full-text search (SQLite FTS5 porter stemming) scoped to this project. Structured mode still matches frontmatter.

project_contextB

Get the context document for a project. Auto-detects project from CWD if not specified.

generate_contextA

Scan a git repo and generate a draft context.md. Returns the draft — does NOT write to vault. Human reviews before committing.

decideC

Log an architectural/design decision to the project's decisions directory.

taskB

Manage project tasks. Supports add, list, update, and board (kanban) views. Tasks are stored as individual files in projects//tasks/.

learnB

Capture and query learnings. Learnings persist discoveries across sessions. Stored as individual files in projects//learnings/.

brainstormC

Start or continue a brainstorm document for a project.

sessionA

Register, update, or query active agent sessions for multi-agent coordination. On complete, persists a session note to the vault.

pruneA

Archive or delete stale vault content based on retention policies. Use mode='dry-run' first to preview.

statsB

Show content statistics for a project — file counts, task breakdown, growth monitoring.

resumeA

Get resume context for continuing work — recent sessions, interrupted work, in-progress tasks, suggested next steps. Call this at session start to understand what happened before.

deprecateB

Mark a vault item (ADR, learning, etc.) as deprecated with an optional reason.

initA

Initialize superskill for the current project. Detects stack, indexes the in-repo catalog, builds the project-local knowledge graph, and registers the repo in the vault map for auto-detection. Does not scrape skills.sh.

statusA

Show superskill knowledge graph state: loaded skills, weights, recent sessions.

telemetryA

Local, opt-in rule-selection telemetry: status/enable/disable/report/clear. Mutations require explicit user authorization and confirm=true. Events never leave the machine; prompts are stored only as truncated hashes.

registerA

Map a repo to a vault project so vault-backed commands auto-detect the slug (writes the vault project-map.json locator; project knowledge stays jailed under projects//).

doctorB

One-shot health check: install vs running MCP servers, vault + project mapping, project graph isolation (must stay gitignored/project-local), rules catalog, compile toolchains, telemetry, MCP clients.

superskillB

Route a task to curated in-repo packs and verified rules selected by language, keywords, symbols and file hints. Phase selects methodology packs and budget, not individual rule eligibility. Does not scrape skills.sh or execute plan flows/gates.

skill_installA

Install skills from a GitHub repo (e.g. owner/repo or full URL). Resolves the skill list and gen/socket/snyk audits via skills.sh; fail-audit skills are blocked, and the unaudited GitHub fallback is used only when skills.sh is unreachable.

skill_validateA

Validate a native skill file against Anthropic or portable requirements without modifying it.

skill_list_installedA

List skills installed locally from GitHub repos.

skill_removeA

Remove an installed skill by name.

linkA

Create a forward link between two vault notes. Appends a [[wikilink]] to the source note, enabling graph_related to discover the connection.

extractB

Extract decisions, learnings, or other items from a source document into individual vault files. Each extracted item gets its own file with a backlink to the source.

graph_relatedA

Related notes via the FTS/edge index (related frontmatter + wikilinks), jailed to this project.

graph_traverseA

Traverse the project index without loading bodies. node|children return metadata; resolve finds relevant notes, skills, rules, files and symbols with size estimates; open retrieves one file or symbol span capped at 4096 UTF-8 bytes by default.

knowledge_rebuildA

Rebuild this project's SQLite FTS5 + edges index from markdown. Source of truth stays the files.

knowledge_vizC

Write architecture notes and code notes (Obsidian-native markdown) and rebuild the project index.

graph_cross_projectB

Search the current project's vault only. Cross-project search is denied.

snapshot_repo_stateB

Snapshot current git state (branch, dirty files, last commit) into the vault. Helps avoid repeating repo discovery across sessions.

env_factsA

Store and query stable environment facts for a project (e.g., auth backend, env file locations, local URLs, required env vars). Not for secrets — use cred_refs for that.

cred_refsB

Store pointers to where credentials are documented (not the credentials themselves). E.g., 'Django admin creds are in tests/live/test_all_endpoints.py'.

rollbackB

Manage rollback checkpoints. Store commit hashes with purpose/scope so rollback is safer. Mark when follow-up work starts after a checkpoint.

captureB

Batch-capture multiple insights from a conversation into individual vault items. Each item gets its own file with auto-numbering. Supports any content type (learning, decision, adr, prd, research, etc.).

templateA

Get pre-filled templates for common vault item types (adr, prd, decision, learning, spec, rfc, roadmap, competitive-analysis, incident, research, vision, strategy). Use to scaffold new documents.

specA

Manage deterministic plan specs. Actions: create, status, approve, freeze, list. Specs use a fixed skeleton (goal, non-goals, constraints, context, files, acceptance, risks, rollback). Approve requires zero gaps; freeze pins a content hash and makes the spec immutable.

ticketsB

Manage tickets derived from a frozen spec. Actions: create, list, board, ready, update. Tickets carry acceptance criteria, blocked_by, a requires_review flag, and an evidence slot. ready returns unblocked tickets in deterministic topological order.

evidenceB

Record and read ticket evidence. Actions: add, list. Evidence is appended to projects//evidence/.jsonl with command, exit code, truncated output, commit, and timestamp.

gateA

Deterministic evidence gate. Checks a spec (fields complete, frozen, hash intact) or a ticket (acceptance present, spec frozen and unchanged, evidence recorded at HEAD, review evidence when required). Returns pass/fail with the missing items.

impactA

Deterministic code-graph impact for a file or symbol: EXTRACTED definitions, importers, INFERRED callers, and the shortest graph path to a second target. Read-only; no LLM.

claimsA

Verify structured claims against a deterministic code-graph scan of a root (default cwd). Kinds: file-exists {path}, symbol-exists {name,file?}, symbol-exported {name,file}, import-resolves {from,specifier}, no-other-importers {file}, no-other-callers {symbol,file?}. Returns verified|refuted|unverifiable with node ids and edge confidence; hard verdicts require EXTRACTED facts.

worktree_envA

Resolve shared-cache environment variables for the current git worktree (cache dirs + hit-enabling flags). Use before running installs/builds in a worktree.

worktree_auditA

Read-only audit of git worktrees and build-cache duplication for this repo. Reports safety verdicts and recommendation items. Never deletes anything.

worktree_statusB

Worktree cache status: policy/hook state, per-worktree safety, cache bytes, optional budget check.

worktree_activateA

Install the shared build-cache policy for this repo: policy file in .git/superskill, guarded post-checkout hook, and host session hooks. Call with confirm=false first to preview; only pass confirm=true after the user agrees. Nothing is ever deleted.

worktree_applyA

Apply selected audit recommendation items (policy/hook/seed/tool-prune) after user consent. Requires confirm=true to mutate; without it returns the plan. Never removes worktrees or user files.

worktree_gcA

Reclaim rebuildable build-cache entries (project-wise or --all). Default is a dry-run report. Mutations require confirm=true; deletions are quarantine-only (reversible via undo). Filters: tool, older_than, newer_than, min_size, max_size, tier, include, exclude, keep_latest, project, all, undo, journal_id, purge.

worktree_uninstallA

Remove worktree-cache integration for this repo: host session hooks, post-checkout hook, policy metadata. Caches are untouched unless purge_local=true AND confirm=true (then this repo's cache namespace is quarantined, still reversible).

hygiene_reportA

Read-only machine-wide space hygiene report across mapped repos: build caches, git worktrees, docker, xcode, and agent scratch. Marks entries that are DUE for cleanup with reasons and exact remediation commands. Reports only — deletes nothing.

watchdogA

Session review + environment optimization. action='dig' analyzes a session, a window of sessions, or the machine environment and returns severity-ranked findings with evidence and proposals (digests for agent reasoning, persisted to the vault as watchdog notes). action='fix' applies approved repairs — dry-run by default; file reclamation is quarantined and reversible. action='status' lists past digs and pending findings.

Prompts

Interactive templates invoked by user choice

NameDescription
inject-project-contextReturns a system prompt fragment with project context, active blockers, open threads, learnings, and the last session.
summarize-sessionReturns a prompt guiding the agent to produce a structured session summary.

Resources

Contextual data attached and managed by the client

NameDescription
Active SessionsActive agent sessions across tools for the current mapped project
Project ContextThe context.md for one project; replace <slug> with the project slug

TDQS

B3.1/5.0

Scored across 52 tools

Disambiguation2/5

Many tools overlap in purpose: capture, extract, learn, decide, task, and brainstorm all store different knowledge artifacts, while status, stats, doctor, telemetry, hygiene_report, watchdog, resume, and session all report on project/session state. Descriptions help somewhat, but an agent faces multiple plausible choices for common actions like recalling context, recording knowledge, or checking health.

Naming Consistency3/5

Naming mixes single-word nouns and verbs (spec, tickets, gate, read, write) with prefixed snake_case families (worktree_*, skill_*, graph_*, knowledge_*). The groupings are readable, but there is no single consistent verb_noun pattern across all 52 tools.

Tool Count1/5

52 tools is far beyond the typical concise MCP surface and exceeds the rubric's 50+ extreme mismatch threshold. Even with broad knowledge, skill, worktree, and hygiene domains, this many tools creates a high selection burden and likely includes low-frequency operations better exposed as actions within fewer multiplexed tools.

Completeness4/5

The surface is extensive and covers most domains it names: vault read/write/search/link/capture/extract, skill install/list/remove/validate, worktree lifecycle, spec/ticket/evidence/gate workflows, graph traversal, and session coordination. Only minor gaps exist, such as explicit edit/delete operations for individual vault notes beyond deprecate/prune, but agents can work around them.

Maintenance

ActivityMaintained
ResponsivenessNo issues