atx-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ATX_WORKSPACE | Yes | The directory used as the asset store. Configured via the --workspace command-line flag or the ATX_WORKSPACE environment variable. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| apply_transformA | Apply a transform recipe at full resolution and issue a new revision.
Pass either |
| compare_revisionsA | Scale two revisions to a long edge of 640px each and compose them on one canvas (side by side, or stacked) with an 8px gap, returned inline as a JPEG. A is placed left/top, B is placed right/bottom. Useful for before/after or A/B visual checks. layout="diff" instead requires A and B to share the exact same dimensions and returns a single pixel-difference heatmap plus mean_abs_diff/max_abs_diff/changed_pixel_ratio. |
| detect_documentA | Detect the dominant quadrilateral (a sheet of paper, a screen, a whiteboard, a sign)
in a revision with a contour-based search, and return it as a ready-to-paste
perspective operation. This is to |
| detect_tiltA | Detect the tilt (roll) of a revision: Canny + Hough dominant lines for coarse candidates, refined below 0.1 degree with an edge projection-profile search. Horizontal-only and vertical-only estimates are reported separately so a disagreement can be read as perspective/camera position rather than roll, Set include_score_curve=true to also get the whole search range as a score curve (omitted by default to keep the answer small). Read-only: it never modifies the image. A null recommended angle means "do not correct". |
| explain_operationA | Full reference for one recipe operation: every parameter with its type, range, required/default status and semantics, one or two ready-to-paste JSON examples, and the gotchas worth knowing before using it. A built-in preset name works too and returns its full operation list, so a preset can be read and copied as a raw recipe. An unknown name returns a structured error listing every valid operation and preset. Read-only. |
| export_assetA | Copy a revision's bytes out of the workspace to a destination path. Refuses to overwrite an existing file unless overwrite=true (ask the user first). |
| generate_maskA | Generate a deterministic grayscale mask as a new PNG revision, with exactly the
dimensions of |
| import_assetA | Import a local image file into the workspace and issue an immutable revision.
Pass either |
| inspect_imageA | Inspect a revision: dimensions, MIME type, byte size, alpha/ICC presence, EXIF orientation and summary, and whether GPS (PII) metadata is present. |
| list_assetsB | List revisions in the workspace ledger (lineage, recipe hash, dimensions, sizes). |
| list_operationsA | Compact catalog of the recipe vocabulary: every operation with a one-line
description and its parameter names with terse type/range hints, plus the
built-in preset names. Optional |
| render_previewA | Render a recipe as a small JPEG preview (long edge <= 768 by default) and return it
inline plus a file path, so the composition can be checked before committing to
apply_transform. Takes either |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Each tool has a clearly distinct purpose: apply_transform and render_preview are differentiated by output resolution and intent, detect_document and detect_tilt are both read-only but target different geometric features, and the asset management tools (import/export/list/inspect) have no overlap. No two tools could be confused.
All 12 tools follow a consistent verb_noun pattern in snake_case (e.g., apply_transform, compare_revisions, list_assets). No deviations or mixed conventions.
12 tools is well-scoped for an image processing and asset management server. Each tool earns its place covering the core workflow: import, inspect, transform, preview, apply, export, plus detection, mask generation, comparison, and reference operations.
The tool surface is complete for its domain: import (import_asset), list (list_assets), inspect (inspect_image), transform (apply_transform), preview (render_preview), export (export_asset), and supporting operations like detect_document, detect_tilt, generate_mask, compare_revisions, explain_operation, and list_operations. No obvious dead ends; even idempotency is handled. The only potential gap is lack of delete/update, but revisions are immutable by design, so that's intentional.