English Français العربية

File AI

Official registry Productivity

Agent-ready local document context with stable anchors.

Source code Website Documentation

What can you do with File AI?

  • 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.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package @flyfish-dev/file-ai
Claude Code 
claude mcp add file-ai -- npx -y @flyfish-dev/file-ai@0.1.1
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "file-ai": {
            "command": "npx",
            "args": [
                "-y",
                "@flyfish-dev/file-ai@0.1.1"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. File AI
  2. Install
  3. MCP Client Config
  4. Tools
  5. Resources
  6. Supported Files
  7. Development
  8. Publishing

File AI

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

Install

Use it directly with npx:

npx -y @flyfish-dev/file-ai

Or install it globally:

npm install -g @flyfish-dev/file-ai
file-ai --transport stdio

MCP Client Config

Stdio:

{
  "mcpServers": {
    "file-ai": {
      "command": "npx",
      "args": ["-y", "@flyfish-dev/file-ai"]
    }
  }
}

Streamable HTTP:

npx -y @flyfish-dev/file-ai --transport http --host 127.0.0.1 --port 8765

Endpoint:

http://127.0.0.1:8765/mcp

Tools

  • 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.

Resources

  • doc://{indexId}/profile
  • doc://{indexId}/outline
  • doc://{indexId}/chunks

Supported Files

File 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.

Development

pnpm install
pnpm build
pnpm test
pnpm validate:skill

Run locally:

pnpm dev -- --transport stdio
pnpm dev -- --transport http --port 8765

Publishing

The package includes:

  • npm metadata for @flyfish-dev/file-ai
  • MCP Registry metadata in server.json
  • GitHub Actions workflow .github/workflows/publish-mcp.yml

Release flow:

git tag v0.1.0
git push origin v0.1.0

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.

Frequently asked questions

What is File AI?

Agent-ready local document context with stable anchors.

How do I install File AI?

It runs on your machine. In Claude Code: claude mcp add file-ai -- npx -y @flyfish-dev/file-ai@0.1.1. For other clients, paste the JSON configuration from this page into their MCP settings.

Does File AI need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is File AI open source?

Yes. Its code is on GitHub under the Apache-2.0 license.

Who maintains File AI?

It is published by flyfish-dev. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.