The fileAI MCP server exposes 32 tools. Each one calls the fileAI API as you, on the instance your connection points at. Your assistant picks the tool and fills in the parameters; this page tells you what each tool can do so you know what to ask for.

Parameters every tool shares

  • project_id (string, optional): the project to work in, as a 24-character id from list_projects. Required when you connected by signing in to fileAI (Claude). Ignored when you connect with an API key, because the key already belongs to one project. Every tool except list_projects accepts it. See Choosing a project.
  • confirm (true, required): only on destructive tools: delete_files, delete_directory, delete_file_types and delete_forensics_run. The call is rejected unless it is exactly true.
  • Pagination: list tools marked paginated also accept page (integer), limit (integer), sortBy (string), sortOrder (ASC or DESC) and cursor (string, from the previous response). See Pagination.
Ids that go into a URL path (fileId, uploadId, workflowId, directoryId, run_id, analysis_id) accept only letters, digits, _ and -.

Projects

Files and uploads

delete_files with isHardDelete: true deletes files permanently.

Uploading a file

No file bytes pass through the MCP server. Your client uploads them straight to fileAI storage.
1

Request an upload URL

Call request_file_upload with fileName and fileType. It returns presignedUploadURL, uploadId and s3Path.
2

Upload the bytes

Send the raw file with an HTTP PUT to presignedUploadURL. The URL is already signed, so don’t add x-api-key.
3

Wait for processing

Poll get_upload with the uploadId until processing finishes.
4

Read the results

Call get_file_values and get_file_ocr.
In Claude, the upload runs from the code sandbox, which needs network access to your instance’s storage domain. See Connect Claude → File uploads.

Values and schemas

File types

A file type is the kind of document, such as Invoice or Bank statement, that an AI Schema belongs to. The API calls it a blueprint, so tool parameters use blueprintId. See Concepts.

Folders

Forensics

fileForensics checks a stored file for signs of editing, AI generation, reuse and hidden content. See fileForensics for what it does and Detectors for what each check looks for. Accepted checks values (17): web_presence, ai_gen_detection, ai_text_detection, copy_move, exact_duplicate, provenance_credentials, generation_toolchain, producer_divergence, encryption_permissions, active_content, digital_signature, attachments, revision_history, magic_byte, polyglot, trailing_data, entropy. The API’s ai_pdf_detection and ai_office_detection are not offered through MCP; use POST /v1/forensics for those. Results also carry a billing field. It is a placeholder: don’t rely on it to track usage or cost.

Workflows

Workspace

fileAI MCP server

Server URLs, sign-in and safety guards.

Connect a client

Set up Claude, Codex, Cursor, ChatGPT or VS Code.

Claude details

Projects, file uploads and troubleshooting in Claude.