tiny-context — efficient file tools by AVRG3 MCP Server
tiny-context — efficient file tools by AVRG3 runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 7 Nov 2026.
Local document queries, saved extraction profiles, spreadsheet SQL, logs and keyed JSON changes.
What the code does
We read the source, 5 h ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const candidates = rel.startsWith("/") ? [path.join(dir, rel), rel] : [path.resolve(dir, rel)];
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to tiny-context — efficient file tools by AVRG3
same job, measured the same wayEvery spreadsheet is a table: Excel, CSV, Parquet and JSON as SQL tables for AI agents.
Local MCP proxy for tool restrictions, response redaction, audit logs, and database schema context.
Local data runtime for AI agents: query CSV, Excel, Parquet and JSON files with DuckDB SQL.
Comprehensive PostgreSQL documentation and best practices, including ecosystem tools
AI access to Quadratic spreadsheets: open files, run Python/SQL, query connected databases.
Read and filter Excel, ODS, CSV, SQLite, Parquet and MTSV files — or a directory — as plain text
Read-only health checks and data questions for SQL Server and PostgreSQL, with your saved profiles.
Read-only SQL database and plain-text SQL dump schema extraction to compact TOON for MCP clients.
tiny-context — efficient file tools by AVRG3 — questions
Answers built from our own checks of this server.