Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
JAMBAVAN_ROOTNoProject root to index and serveauto-detect
JAMBAVAN_DEV_MODENoDefault Vibhishana Niti level (lite / full / ultra)full
JAMBAVAN_ALLOW_BASHNo1 registers bashoff
JAMBAVAN_ALLOW_WRITENo1 registers write_file + patch_fileoff
JAMBAVAN_TOKEN_BUDGETNoMax tokens in jambavan_context output8000
JAMBAVAN_ALLOW_SECRETSNo1 lets file tools touch secret-looking filesoff
JAMBAVAN_MAX_READ_BYTESNoMax file size read_file will load5242880
JAMBAVAN_BASH_INHERIT_ENVNo1 passes the full host env to bash (default: minimal env)off
JAMBAVAN_MAX_OUTPUT_CHARSNoGlobal cap on any tool's returned output100000
JAMBAVAN_ALLOW_OUTSIDE_ROOTNo1 lets tools escape the project root (trusted local use only)off

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
{}
prompts
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
jambavan_awakenA

Return the Jambavan operating protocol: recall memory, index/watch code, retrieve context before edits, patch surgically, run checks, and store durable decisions. Call once at the start of every host session. Includes recent project memories by default.

jambavan_indexA

Build or refresh the Jambavan codebase index. Parses source files with a tree-sitter AST extractor and stores symbols in a local SQLite database. Run once per project, then incrementally on file changes. Returns indexing statistics (files processed, symbols extracted, duration).

jambavan_contextA

Search the Jambavan index for code symbols and snippets most relevant to a query. Returns a ranked, token-budgeted context block of matching functions, classes, and types. Inject this block into your prompt to give the model precise, token-efficient codebase knowledge. Much cheaper than reading whole files — only the relevant symbol bodies are returned. Automatically includes top project-memory matches and a bounded set of extracted callers/callees under the same token budget. Options: compress_prose shrinks comments for extra budget; include_diff adds recent git changes; include_tests shows heuristic test associations/references, not execution coverage.

jambavan_watchA

Control the live file watcher that keeps the index in sync as you edit code. Actions: "start" — begin watching (index must exist first); "stop" — stop watching; "status" — show watcher state. While running, supported non-ignored source-file changes trigger incremental re-indexing (no full rescan). Use "start" after jambavan_index, then forget about it — the index stays fresh automatically.

jambavan_debt_ledgerA

Harvest every rin marker (lines marked with a ceiling and upgrade path) from the project into a debt ledger. Groups findings by file and flags any marker with no upgrade trigger — those are the ones that silently rot. Read-only. Call before a release or refactor sprint.

jambavan_graphA

Navigate the code graph built from the current index. Call jambavan_index first. action=report lists hub nodes and edge-confidence notes; action=query finds matching nodes and their BFS neighbors; action=path finds the shortest route between two symbols. Action is inferred from the arguments when omitted. Ambiguous same-name edges are excluded unless include_inferred=true.

jambavan_doctorA

One-shot environment health check: root detection source, tree-sitter vs regex parser backends, write/bash tool gates, token budget, memory dir writability, .gitignore/CI presence, and index/watcher status. Call this first when something feels off (e.g. context results look like the wrong project) — it catches the most common cause: the MCP host resolving the wrong project root.

jambavan_memory_storeA

Persist a memory as an Open Knowledge Format (OKF) concept document. Memories are markdown files with YAML frontmatter — human-readable and portable. Each memory has a title, body (markdown), optional tags, and a scope (e.g. project name). Memories with the same title in the same scope are overwritten (idempotent). Returns the OKF concept ID (scope/slug) of the stored document.

jambavan_memory_readA

Read stored memories. Pass id to fetch one document, query to BM25-search, or neither to recall the most recent. Set provider=mempalace for explicit read-only MemPalace access, or provider=all for separate provider sections; ordinary reads never start MemPalace. Jambavan scope/collection map to MemPalace wing/room.

jambavan_memory_mine_sessionA

Mine durable facts, decisions, TODOs, and constraints from a pasted session transcript or log. Stores each extracted item as an OKF memory in the requested scope. This is deterministic text mining — no summarization or external service.

jambavan_memory_forgetA

Retire a memory. mode=invalidate (the default) marks it superseded but keeps the document for temporal history; mode=delete permanently removes it. Provide id for one memory, or scope with delete_scope: true to wipe a scope.

jambavan_memory_statusA

Show active Jambavan counts by scope and collection by default. Set provider=mempalace or provider=all to explicitly include read-only MemPalace status and taxonomy.

jambavan_failure_storeA

Store a structured failure record in the memory palace. Use after a command/approach fails to prevent repeating the same mistake in future sessions. Stores: command, symptom, attempted fix, root cause, resolution, status, and advice on what NOT to retry.

jambavan_failure_searchA

Search past failure records for a command, error, or symptom. Call BEFORE retrying a failing command to check if it was already diagnosed. Returns structured failure records with status and resolution info.

jambavan_session_handoffA

Move session context between sessions, hosts, or people as one self-contained markdown document containing recent memories, rin debt markers, and git status. Omit text to export; pass text to import it back (idempotent — re-importing creates no duplicates).

jambavan_review_packA

Assemble a review pack for the current branch vs a base branch: touched files, the symbols changed or deleted in them, their callers (via the knowledge graph), related test associations/references, past failure records mentioning the same files, and risk flags (open rin debt, no matching test association). Call before opening/updating a PR, or whenever asked "what changed" / "review this branch". Requires jambavan_index to have been run at least once for symbol/caller/test/risk analysis.

jambavan_impactA

Analyze changed symbols against inbound extracted graph edges and test associations/references. Reports bounded transitive callers, test associations/references, and explicit graph incompleteness. Use before a risky refactor or PR review; call jambavan_index first.

read_fileA

Read the contents of a project file. Paths are confined to the project root unless JAMBAVAN_ALLOW_OUTSIDE_ROOT=1.

searchA

Search project files using ripgrep, with grep fallback. Fast regex search. Paths are confined to the project root unless JAMBAVAN_ALLOW_OUTSIDE_ROOT=1.

list_filesA

List project files in a directory. Paths are confined to the project root unless JAMBAVAN_ALLOW_OUTSIDE_ROOT=1.

Prompts

Interactive templates invoked by user choice

NameDescription
root_causeRoot-cause investigation protocol. Use before fixing any bug, test failure, or unexpected behavior — it enforces observe → compare → hypothesize → fix instead of guess-and-check. Escalates at 3+ failed attempts.
verify_gateVerification gate demanding fresh evidence before claiming completion. Use before asserting tests pass, a build succeeds, a bug is fixed, or requirements are met.
strategy_planStrategic approach protocol for multi-step work, scaled to task size. Use before starting any non-trivial implementation.
decompose_taskParallel work decomposition protocol: boundaries, independence checks, contracts, and merge sequencing. Use when a task has sub-units that can proceed independently.
dev_rulesVibhishana Niti: efficient, truthful senior-dev rules — YAGNI first, stdlib before dependencies, shortest working diff, root-cause fixes.

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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/beingmartinbmc/jambavan'

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