Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CONTEXTENGINE_CONFIGNoPath to a contextengine.json configuration file. If not set, ContextEngine auto-discovers configuration from ./contextengine.json or ~/.contextengine.json.
CONTEXTENGINE_WORKSPACESNoColon-separated list of workspace directories to scan for projects. Overrides the 'workspaces' setting in the configuration file. Default is ~/Projects.

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
search_contextA

Search across all indexed project knowledge (copilot-instructions, skills docs, runbooks, session docs). Uses hybrid BM25 keyword + semantic search with temporal decay. Returns the most relevant chunks with source file, section, and line numbers.

list_sourcesA

List all knowledge sources indexed by ContextEngine, each with a one-line summary (from the file's own head: frontmatter description, title plus first sentence, or module docstring), status (found/missing) and chunk counts. Read the summary to pick the right source before calling read_source.

read_sourceA

Read the full content of a specific knowledge source by name.

reindexA

Force a full re-index of all knowledge sources. Use after adding new files or changing contextengine.json.

list_projectsA

Discover and analyze all projects in the workspace. Shows tech stack (framework, runtime, key dependencies), infrastructure (git, docker, pm2), and git remote status for each project. Requires Pro license.

check_portsA

Scan all projects for port declarations (ecosystem.config.js, docker-compose.yml, .env, package.json) and detect port conflicts. Returns a port allocation map with conflict warnings. Requires Pro license.

run_auditB

Run the Compliance Agent audit across all projects. Checks: port conflicts, git remotes (origin + gdrive), git hooks (post-commit auto-push), .env files (existence + gitignore), Docker config (restart policy, workdir), PM2 config (treekill, kill_timeout, no bash wrappers), version issues (EOL runtimes, outdated deps, MUI v4/v5 coexistence). Returns a structured plan with findings and remediation steps.

score_projectA

Score one or all projects on AI-readiness (0-100%). Checks documentation (copilot-instructions, README, CLAUDE.md, .cursorrules, SKILLS.md, .env.example), infrastructure (git, hooks, Docker, CI, deploy scripts, PM2), code quality (tests, TypeScript, linting, npm scripts), and security (.env gitignored, secrets exposure, lockfiles). Returns letter grade (A+ to F) with detailed breakdown.

save_sessionA

Save a key-value entry to a named session. Use to persist decisions, context, plans, and findings between coding sessions. Each session can hold multiple keys (e.g., 'summary', 'active_tasks', 'decisions'). Keys are updated in place if they already exist.

load_sessionA

Load a previously saved session by name. Returns all stored key-value entries with timestamps. Use at the start of a session to restore context from a previous conversation.

list_sessionsA

List all saved sessions. Shows session names, entry counts, and timestamps. Use to discover what context is available from previous conversations.

delete_sessionA

Delete a saved session by name. Returns success/not-found. Use for cleanup of stale or obsolete session context.

audit_verifyA

Verify the integrity of the local audit log chain. Returns OK + record count, or BROKEN + break index when a record has been edited or the chain otherwise diverges. Produces evidence aligned with SOC 2 CC7.2 (change monitoring) and ISO 27001 A.12.4.1 (event logging) — evidence artifacts, not a certification (OpsContext is not itself SOC 2– or ISO 27001–certified; see docs/compliance/). The audit log lives at ~/.contextengine/audit.log and records every state-changing operation (learning save/delete/import, session save/delete, activation activate/deactivate) as a hash-chained JSONL line.

agent_costA

Multi-agent cost report from Claude Code's own transcripts on this machine: tokens moved (cache read/write, fresh input, output), valued cost at API list prices (marked NOTIONAL on a subscription, UNPRICED when no rate matches), capacity intensity (subagents, failed, died at window, tool calls per agent, cache reuse), top runs, and context_burn / fanout_without_canary signals. Call it after a fan-out to read what it consumed, or before one to compare with the last. Thresholds come from .contextengine/policy.json agent_cost, else built-in defaults.

drift_statusA

Returns active drift / loop / stuck-tool / fabrication / silent-failure signals detected over the recent audit-log window. Use to self-check before starting a major task phase. If any 'critical' signal is active (fabrication_suspect or silent_failure), pause and surface to the human.

end_sessionA

MUST be called before ending any coding session. Checks all project repos for uncommitted changes, verifies documentation freshness (copilot-instructions.md, SKILLS.md, session docs), and returns a checklist of required actions. Will report PASS/FAIL for each check. The AI agent should resolve all FAIL items before ending.

save_learningA

Save a permanent operational rule learned during a coding session. Unlike sessions (ephemeral), learnings persist forever and auto-surface in search_context results so AI agents don't repeat mistakes. Duplicate rules (same category + rule text) are updated in place.

list_learningsA

List all permanent learnings, optionally filtered by category. Shows operational rules that have been discovered across sessions. Use search_context to find learnings by keyword — they're automatically included in search results.

delete_learningA

Delete a learning by its ID. Use list_learnings first to find the ID of the learning you want to remove.

import_learningsA

Bulk-import learnings from a Markdown or JSON file. By default only MARKED learnings are imported: inline bullets with a [category] prefix, anything inside a *LEARNINGS.md file, anything under a heading that says learnings / lessons / gotchas / rules, and JSON arrays of {category, rule, context}. Set permissive=true to also import every H3 heading, bold bullet and table row (H2=category, H3=rule, bullets=context). Deduplicates against existing learnings.

activateA

Activate a ContextEngine Pro license to unlock premium tools (score_project, run_audit, check_ports, list_projects, HTML reports). Get a license at https://api.compr.ch/contextengine/pricing

activation_statusA

Check current ContextEngine license status, plan, and available premium tools.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 22 tools

Disambiguation4/5

Tools cluster into clear domains (sessions, learnings, knowledge sources, project audit, monitoring) and most have a single obvious purpose. Minor overlap exists between run_audit and score_project, and between end_session and drift_status, but the descriptions are specific enough to prevent serious misselection.

Naming Consistency4/5

Most tools follow a snake_case verb_noun pattern (list_sources, save_session, delete_learning, score_project), making the set predictable. A few names break the pattern—audit_verify, agent_cost, drift_status, activation_status—but these are still readable and not chaotic.

Tool Count3/5

At 22 tools, the surface is on the heavy side and spans many distinct domains: knowledge, sessions, learnings, project audit, compliance, and licensing. The breadth is defensible, but the count lands in the 16-25 range that feels heavy for an agent to navigate.

Completeness4/5

Sessions and learnings have full create/read/update/delete coverage, and knowledge sources support list/read/search/reindex. Minor gaps exist—no direct tool for adding or removing knowledge sources and no remediation application for audit findings—but agents can work around them via files and reindexing.

Maintenance

ActivityMaintained
ResponsivenessNo issues