mcp server
Aspicio
DXF and PDF/X-4 for AI agents: structured facts, PNG renders, an interactive in-chat viewer.
Description as published by the maintainer. Source
- version 0.12.0
- active
- document understanding
active — Most recent push to the repository was 2026-08-07. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
8 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
describe_doc(space, source)- Return a structured JSON summary of a drawing in any supported format (DXF or PDF), detected from its bytes rather than its name. Use this when you do not know which format you have; the reply names the format that was read. Covers the whole drawing by default, including every page of a multi-page PDF; pass `space` (a name from the reply's `spaces`) to scope it to one page or sheet. When the user wants to see or explore the drawing themselves, prefer view_dxf (interactive viewer) — if your platform gates it behind user approval, offer it and ask rather than substituting a static render. Required: source.
describe_dxf(space, source)- Return a structured JSON summary of a DXF drawing — units, bounding box, layers (with the color actually drawn), per-type entity counts, and any skipped/unsupported types. Use this to answer structural questions (what layers exist, how many parts, what size, is it to scale) without rendering an image. For a PDF use describe_pdf; if you do not know the format, use describe_doc. Covers the whole drawing by default, including every page of a multi-page PDF; pass `space` (a name from the reply's `spaces`) to scope it to one page or sheet. When the user wants to see or explore the drawing themselves, prefer view_dxf (interactive viewer) — if your platform gates it behind user approval, offer it and ask rather than substituting a static render. Required: source.
describe_pdf(space, source)- Return a structured JSON summary of a PDF drawing — units (points), bounding box, layers, per-type entity counts, the text it contains, and what was skipped (images, shadings, transparency). Use this for structural questions about a PDF without rendering it. For a DXF use describe_dxf; if you do not know the format, use describe_doc. Covers the whole drawing by default, including every page of a multi-page PDF; pass `space` (a name from the reply's `spaces`) to scope it to one page or sheet. When the user wants to see or explore the drawing themselves, prefer view_dxf (interactive viewer) — if your platform gates it behind user approval, offer it and ask rather than substituting a static render. Required: source.
load_dxf_for_viewer(length, offset, source)- Internal: returns DXF bytes (base64) for the in-chat viewer. Called by the widget, not the model. Required: source.
render_doc(space, width, source)- Render a drawing in any supported format (DXF or PDF) to a PNG you can look at, detected from its bytes rather than its name. Use this when you do not know which format you have. Renders the first page/sheet by default; pass `space` (a name from a describe reply's `spaces`) to render another one. Some chat UIs do not display the returned image to the user: for URL sources the result also includes a direct image link — show it (e.g. as a markdown image) when they need to see the render. When the user wants to see or explore the drawing themselves, prefer view_dxf (interactive viewer) — if your platform gates it behind user approval, offer it and ask rather than substituting a static render. Required: source.
render_dxf(space, width, source)- Render a DXF drawing to a PNG image you can look at. Use this to answer visual questions (what does it look like, where is a feature, does it look right) — it returns an image, not text. For structural facts, prefer describe_dxf. For a PDF use render_pdf; if you do not know the format, use render_doc. Renders the first page/sheet by default; pass `space` (a name from a describe reply's `spaces`) to render another one. Some chat UIs do not display the returned image to the user: for URL sources the result also includes a direct image link — show it (e.g. as a markdown image) when they need to see the render. When the user wants to see or explore the drawing themselves, prefer view_dxf (interactive viewer) — if your platform gates it behind user approval, offer it and ask rather than substituting a static render. Required: source.
render_pdf(space, width, source)- Render a PDF drawing's vector content to a PNG you can look at. Images, shadings, and transparency are not drawn — they are reported by describe_pdf — so this shows line work and text, not a page facsimile. For a DXF use render_dxf; if you do not know the format, use render_doc. Renders the first page/sheet by default; pass `space` (a name from a describe reply's `spaces`) to render another one. Some chat UIs do not display the returned image to the user: for URL sources the result also includes a direct image link — show it (e.g. as a markdown image) when they need to see the render. When the user wants to see or explore the drawing themselves, prefer view_dxf (interactive viewer) — if your platform gates it behind user approval, offer it and ask rather than substituting a static render. Required: source.
view_dxf(source, allow_file_open)- Open an interactive viewer the user can pan, zoom, and toggle layers in (renders in-chat on MCP Apps-capable hosts). Reads DXF and vector PDF; for a PDF it shows line work and text rather than a page facsimile, so images, shadings, and transparency are absent by design. Use this when the user wants to see or explore the drawing themselves; for your own analysis use a describe_* tool (facts) or a render_* tool (image). The viewer shows only the drawing from this call. Delivery is handled by the widget itself: small drawings are embedded in the result and larger URL-sourced drawings are fetched by the widget through its own tool call — never re-fetch or inline the file for the viewer's sake, and don't blind-retry if the user reports an empty viewer (the viewer posts its actual status back to the conversation context). Required: source.
Last successful function declaration observed on . Source: https://aspicio-api.frontsail.app/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://aspicio-api.frontsail.app/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 3 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-08-07 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 7 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 0.12.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-08-02 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| License | MIT | Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. | as of fetch | GitHub | |
| First listed in the MCP Registry | 2026-08-02 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub | |
| mcp tools declared | 8 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | aspicio-api.frontsail.app | |
| mcp endpoint status | ok | The server listed 8 functions when asked. | as of probe | aspicio-api.frontsail.app |
Where to get it
Related, by what their authors tagged them
-
io.github.bcllcc/modulor
— last commit 2026-06-12, shares cad, dxf
Agent-native CAD: draw plans, model 3D, render checks, export DXF/SVG/STL/GLB/IFC, import DXF.
-
io.github.cadlens-co/cadlens-mcp
— last commit 2026-07-17, shares cad, dxf
Model Context Protocol server that wraps the CADLens REST API.
-
io.github.ChanMeng666/archlang-mcp
— last commit 2026-08-06, shares cad, dxf
Compile, describe, lint, validate, score and repair multi-storey and curved ArchLang floor plans.
-
agiwhitelist-auteur-auteur
— last commit 2026-08-05, shares webgl
Design and build complete web experiences from scratch — award-level product and marketing pages, cinematic scroll-dire…
-
io.github.gaopengbin/cesium-mcp-dev
— last commit 2026-08-05, shares webgl
CesiumJS API docs, code generation and development tools for IDE AI assistants.
-
io.github.gaopengbin/cesium-mcp-runtime
— last commit 2026-08-05, shares webgl
AI-powered 3D globe control via MCP. Camera, layers, markers, spatial analysis with CesiumJS.
-
Wiplash
— last commit 2026-07-31, shares chatgpt, mcp-apps
Discover Wiplash and manage owned agents with human OAuth.
-
YTDL RMCP
— last commit 2026-08-06, shares mcp-apps
yt-dlp search, download, metadata, delivery, and Plex workflows over MCP and CLI.
-
YTDL RMCP
— last commit 2026-08-06, shares mcp-apps
Rust MCP server and CLI for yt-dlp search, downloads, metadata, transfers, and Plex playlists.
-
ai.tuteliq/mcp
— last commit 2026-08-06, shares mcp-apps
Detect grooming, bullying, fraud, and 16+ online threats across text, voice, image, and video.
These share tags the maintainers applied themselves, such as cad, dxf, webgl, chatgpt. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
How the author describes it
Topics the maintainer set on GitHub: ai-agents, artwork, autocad, cad, chatgpt, claude, dieline, dxf, dxf-parser, dxf-viewer, mcp, mcp-apps, mcp-server, packaging, pdf-drawing, pdf-x4, prepress, react, typescript, webgl.
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json