LEIO Code 2.6.2 · Local stdio MCP

Repository context that remembers where your agent is.

The local-first LEIO Code gives Codex and other local agents 18 MCP tools, bounded task context, and stateful graph, FCA, and heading navigation. Start with a task and an absolute repository root; continue through exact evidence with a session-pinned cursor.

18 local tools Persistent session cursor Inspectable evidence

SYNTHETIC EXAMPLE / LOCAL STDIO SESSION PINNED

leio_code_context
task: “Change token validation safely”
repo_root: /workspace/example-service

leio_code_graph(repo_root="/workspace/example-service", kind="symbols-in", needle="src/auth.rs")
Copy a returned stable symbol URN; the synthetic file may contain several definitions.

18local MCP tools

1named session

6walk candidates

0selected result

3limitations

GO TO SYMBOL

leio_code_nav(repo_root="/workspace/example-service", session="token-change", kind="goto", needle="<paste returned stable symbol URN>")

use the value returned by symbols-in · no URN is fabricated

LIST CALLEESleio_code_nav(repo_root="/workspace/example-service", session="token-change", kind="callees")returns choices · cursor does not move

SELECT RESULTleio_code_nav(repo_root="/workspace/example-service", session="token-change", kind="select", index=0)only when a result exists · cursor moves

ORIENT

leio_code_nav(repo_root="/workspace/example-service", session="token-change", kind="here")
leio_code_nav(repo_root="/workspace/example-service", session="token-change", kind="back")
leio_code_nav(repo_root="/workspace/example-service", session="token-change", kind="forward")

same session · inspect and restore cursor history

NAVIGATION RULE

Listing callees or neighbors never moves the cursor. If a result exists, select its zero-based index before walking again; use here, back, and forward to inspect session state.

Local product surface

Eighteen tools around one persistent investigation.

Local stdio capabilityWhat it gives the agent

Bounded contextTask-specific files, symbols, checks, identity, provenance, and limitations

Stateful navigationA session-pinned cursor across graph, FCA, and heading walks

Candidate selectionList without moving; select a zero-based result before continuing

Cursor historyInspect here and move back or forward within the same session

Exact evidenceSource locations, stable symbol identities, observed calls, and imports

Focused checksSupported repository checks chosen for the current task

Local LEIO is the primary product for Codex and local agents. The hosted HTTP Apps SDK integration is optional and separate.

Primary local workflow

Context first. Then a stateful evidence walk.

01 / PROVIDE

State the task and absolute repository root.

Call leio_code_context(task, repo_root). The absolute root makes repository scope explicit and returns a bounded context bundle.

02 / INSPECT

Review identity, evidence, and limits.

Check provider and CLI identity, index repository and age, observed indexed languages, ranked candidates, local JSON-LD provenance, and explicit limitations.

03 / NAVIGATE

Pin graph, FCA, or heading navigation to a session.

Every leio_code_nav call includes the absolute repo_root and an explicit session. A neighbors call lists results without moving the cursor.

04 / SELECT + CHECK

If a result exists, select its zero-based index.

Then continue walking or use here, back, and forward within the same session. The host agent inspects source, makes authorized edits, and runs focused verification.

18-tool local MCP

Context, stateful navigation, evidence, and checks.

The tools form a local repository-intelligence surface. Availability for a given repository is reported by capabilities; status is reserved for health diagnostics.

Context

Prepare a bounded task bundle.

Provide a task and absolute repository root. LEIO returns ranked files, symbols, checks, repository identity, provenance, and explicit limitations for inspection.

SYNTHETIC EXAMPLEInspect the returned evidence before relying on it.

leio_code_context

Context identity

Know which index answered—and what it cannot prove.

LEIO reports provider and CLI identity, index repository and age, observed indexed languages, and explicit limitations so the agent can interpret a result before relying on it.

Index age describes the index. It does not prove that the working tree or remote source is fresh.

SYNTHETIC EXAMPLE

PROVIDER / CLIlocal / leio-code

INDEX

/workspace/example-service
age: 14 minutes
observed: TypeScript, SQL

LIMITATIONS

Excluded-file count: unknown
Source freshness: not established
Candidate coverage: not guaranteed

Illustrative metadata only. Values are not production measurements.

Stateful navigation

Keep one cursor across graph, FCA, and headings.

A named session preserves navigation history. Candidate lists are previews; selecting a result is the explicit move.

SYNTHETIC EXAMPLE / EVERY CALL USES THE SAME ROOT + SESSIONrepo_root="/workspace/example-service" · session="token-change"

1 · FIND SYMBOLS IN SYNTHETIC FILEleio_code_graph(repo_root="/workspace/example-service", kind="symbols-in", needle="src/auth.rs")

Inspect the exact synthetic file. Several definitions may be returned.

2 · GO TO A RETURNED SYMBOL

leio_code_nav(repo_root="/workspace/example-service", session="token-change", kind="goto", needle="<paste returned stable symbol URN>")

Copy the stable URN from the response; do not invent one.

3 · LIST CALLEESleio_code_nav(repo_root="/workspace/example-service", session="token-change", kind="callees")

Inspect returned results. Cursor stays put.

4 · SELECT IF PRESENTleio_code_nav(repo_root="/workspace/example-service", session="token-change", kind="select", index=0)

Call only if result 0 exists. Cursor moves.

5 · ORIENT

leio_code_nav(repo_root="/workspace/example-service", session="token-change", kind="here")
leio_code_nav(repo_root="/workspace/example-service", session="token-change", kind="back")
leio_code_nav(repo_root="/workspace/example-service", session="token-change", kind="forward")

Call and import evidence remains distinct from FCA shared-attribute similarity. FCA does not establish runtime coupling.

Evidence semantics

Observed relationships and similarity answer different questions.

Exact-file graph navigation follows supported calls, callers, callees, imports, importers, and membership evidence without inventing symbol identifiers.

FCA groups entities by shared attributes. It can suggest useful neighbors, but cannot by itself prove a call path, import edge, dependency, complete runtime trace, working application, or deployment.

SYNTHETIC EXAMPLE / INTERPRETATIONINSPECT

GRAPH

Observed call or import evidence from an exact file or selected candidate.

FCA

Shared attributes that may guide discovery; runtime coupling is not established.

NEXT ACTION

Open the cited source, verify the relationship, then run focused checks.

Official source installation

Install with one prompt.

Paste this into a local coding agent with terminal access, such as Codex or Claude Code. It asks the agent to inspect the official installer, preserve your other MCP entries, build locked source, and verify the real local stdio connection.

A browser-only chat cannot install software on your machine. Source installation requires Git, C/C++ build tools, stable Rust, and Node.js 22+ with npm, and can take several minutes. This is a source download and build—not a prebuilt binary or npm-published package.

Official source ↗Installation guide ↗Download source ZIP ↓

Licensed MIT OR Apache-2.0.

SOURCE INSTALL PROMPT

Install the official LEIO Code local stdio MCP from https://github.com/josaum/leio-code by following docs/install-stdio.md. Inspect the installation script, check prerequisites, build the locked source, and verify the actual MCP handshake, 18 tools, context and session navigation. Register only the leio-code stdio server in this host, preserving other MCP entries. Use absolute paths and the installer output. Do not enable the HTTP integration. Tell me whether a host reconnect is required and report the installed revision and verification results.

Copies the exact prompt above.

Developer material

Local stdio first. Hosted HTTP when ChatGPT needs it.

The two integrations are alternatives for different hosts. Local agents do not need both, and the hosted surface does not inherit the local tool count or its stateful cursor model.

PRIMARY · 18 LOCAL MCP TOOLS

Local leio-code stdio

Recommended for Codex and local agents. Prepare context once, then keep navigation pinned to an explicit session.

SYNTHETIC EXAMPLE / CONTEXT

leio_code_context(
  task="Change token validation safely",
  repo_root="/workspace/example-service"
)

SYNTHETIC EXAMPLE / STATEFUL NAVIGATION

leio_code_graph(
  repo_root="/workspace/example-service",
  kind="symbols-in",
  needle="src/auth.rs"
)

leio_code_nav(
  repo_root="/workspace/example-service",
  session="token-change",
  kind="goto",
  needle="<paste returned stable symbol URN>"
)

leio_code_nav(
  repo_root="/workspace/example-service",
  session="token-change",
  kind="callees"
)

leio_code_nav(
  repo_root="/workspace/example-service",
  session="token-change",
  kind="select",
  index=0
)

A file may return several definitions. Copy a returned stable symbol URN, list candidates without moving, and select index 0 only if that result exists.

Use status for health diagnostics and capabilities to choose supported operations. Neither is a mandatory startup call before every edit.

SECONDARY · BROWSER + HOSTED SURFACES

Native WebMCP and optional HTTP

When document.modelContext is available and browser policy permits, this page registers the read-only tool leio.describe_semantics. It returns the site graph and referenced TBox as JSON-LD. The separate HTTP Apps SDK surface remains optional for ChatGPT and uses stateless graph queries.

MACHINE-READABLE DISCOVERY

RDF 1.2 site graph ↗
LEIO TBox ↗

View developer reference ↗

01ProvideTask + absolute repository root

02InspectIdentity, ranked evidence, provenance, and limitations

03NavigateExplicit session on every leio_code_nav call

04SelectZero-based candidate before the next walk

05Orienthere, back, and forward within the session

06VerifyAuthorized edits and focused checks remain with the host agent

EXECUTION BOUNDARY

Repository evidence is context, not authority.

LEIO does not grant permission to execute, edit, or deploy. The host agent remains responsible for authorization and verification.

Trust and context

Useful evidence, with concise limits attached.

Bounded retrieval

Ranked candidates require inspection. They are not calibrated confidence or a guarantee that every relevant file was found.

Local provenance

Paths, locations, observed relationships, and local JSON-LD provenance support review.

Freshness stated carefully

Index repository and age are reported. Index age alone does not establish source freshness.

Unknown stays unknown

If excluded-file counts are unavailable, they remain unknown rather than estimated.

Graph and FCA stay distinct

Observed calls and imports are not conflated with FCA shared-attribute similarity.

Authority stays with the host

The host agent performs approved edits and checks. A graph or passing build alone is not proof of runtime behavior or deployment.

Use cases

Built for the moments when guessing is expensive.

Before an edit

Bound the task, inspect likely owners, and identify tests and constraints.

During code review

Follow exact file, symbol, call, and import evidence beyond the visible diff.

During navigation

Keep a session-pinned cursor and return with here, back, or forward.

During incidents

Use health, index, language, and limitation metadata to interpret evidence.

During onboarding

Ask evidence-backed questions without pretending the index replaces source inspection.

Across agent hosts

Use local stdio for stateful navigation; use hosted HTTP only when ChatGPT needs it.

LEIO Code 2.6.2 · Local stdio

Eighteen tools. One persistent line of investigation.

Start with a bounded context bundle, keep navigation pinned to a session, and finish with inspected evidence and focused checks.

Read the developer reference ↗