Frequently Asked
Questions
Answers to common questions about Devscriptor
What is Devscriptor?
Devscriptor is a high-performance code analysis engine built in Rust that builds a knowledge graph of your codebase in a single SQLite file. It extracts entities (functions, classes, etc.), relationships (calls, inheritance), enables semantic search, and provides LSP code intelligence—making your codebase queryable by AI agents through the Model Context Protocol (MCP).
Is Devscriptor free?
Yes — Devscriptor is currently free to download and use. It is distributed as pre-built installers for Linux (x86_64 and aarch64), macOS (Apple Silicon), and Windows (x86_64) from downloads.devscriptor.com. Just download, extract, and run.
How does MCP integration work?
Devscriptor includes a native, unified MCP (Model Context Protocol) server that exposes 74 tools over stdio to AI agents like Claude Desktop, Cursor, and Cline. This includes 31 core tools for scanning, search, analysis, the Context Graph, and the real-time watcher; 38 LSP tools for live code intelligence (go-to-definition, hover, completions, diagnostics); and 5 architecture tools for LSP detection and setup. Point your client at the devscriptor-mcp entry point.
Does it work with local LLMs?
Yes. Devscriptor is an MCP server, not an LLM — it works with any MCP-compatible client, including agents backed by locally hosted models. Because all of Devscriptor’s own analysis runs on your machine, nothing about your code depends on a cloud provider. Your AI client (Claude Desktop, Cursor, Cline, etc.) connects to Devscriptor over stdio and can route to whatever model you choose.
Is my code sent to any external service?
No. Devscriptor is 100% local. All analysis happens on your machine, all data is stored in a local SQLite file, and nothing is ever sent to external servers. There is no telemetry, no analytics, and no tracking of any kind. This makes it well suited for proprietary codebases, sensitive projects, and environments with strict data-security requirements.
What languages are supported?
Devscriptor parses 26 languages and frameworks with tree-sitter 0.25: Python, Rust, TypeScript/TSX, JavaScript, Go, Java, C, C++, C#, Ruby, PHP, Swift, Kotlin, Scala, Dart, Bash, SQL, Solidity, F#, GraphQL, HTML, Objective-C, CUDA, and VB.NET — plus the Vue and Svelte frameworks. It extracts functions, classes, structs, enums, interfaces, components, and their relationships (calls, inherits, implements, uses).
What is LSP Code Intelligence?
LSP (Language Server Protocol) integration provides real-time IDE features: go-to-definition, hover information, completions, diagnostics, call hierarchy, and type hierarchy. Devscriptor includes 38 LSP tools and 5 architecture tools, and ships 21 pre-configured language servers resolved via a 4-tier detection system (user config → Devscriptor-managed → system PATH/SDKs → VS Code extensions), then installed on demand. Servers include rust-analyzer, pyright, typescript-language-server, gopls, clangd, and more.
What is the Context Graph?
Context Graph is an AI memory system that persists across sessions in the same local SQLite database as the code graph. It stores notes using 9 structured types: adr (architecture decisions), standard (coding standards), optimization, failure, practice, reflection, general, file_description, and modification. Notes can be linked to concrete code entities and abstract concepts, and retrieved by keyword, semantic, or hybrid search. When you return to a project weeks later, your AI recalls the context.
How does semantic search work?
Devscriptor generates 768-dimensional vector embeddings for your code using the local jina-embeddings-v2-base-code model (INT8-quantized, ~150 MB). No API keys are required — the model downloads once, then runs offline. These embeddings capture the semantic meaning of code, so you can search by concept (e.g., "functions that handle authentication") rather than keywords. Vector search uses cosine similarity via sqlite-vec, and can be fused with FTS5 keyword results using Reciprocal Rank Fusion.
Is it suitable for large codebases?
Yes. Devscriptor is built in Rust and uses parallel, gitignore-aware file discovery, memory-mapped parsing, and a streamed cross-file analysis pass with bounded memory. Incremental scanning (mtime+size+XXH3) and a content-hash embedding cache make re-analysis fast. The streaming cross-file pipeline has been validated on large repositories such as Kubernetes (~11.5k Go files) without a memory cliff.
How do I get started?
Download the installer for your platform from downloads.devscriptor.com, extract it, and add the devscriptor binary to your PATH. Then run "devscriptor scan ./your-project" to build the knowledge graph, and optionally "devscriptor embed" for semantic search. For AI integration, point your MCP client at the devscriptor-mcp entry point. See the Download page for full setup instructions.
Why Rust?
Rust provides memory safety without garbage collection, zero-cost abstractions, and predictable performance. Devscriptor leans on that with multi-threaded parsing (scaling to num_cpus), memory-mapped file reading, a multi-session ONNX embedding pool, batched WAL-mode SQLite transactions, and content-hash caches that skip redundant work. The result is a fast, low-overhead engine that stays responsive on large codebases while keeping strong safety guarantees.
Quick Reference
All questions at a glance
What is Devscriptor?
Devscriptor is a high-performance code analysis engine built in Rust that builds a knowledge graph of your codebase in a single SQLite file. It extracts entities (functions, classes, etc.), relationships (calls, inheritance), enables semantic search, and provides LSP code intelligence—making your codebase queryable by AI agents through the Model Context Protocol (MCP).
How does MCP integration work?
Devscriptor includes a native, unified MCP (Model Context Protocol) server that exposes 74 tools over stdio to AI agents like Claude Desktop, Cursor, and Cline. This includes 31 core tools for scanning, search, analysis, the Context Graph, and the real-time watcher; 38 LSP tools for live code intelligence (go-to-definition, hover, completions, diagnostics); and 5 architecture tools for LSP detection and setup. Point your client at the devscriptor-mcp entry point.
Is my code sent to any external service?
No. Devscriptor is 100% local. All analysis happens on your machine, all data is stored in a local SQLite file, and nothing is ever sent to external servers. There is no telemetry, no analytics, and no tracking of any kind. This makes it well suited for proprietary codebases, sensitive projects, and environments with strict data-security requirements.
Does it work with local LLMs?
Yes. Devscriptor is an MCP server, not an LLM — it works with any MCP-compatible client, including agents backed by locally hosted models. Because all of Devscriptor’s own analysis runs on your machine, nothing about your code depends on a cloud provider. Your AI client (Claude Desktop, Cursor, Cline, etc.) connects to Devscriptor over stdio and can route to whatever model you choose.
What languages are supported?
Devscriptor parses 26 languages and frameworks with tree-sitter 0.25: Python, Rust, TypeScript/TSX, JavaScript, Go, Java, C, C++, C#, Ruby, PHP, Swift, Kotlin, Scala, Dart, Bash, SQL, Solidity, F#, GraphQL, HTML, Objective-C, CUDA, and VB.NET — plus the Vue and Svelte frameworks. It extracts functions, classes, structs, enums, interfaces, components, and their relationships (calls, inherits, implements, uses).
What is LSP Code Intelligence?
LSP (Language Server Protocol) integration provides real-time IDE features: go-to-definition, hover information, completions, diagnostics, call hierarchy, and type hierarchy. Devscriptor includes 38 LSP tools and 5 architecture tools, and ships 21 pre-configured language servers resolved via a 4-tier detection system (user config → Devscriptor-managed → system PATH/SDKs → VS Code extensions), then installed on demand. Servers include rust-analyzer, pyright, typescript-language-server, gopls, clangd, and more.
What is the Context Graph?
Context Graph is an AI memory system that persists across sessions in the same local SQLite database as the code graph. It stores notes using 9 structured types: adr (architecture decisions), standard (coding standards), optimization, failure, practice, reflection, general, file_description, and modification. Notes can be linked to concrete code entities and abstract concepts, and retrieved by keyword, semantic, or hybrid search. When you return to a project weeks later, your AI recalls the context.
How does semantic search work?
Devscriptor generates 768-dimensional vector embeddings for your code using the local jina-embeddings-v2-base-code model (INT8-quantized, ~150 MB). No API keys are required — the model downloads once, then runs offline. These embeddings capture the semantic meaning of code, so you can search by concept (e.g., "functions that handle authentication") rather than keywords. Vector search uses cosine similarity via sqlite-vec, and can be fused with FTS5 keyword results using Reciprocal Rank Fusion.
Is it suitable for large codebases?
Yes. Devscriptor is built in Rust and uses parallel, gitignore-aware file discovery, memory-mapped parsing, and a streamed cross-file analysis pass with bounded memory. Incremental scanning (mtime+size+XXH3) and a content-hash embedding cache make re-analysis fast. The streaming cross-file pipeline has been validated on large repositories such as Kubernetes (~11.5k Go files) without a memory cliff.
How do I get started?
Download the installer for your platform from downloads.devscriptor.com, extract it, and add the devscriptor binary to your PATH. Then run "devscriptor scan ./your-project" to build the knowledge graph, and optionally "devscriptor embed" for semantic search. For AI integration, point your MCP client at the devscriptor-mcp entry point. See the Download page for full setup instructions.
Why Rust?
Rust provides memory safety without garbage collection, zero-cost abstractions, and predictable performance. Devscriptor leans on that with multi-threaded parsing (scaling to num_cpus), memory-mapped file reading, a multi-session ONNX embedding pool, batched WAL-mode SQLite transactions, and content-hash caches that skip redundant work. The result is a fast, low-overhead engine that stays responsive on large codebases while keeping strong safety guarantees.
Is Devscriptor free?
Yes — Devscriptor is currently free to download and use. It is distributed as pre-built installers for Linux (x86_64 and aarch64), macOS (Apple Silicon), and Windows (x86_64) from downloads.devscriptor.com. Just download, extract, and run.
Still have questions?
We're here to help. Reach out and we'll get back to you as soon as possible.
contact@devscriptor.com