Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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
}
logging
{}
prompts
{
  "listChanged": true
}
resources
{
  "subscribe": false,
  "listChanged": true
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
sessionC

USE WHEN: Session lifecycle (orientation, registry, compaction).

EXAMPLES: session(operation="start", goal="Fix auth bug"); session(operation="compact", summary="Session handoff").

planB

Plan lifecycle: create, list, get, complete, register, graph, or archive_completed.

USE WHEN: managing plan files, marking plans complete, registering roadmap entries, or reading the plan dependency graph (operation="graph"). EXAMPLES: plan(operation="create", ...), plan(operation="graph"), plan(operation="register", ...).

update_memory_bankA

Add/remove roadmap entries and append memory-bank entries.

USE WHEN: You need a single memory-bank mutation entrypoint for roadmap edits (add/remove section entries) or append-style updates for progress, active context, or operations log entries.

DO NOT use this tool for free-form markdown rewrites; Prefer targeted operation modes so validation and sync rules remain enforceable.

EXAMPLES:

  • update_memory_bank(operation="roadmap_add", section="pending", entry_text="- Improve retrieval scoring")

  • update_memory_bank(operation="progress_append", date_str="2026-04-14", entry_text="Implemented typed memory reader")

  • update_memory_bank(operation="log_append", operation_type="fix", title="Resolve docs gate mismatch", summary="Aligned roadmap and progress")

run_quality_gateA

Run Phase A quality gate end-to-end and return full result. Zero args required.

USE WHEN: Running the commit pipeline Phase A quality gate or the Step 12 final gate. Spawns checks as a detached subprocess and polls with heartbeat progress notifications, keeping the MCP stdio connection alive.

Config is read from the pipeline session file written by pipeline_handoff(operation="write", pipeline="commit", phase="checks"). Supported keys: coverage_threshold (float), test_timeout (int), force_fresh (bool), reflection (bool), force_reflection (bool). When reflection is enabled and primary checks pass, a heuristic reflection pass runs; error-level findings set preflight_passed to false.

EXAMPLES:

  • run_quality_gate() before commit Phase A.

  • pipeline_handoff(write, checks, {"force_fresh": true, "test_timeout": 600}) then run_quality_gate() for Step 12 final gate.

run_docs_gateA

Run Phase B docs/memory-bank sync validation. Zero args required.

USE WHEN: Validating that timestamps, roadmap_sync, and memory-bank files are consistent after documentation updates. Called by the commit-docs subagent as a zero-arg alternative to execute_pre_commit_checks(phase="B") (which Cursor's MCP bridge zero-args to Phase A, running tests instead).

RETURNS: JSON with docs_phase_passed (bool), timestamps_result, and roadmap_sync_result. Does NOT run tests or code quality checks.

EXAMPLES:

  • run_docs_gate() after updating memory-bank files via manage_file() in Phase B of the commit pipeline.

  • run_docs_gate() to re-check roadmap_sync and timestamps without re-running tests or other quality checks.

autofixA

Auto-fix formatting, linting, type errors, and markdown lint. Zero args required.

USE WHEN: Phase A fails and automated fixes are needed before re-running checks. Called by commit-checks, commit-final-gate, and implement-code agents after preflight_passed=false. Runs fix_errors, format, type_check, and markdown auto-fix.

INTEGRITY SAFEGUARDS:

  • Do not use this tool output as a "done" signal by itself; always re-run run_quality_gate() and validate changed modules still import cleanly.

  • If a fix iteration introduces new failures/regressions, roll back that attempt and retry with a different approach (max 3 attempts).

EXAMPLES:

  • autofix() immediately after a failing run_quality_gate() call to auto-fix formatting, linting, type, and markdown issues.

  • autofix() inside implement-code or commit-checks agents on the fix path before re-running the quality gate.

compress_memory_bankA

Compress project memory files (CLAUDE.md, .cortex/memory-bank/*.md) to reduce session token cost. Creates .original backups; validates structural integrity before overwriting. Returns per-file compression ratios.

USE WHEN: Attached projects need shorter CLAUDE.md / memory-bank prose after cortex://analysis flags compression candidates, or before long sessions.

DO NOT: Run on source code, tests, or user-facing docs outside memory paths.

EXAMPLES:

  • compress_memory_bank() — zero-arg uses MCP workspace root

  • compress_memory_bank(project_root="/path/to/project")

RETURNS: JSON with status and result (CompressMemoryBankResult fields).

memory_walA

Inspect or manage the memory-bank WAL (JSONL audit log and snapshots).

USE WHEN: You need an audit trail of memory-bank writes, anomaly hints, or a filesystem snapshot/restore of .cortex/memory-bank/*.md (not a git substitute).

DO NOT: Treat WAL as authoritative security auditing; it is best-effort and can be disabled by disk errors (writes still proceed).

EXAMPLES:

  • memory_wal(operation="read") — last 50 WAL entries

  • memory_wal(operation="anomalies") — heuristic warnings

  • memory_wal(operation="snapshot", label="backup-2026-04-15")

  • memory_wal(operation="restore", label="backup-2026-04-15")

Pre-compact automation: there is no bundled Claude PreCompact hook in this repo; run memory_wal(operation="snapshot", label="pre-compact-…") manually before risky compaction if you want a rollback point.

pipeline_handoffA

Structured inter-agent communication for pipeline workflows.

USE WHEN: Orchestrators need to exchange structured data between pipeline phases. Each phase writes its output; the next phase reads it. All data persists in .cortex/.session/{id}/{pipeline}/.

WORKFLOW (simplified):

  1. pipeline_handoff(operation="init", pipeline="commit")

  2. pipeline_handoff(operation="write", pipeline="commit", phase="preflight", data='{"status":"complete","snapshot_ref":"abc123"}')

  3. pipeline_handoff(operation="read", pipeline="commit", phase="preflight") → reads phase data

  4. pipeline_handoff(operation="read", pipeline="commit") → reads full pipeline state (all phases)

  5. pipeline_handoff(operation="clear", pipeline="commit")

EXAMPLES:

  • pipeline_handoff(operation="init", pipeline="commit")

  • pipeline_handoff(operation="write", pipeline="commit", phase="checks", data='{"status":"passed","coverage":0.94}')

  • pipeline_handoff(operation="read", pipeline="commit", phase="checks")

  • pipeline_handoff(operation="read", pipeline="commit")

  • pipeline_handoff(operation="clear", pipeline="commit")

Legacy aliases (write_task, read_task, write_result, read_state) still work.

RETURNS: JSON with {status, ...} for write ops; JSON file content for reads.

Args: operation: init | write | read | read_log | status | mark_running | clear | snapshot | rollback (legacy: write_task, read_task, write_result, read_state) pipeline: Pipeline name (e.g. "commit", "implement"). Default: "default". phase: Phase name (e.g. "preflight", "checks"). Required for write. For read: if given, reads that phase; if omitted, reads full state. data: Payload for write and init. Accepts JSON string or native object. When the JSON includes free-text fields such as context or summary, write compact technical prose (see cortex://rules, Agent-Internal Communication): no filler or hedging; keep file paths and error messages verbatim. paths: Paths to snapshot for operation="snapshot". Can be passed via this argument or via data={"paths":[...]} for arg-stripping clients. snapshot_id: Snapshot id for operation="rollback". Can be passed via this argument or via data={"snapshot_id":"..."}. ctx: MCP context (auto-provided).

thinkA

Append a thought to internal scratchpad.

USE WHEN: Agent needs reasoning before action or multi-step deliberation. EXAMPLES: think(thought="Check constraints"), think(thought="Step 1", thought_number=1, total_thoughts=2, next_thought_needed=True).

Prompts

Interactive templates invoked by user choice

NameDescription
setup_synapseSetup Synapse via Git submodule (always available). Args: synapse_repo_url: URL of Synapse repository (default provided)
setup_codegraphAdd CodeGraph semantic code intelligence to this project. Adds CodeGraph MCP server to .cursor/mcp.json, runs codegraph init, and wires permissions for Claude Code.

Resources

Contextual data attached and managed by the client

NameDescription
get_structure_infoResource: Project structure info. Zero-arg with caching.
health_checkCheck MCP connection health and resource utilization. USE WHEN: User wants connection status, user needs health check, user requests connection health, user wants to monitor MCP server. EXAMPLES: 'check MCP connection health', 'get connection status', 'check server health', 'monitor MCP connection'. DO NOT: - Call this tool in tight loops or as part of every agent turn; it is a diagnostics helper, not a heartbeat. - Treat this as a generic HTTP or infrastructure health check; it reports only on the MCP server connection. RETURNS: JSON with connection status, resource metrics, and health indicators. Args: None. No parameters required. Returns connection health metrics including: - Connection status (healthy/unhealthy) - Current concurrent operations - Maximum allowed concurrent operations - Resource utilization percentage - Available semaphore slots Returns: JSON string with health metrics: { "status": OperationStatus.SUCCESS.value, "health": { "healthy": true, "concurrent_operations": 2, "max_concurrent": 5, "semaphore_available": 3, "utilization_percent": 40.0 } } Example (success): health_check() → {"status": OperationStatus.SUCCESS.value, "health": {"healthy": true, "concurrent_operations": 1, "max_concurrent": 5, "semaphore_available": 4, "utilization_percent": 20.0}} Example (error): health_check() (when MCP disconnected or check fails) → {"status": OperationStatus.ERROR.value, "error": "Connection closed", "error_type": "ConnectionError"}
get_relevant_rulesResource: Rules relevant to current task. Zero-arg — reads task from session config. Falls back to "general coding standards" if no session config exists.
analyzeResource: Run analysis. Zero-arg — reads target from session config. Falls back to "context" if no session config exists. Target must be one of: usage_patterns, structure, insights, context.
validateResource: Run validation. Zero-arg — reads check_type from session config. Falls back to "timestamps" if no session config exists. check_type must be one of: schema, duplications, quality, infrastructure, timestamps, roadmap_sync.
load_context

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/igrechuhin/Cortex'

If you have feedback or need assistance with the MCP directory API, please join our Discord server