# Aspicio MCP server

DXF and PDF/X-4 for AI agents: structured facts, PNG renders, an interactive in-chat viewer.

## Links
- Registry page: https://www.getdrio.com/mcp/io-github-frontsail-ai-aspicio
- Repository: https://github.com/frontsail-ai/aspicio
- Website: https://aspicio.frontsail.app

## Install
- Command: `npx -y @aspicio/mcp`
- Endpoint: https://aspicio-api.frontsail.app/mcp
- Auth: Not captured

## Setup notes
- Package: Npm @aspicio/mcp v0.12.0
- Remote endpoint: https://aspicio-api.frontsail.app/mcp

## Tools
- describe_dxf (Describe a DXF drawing) - 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. 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. Endpoint: https://aspicio-api.frontsail.app/mcp
- render_dxf (Render a DXF to an image) - 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. 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. Endpoint: https://aspicio-api.frontsail.app/mcp
- describe_pdf (Describe a PDF drawing) - 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. 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. Endpoint: https://aspicio-api.frontsail.app/mcp
- render_pdf (Render a PDF to an image) - 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. 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. Endpoint: https://aspicio-api.frontsail.app/mcp
- describe_doc (Describe a drawing of any supported format) - 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. 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. Endpoint: https://aspicio-api.frontsail.app/mcp
- render_doc (Render a drawing of any supported format) - 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. 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. Endpoint: https://aspicio-api.frontsail.app/mcp
- view_dxf (Open a drawing in the interactive viewer) - 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). Endpoint: https://aspicio-api.frontsail.app/mcp
- load_dxf_for_viewer (Load a DXF for the viewer widget) - Internal: returns DXF bytes (base64) for the in-chat viewer. Called by the widget, not the model. Endpoint: https://aspicio-api.frontsail.app/mcp

## Resources
- ui://aspicio/viewer-v2.html - Aspicio DXF viewer Interactive in-chat DXF viewer (pan, zoom, layer toggles). MIME type: text/html;profile=mcp-app

## Prompts
Not captured

## Metadata
- Owner: io.github.frontsail-ai
- Version: 0.12.0
- Runtime: Npm
- Transports: STDIO, HTTP
- License: Not captured
- Language: Not captured
- Stars: Not captured
- Updated: Aug 2, 2026
- Source: https://registry.modelcontextprotocol.io