Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
BOLT_REGISTRY_DIRNoOverrides the global local registry directory (default is path.join(os.homedir(), '.bolt-mcp', 'registry')) for isolated tests or another local catalog.

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

Tools

Functions exposed to the LLM to take actions

NameDescription
bolt_init_ledgerC

Audit: initialize the three-bucket rules and declared plumbing slots. Existing ledgers are preserved.

bolt_surgical_harvestC

Harvest explicit paths from a local directory or sparse Git clone, preserving licenses and SHA-256 provenance.

bolt_scaffold_adapterB

Generate an isolated JS/TS/Python adapter and real contract tests. Both schemas need paired examples; select a callable vendor export.

bolt_audit_seamsC

Check vendor imports, cross-slot coupling, unfinished boundaries, provenance, and banned literal patterns. Record actionable seam tickets and vendor security_notices.

bolt_verify_slotC

Audit then run the live contract with timeout and bounded logs. Secrets are scrubbed; node-permission restricts generated Node contracts to project/temp filesystem roots. Custom shell commands require clean-env.

bolt_registry_promoteB

Copy an unchanged VERIFIED component to the local immutable registry under a new slug.

bolt_registry_search_mountB

Search the local catalog; optionally mount one result into a declared PENDING slot and rerun its contract.

Prompts

Interactive templates invoked by user choice

NameDescription
bolt-and-buildThe six-stage surgical bolt-in workflow

Resources

Contextual data attached and managed by the client

NameDescription
current-ledgerThe most recently used project ledger
registry-catalogLocal component registry catalog

TDQS

B3.3/5.0

Scored across 7 tools

Disambiguation4/5

Most tools map to clearly distinct lifecycle steps: ledger initialization, harvesting, scaffolding, static auditing, live verification, registry promotion, and registry search/mount. Some boundary blur exists because bolt_verify_slot includes an audit step and bolt_registry_search_mount can rerun contracts, overlapping slightly with bolt_audit_seams and bolt_verify_slot. Descriptions still make the intended selection clear.

Naming Consistency4/5

All names use a consistent snake_case `bolt_` prefix and are readable. Most follow an action/object pattern, but the registry tools use a resource-first ordering (`registry_promote`, `registry_search_mount`), which is a minor deviation rather than a real inconsistency.

Tool Count5/5

Seven tools is well scoped for this workflow and each tool represents a meaningful stage in the adapter lifecycle. There are no obviously redundant or filler tools.

Completeness4/5

The surface covers the main lifecycle from ledger initialization and harvesting through scaffolding, auditing, verification, promotion, and registry search/mount. Minor gaps exist around explicitly inspecting ledger/slot status or removing/unmounting registry entries, but core workflows are represented.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues