AGENTS.md

Guidance for coding agents working on LMSSEP Analysis MCP Server. This server provides code analysis and feature-flow analysis tools for understanding complex codebases.

Project overview

The Analysis server has two tool families. Code analysis tools initialize a session, accept step-by-step analysis, finalize documentation, expose current status, and list sessions. Feature-flow tools analyze behavior across files and generate ASCII flow diagrams.

Setup commands

bashcd <project-root>/genesis/LMSSEP/analysis
pip install -r requirements.txt
python3 main.py

Edit configs/analysis.py to enable or disable tools, tune analysis parameters, and set output directories.

Code and output map

• main.py starts the MCP server.
• configs/analysis.py controls tool availability and behavior.
• docs/analysis-tools.md is the detailed tool reference.
• output/analysis/ receives code analysis Markdown files.
• output/analysis/flows/ receives generated feature-flow diagrams.

Tool usage rules

Initialize a code analysis session only after selecting a concrete source file. Submit analysis in ordered steps, then finalize once the evidence is complete. For feature flows, describe the entry point, participating files, and expected output before calling the tool.

Testing and verification

Use a small synthetic source file to verify session initialize, step submission, status, finalize, and list behavior. Then run a feature-flow analysis against a narrow fixture and confirm the output diagram lands in the expected output directory.

Security and data handling

Source files under analysis may contain secrets or proprietary logic. Do not publish generated analysis without redaction. Keep generated files in output/analysis/ and output/analysis/flows/ out of commits unless intentionally curated as fixtures.

Commit and PR rules

For tool changes, include the session lifecycle tested and any output format differences. Avoid broad rewrites of generated analysis text unless the schema or contract changed.