Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GHOSTLINK_LOGNoControls audit logging. Values: 'stdout' (default, writes JSONL to stderr), 'file' (writes to logs/ghostlink.jsonl, auto-rotates at 10MB), or 'off' (no logging).stdout
GHOSTLINK_REPO_ROOTYesThe absolute path to the repository root that GhostLink will expose.

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
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
repo.searchA

Search repo files using ripgrep with output caps and deterministic ordering

repo.read_fileA

Read a file from the repository with size and binary guards

repo.apply_patchA

Apply a unified diff patch with validation, sandbox enforcement, and rollback

repo.runA

Run a curated command (test, lint, typecheck, build, smoke) with allowlisted args

git.statusA

Get normalized git status with branch info, ahead/behind, and file entries

git.diffA

Get diff output for staged or unstaged changes with optional path filtering

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: repo.search scans file contents, repo.read_file reads individual files, repo.apply_patch modifies files, repo.run executes allowed commands, git.status reports repository state, and git.diff shows changes. There is no functional overlap or ambiguity between them.

Naming Consistency5/5

All tool names follow the consistent pattern of a namespace prefix (repo or git) plus a verb or noun phrase in snake_case, such as repo.read_file and git.status. This uniform convention makes the toolset predictable and easy to navigate.

Tool Count5/5

The server contains exactly 6 tools, which is well within the ideal range for a focused toolset. Each tool addresses a distinct need in repository inspection and git operations, without unnecessary bloat or fragmentation.

Completeness4/5

The toolset covers the core operations of searching, reading, modifying, and running commands in a repository, plus git status and diff for change inspection. It lacks explicit commit or branch management, but those are outside the apparent scope, so the gap is minor and workable.

Maintenance

ActivitySlowing
ResponsivenessNo issues