LLMScribe
Turn any local project into clean, structured context for AI agents.
For AI Agents (primary)
LLMScribe provides a deterministic code-context infrastructure layer for AI agents. It is NOT an AI-powered coding/search agent.
Installation
pip install llmscribe
Running the MCP Server
llmscribe-mcp
MCP Client Configurations
Cursor / Claude Desktop / Standard MCP Clients:
{
"mcpServers": {
"llmscribe": {
"command": "llmscribe-mcp"
}
}
}
Alternative Module Invocation:
{
"mcpServers": {
"llmscribe": {
"command": "python",
"args": ["-m", "llmscribe.mcp"]
}
}
}
Tools Reference
LLMScribe MCP provides exactly 7 tools:
1. project_map
- Purpose: Generates directory tree structure without file contents.
- Parameters:
path(Optional[str]),format(str ="markdown") - When to use: Exploring repository structure before selecting specific files.
2. project_overview
- Purpose: Generates full directory structure and full contents of all supported text files.
- Parameters:
path(Optional[str]),format(str ="markdown") - When to use: Getting a complete overview of small-to-medium codebases in one call.
3. search
- Purpose: Keyword search across file paths and line-by-line file contents. Main discovery primitive for AI agents.
- Parameters:
query(str),path(Optional[str]),format(str ="markdown") - When to use: Locating specific symbols, function definitions, or import statements.
4. read
- Purpose: Retrieves full content of a single specific relative file path, with strict path traversal security checks.
- Parameters:
file_path(str),path(Optional[str]),format(str ="markdown") - When to use: Reading a specific file into context safely.
5. read_many
- Purpose: Retrieves full contents of multiple relative file paths in a single call, handling partial success if some paths fail.
- Parameters:
file_paths(list[str]),path(Optional[str]),format(str ="markdown") - When to use: Batch fetching multiple source files efficiently.
6. project_dependencies
- Purpose: Analyze file dependencies - what files this file depends on, what files depend on this file, local vs external vs unresolved.
- Parameters:
file_path(str),path(Optional[str]),format(str ="markdown") - When to use: Understanding dependency relationships and import graphs.
7. project_diff
- Purpose: Inspects Git status and unified diffs for staged, unstaged, or specific commits.
- Parameters:
path(Optional[str]),staged(bool),commit(Optional[str]),format(str ="markdown") - When to use: Reviewing uncommitted edits or verifying changes.
Agent Workflow
Recommended workflow sequence for AI agents:
project_map → search → read/read_many
Example: Understand a New Repository
project_map(): Get the overall directory tree to understand repository architecture.search("main"): Search for key entrypoints or symbol definitions.read("src/main.py")orread_many(["src/main.py", "src/utils.py"]): Read the relevant source files.
Example: Analyze Dependencies
search("FastAPI"): Find files using FastAPI.project_dependencies("src/api/main.py"): Analyze dependencies for key files.read_many(): Read all dependency files together.
CLI Usage
The CLI provides the same core capabilities as MCP:
# Show project structure
llmscribe map
# Generate full project overview
llmscribe overview
# Search project code
llmscribe search "authentication"
# Read specific files
llmscribe read src/auth/service.py
llmscribe read-many src/auth/service.py src/api/login.py
# Analyze dependencies
llmscribe dependencies src/auth/service.py
# Show git changes
llmscribe diff
# JSON output for scripts/AI agents
llmscribe search "auth" --json
llmscribe map --json
JSON Mode
All tools support format="json" for structured, machine-readable output:
Example JSON Response (search):
{
"ok": true,
"tool": "search",
"path": "/path/to/project",
"data": {
"query": "authentication",
"root_path": "/path/to/project",
"matches": [
{
"file_path": "src/auth/service.py",
"line_number": 10,
"line_content": "from fastapi.security import OAuth2PasswordBearer",
"match_type": "content",
"matched_text": "auth"
}
],
"file_count": 5,
"match_count": 12,
"truncated": false,
"truncation_limit": 1000
},
"metadata": {
"query": "authentication",
"file_count": 5,
"match_count": 12,
"truncated": false
}
}
Project Positioning
LLMScribe provides clean, deterministic, structured code context. The AI agent provides the intelligence.
- ✅ Deterministic: No LLM, embeddings, or AI ranking
- ✅ Structured: Consistent JSON output schemas
- ✅ Agent-friendly: Designed specifically for AI agent workflows
- ❌ NOT an AI coding agent
- ❌ NOT a semantic search engine
- ❌ NOT a generic Git client
GitHub Repository Support
All tools can inspect remote GitHub repositories directly. Use repo parameter instead of path.
Example:
# Map a remote repo
project_map(repo="owner/repo")
# Search code in a remote repo
search(query="FastAPI", repo="owner/repo")
Note:
pathandrepoare mutually exclusive.
Install
pip install llmscribe
Version
Current version: 1.2.0
License
Apache License 2.0
Repository
Issues & Support
Metadata
Release files for llmscribe 1.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| llmscribe-1.2.0.tar.gz | 49.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| llmscribe-1.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 98.2 kB
Release files / llmscribe-1.2.0.tar.gz
| Download URL | llmscribe-1.2.0.tar.gz |
|---|---|
| Size | 49.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
def8563172a9a960c86e1e1528b3e2e84acc5b91f3a59943e2b8581bab31f792
|
|
BLAKE2b-256 checksum How to use checksums |
988db3d2cd40075eb0e94e3030d8480a8c83a006f823712621ad11e9f7bd706d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 2, 2026.
Transparency logRelease files / llmscribe-1.2.0-py3-none-any.whl
| Download URL | llmscribe-1.2.0-py3-none-any.whl |
|---|---|
| Size | 48.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
40da8359a3424ef5498c52c65757bb4ea0d2c43155b397b51cbd77cd26ffad8b
|
|
BLAKE2b-256 checksum How to use checksums |
f42c319891e0ee99b0bd4b67f646d856ff1ec8502df49b955af089b13df8c150
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 2, 2026.
Transparency log