Agent-ready local document context with stable anchors.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag β we're steadily working through the catalog.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Read-only document awareness MCP server for agents. File AI uses Flyfish File Viewer core as the source of truth for format recognition, then turns local files into a stable profile, anchors, blocks, chunks, outline, search results, and contextual snippets so an agent can understand document content without reverse-engineering PDF, OOXML, spreadsheet, email, or archive internals.
MCP Registry name: io.github.flyfish-dev/file-ai
Use it directly with npx:
Or install it globally:
Stdio:
Streamable HTTP:
Endpoint:
doc_analyze: parse a local file and cache a document index.doc_read: read blocks, chunks, or anchors from an existing index or path.doc_search: search cached content with source anchors.doc_context: retrieve nearby blocks around an anchor or query.doc_list_formats: list File Viewer core registry formats, all supported extensions, renderer capabilities, and File AI extractor coverage.doc://{indexId}/profiledoc://{indexId}/outlinedoc://{indexId}/chunksFile AI recognizes formats through @file-viewer/core/headless, currently covering 206 registered extensions. profile.format is therefore aligned with the same renderer selection used by Flyfish File Viewer.
Content extraction is a separate layer. File AI provides structured awareness for text/code/Markdown/JSON, PDF text, DOCX, XLSX/CSV, PPTX, EML, and archive manifests. Other File Viewer renderer-only formats such as CAD, 3D, media, image, geospatial, drawing, ebook, and data assets are still recognized in profile.format; when no structured text extractor exists yet, File AI returns a profile plus best-effort metadata/text and explicit warnings in profile.warnings and profile.extraction.
Every content block carries an anchor such as a page, slide, worksheet, row range, nested path, or byte/text location. Agents should cite returned anchorId values when making document-grounded claims.
Run locally:
The package includes:
@flyfish-dev/file-aiserver.json.github/workflows/publish-mcp.ymlRelease flow:
The workflow publishes the npm package first, then publishes io.github.flyfish-dev/file-ai to the official MCP Registry through GitHub OIDC. The repository must have an NPM_TOKEN secret that can publish @flyfish-dev/file-ai.
The server is read-only. It does not mutate source documents.
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/file-ai)<a href="https://allmcps.com/mcp/file-ai"><img src="https://allmcps.com/api/badge/file-ai?style=directory" alt="File AI on AllMCPs" /></a>