MCP Interface¶
Each agent adapter exposes a provider-local MCP server over the host client's configured MCP transport. The server gives the agent direct access to Lint-AI search, inspection, memory controls, and session controls.
Where each mode applies¶
MCP and server mode are general Lint-AI interfaces; they are not restricted to agent clients:
| Mode | Available to | What it provides |
|---|---|---|
| Core/file-based CLI | Any workflow | Build and query an IndexStore directly from local files. |
| HTTP server | Any application or client | /add, /search, /delete, /supersede, and /expire over HTTP. |
| MCP server | Any MCP-capable client | Search, memory inspection, and integration controls through JSON-RPC tools. |
| Lifecycle hooks | Supported agents | Automatic retrieval, context injection, and turn/session capture. |
Only the last row is agent-specific. An application does not need Claude Code, Codex, Gemini CLI, or AGY to use the core index, HTTP API, or MCP interface.
Tools¶
| Tool | Purpose |
|---|---|
search | Search the indexed workspace and return ranked results. Requires query; accepts top_k (1–20). |
info | Return basic information about the indexed workspace. |
list_memories | List bounded previews of indexed agent memories. Accepts limit (1–100, default 20). |
record_session | Start, stop, or inspect capture-only session recording. Use action: start, stop, or status. |
enable_lint_ai | Enable memory retrieval and capture for future hook events; recording is enabled by default. |
disable_lint_ai | Disable Lint-AI retrieval/injection and automatic capture; recording state is unchanged. |
lint_ai_status | Report independent memory and recording state. |
The same tool names are available to Claude Code, Codex, Gemini CLI, and Antigravity CLI through their configured Lint-AI MCP integration.
Search versus hooks¶
MCP calls are explicit agent actions. Lifecycle hooks are automatic client callbacks. A hook can retrieve memory and inject it into the host agent without the model calling search; the model can also call search directly when it needs workspace evidence.
memory_add/memory_search are the direct HTTP memory API equivalents used by the standalone server contract. A successful add refreshes the index before it returns, so a subsequent search can see the new memory.
State and safety¶
Memory and recording state are project- and provider-scoped. Recording is capture-only: it writes session events but does not inject them as memory. Recorded content is bounded and redacted according to the session-recording policy. Tool and hook failures are fail-open so the host agent can continue.
For HTTP deployment and authentication, see Server and MCP.