ContextEngine
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONTEXTENGINE_CONFIG | No | Path to a contextengine.json configuration file. If set, overrides auto-discovery. | |
| CONTEXTENGINE_WORKSPACES | No | Comma-separated list of workspace directories to scan. 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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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, with their status (found/missing) and chunk counts. |
| 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. |
| 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. Parses headings, bullets, and tables to extract operational rules. Supports: (1) Structured Markdown (H2=category, H3=rule, bullets=context), (2) Inline bullets with [category] prefix, (3) JSON arrays of {category, rule, 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
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 21 tools
Most tools have clearly distinct purposes, but there is slight overlap between check_ports (port-only scan) and run_audit (includes port checks), and between activate vs activation_status (one to activate, one to check status). Overall, descriptions help disambiguate.
Tools predominantly follow a verb_noun pattern (e.g., list_learnings, save_session). However, activation_status and drift_status use noun_noun, deviating from the pattern. Overall, the convention is mostly consistent and readable.
With 21 tools, the count is on the higher end of reasonable. The scope covers licensing, project management, knowledge bases, sessions, and audits, justifying many tools, but it feels slightly heavy compared to the typical ideal of 3-15.
The tool surface covers core workflows: CRUD for learnings and sessions, project analysis, audit, search, and licensing. Minor gaps exist (e.g., no explicit update for knowledge sources), but in-place updates handle many cases. Overall, it is well-rounded.