Skip to main content
Glama
Sign In
artifact-gauge-mcp

artifact-gauge-mcp

by mrfentmen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

artifact-gauge-mcp

Artifact Gauge is a local MCP tool for answering a simple release question: what is taking up space? It reports artifact totals, extension histograms, largest files, and dependency manifest metadata without returning file contents.

Tools

  • inspect_artifacts: scan a bounded local project and summarize file sizes and types.

  • inspect_manifest: report metadata for one recognized dependency manifest without exposing its contents or dependency versions.

Related MCP server: Code Graph MCP

Safety

  • Local paths only, with ARTIFACT_GAUGE_ROOT boundary support and symlink checks.

  • Skips Git data, dependencies, coverage, framework caches, and other common generated caches while intentionally including dist and build artifacts.

  • Caps recursion, file count, file size, and output.

  • Never returns file contents, package versions, secrets, or source text.

  • This is a size heuristic, not a complete bundler or dependency vulnerability analyzer.

Run

npm install
npm run build
node dist/index.js

Available Tools

2 tools
inspect_artifactsA

Inspect local artifact sizes, extension totals, largest files, and dependency manifest names without returning file contents.

Inputs: project (required).

inspect_manifestA

Inspect bounded metadata for one recognized local dependency manifest without returning its contents or versions.

Inputs: file (required), project (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A3.7/5.0

    Scored across 2 tools

    Disambiguation4/5

    Both tools involve inspection, but inspect_artifacts provides a broad overview of artifact sizes and extensions, while inspect_manifest targets a single dependency manifest. The scope difference is clear, though the shared 'inspect' prefix could cause minor confusion.

    Naming Consistency5/5

    Both tools use a consistent verb_noun pattern (inspect_artifacts, inspect_manifest), making their purposes predictable and the naming style uniform.

    Tool Count3/5

    With only two tools, the server feels minimal and borderline for a meaningful tool set. However, the two tools cover different granularities, making the count somewhat reasonable for a focused inspection-only purpose.

    Completeness4/5

    The tools cover the main inspection needs: a high-level artifact overview and detailed single-manifest metadata. There may be gaps like per-file detail inspection, but within the stated non-invasive inspection scope, the surface is fairly complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers