# fileAI MCP server
Source: https://docs.file.ai/mcp/overview

> Give AI assistants secure access to your fileAI workspace through the Model Context Protocol.

MCP server

# fileAI MCP server

Copy pageCopy page

Give AI assistants secure access to your fileAI workspace through the Model Context Protocol.

Copy pageCopy page

The fileAI MCP server lets an AI client such as Claude, Cursor or ChatGPT work with your fileAI workspace through the Model Context Protocol (MCP). Your assistant can browse files and folders, read OCR text and extracted values, upload new files, edit data, run fileForensics and manage file types. What the assistant can reach depends on how you connect: **sign-in runs as you**, so it sees the projects you can open; **an API key runs with that key’s project access**, not your role in the app. The server is hosted. You don’t install anything: you point your client at a URL. For setup steps per client, see [Connect a client](/mcp/connect).

## 

[​

](#what-it-can-do)

What it can do

The server exposes 31 tools. Grouped by task:

Task

Tools

Check the connection and pick a project

`whoami`, `list_projects`

Find and read files

`list_files`, `get_file_ocr`, `get_file_values`

Upload files

`upload_file`, `request_file_upload`, `wait_for_upload`, `create_file_preview`

Edit extracted data

`update_file_values`, `rerun_form_filling`, `update_file_export_status`

Organize folders

`list_directories`, `create_directory`, `manage_directory_documents`, `delete_directory`

Work with schemas and file types

`list_schemas`, `export_schemas`, `list_file_types`, `get_file_type_schemas`, `update_file_type`, `delete_file_types`

Check files with fileForensics

`run_file_forensics`, `get_file_forensics_result`, `retry_forensics`, `delete_forensics_run`

Read workflows and settings

`get_workflow`, `get_workflow_result_groups`, `get_project_settings`, `get_subscription`

Delete files

`delete_files`

See the [tools reference](/mcp/tools) for every parameter.

## 

[​

](#server-urls)

Server URLs

Use the URL for the instance your workspace lives on. Each instance exposes the same tools; only the hostname changes.

Instance

Region

MCP server URL

Default

US

`https://mcp.file.ai/mcp`

`au`

Australia

`https://mcp.au.file.ai/mcp`

`sg`

Singapore

`https://mcp.sg.file.ai/mcp`

`jp`

Japan

`https://mcp.jp.file.ai/mcp`

A workspace belongs to exactly one instance, and **an API key only works on the host that issued it**. Use the same instance you use for the fileAI API; see [Regions](/authentication#regions). If you’re not sure, use the default URL.

## 

[​

](#how-you-connect)

How you connect

The server accepts two kinds of credential:

Client

How it authenticates

Claude apps and Claude Code

**Sign in with fileAI (OAuth).** You log in, pick up to 50 workspaces, and Claude gets a token. No API key needed.

Codex, Cursor, ChatGPT, VS Code and other clients

**API key.** Send your fileAI API key in an `x-api-key` request header. See [Authentication](/authentication).

By default, sign-in works with Claude apps and Claude Code only. Other clients, ChatGPT included, connect with an API key. If a request carries an `x-api-key` header, the server uses it, even when a sign-in token is also present.

### 

[​

](#choosing-a-project)

Choosing a project

An API key belongs to one project, so tools run in that project and ignore `project_id`. A sign-in connection covers every project you can open in the workspaces you picked. Your assistant calls `list_projects` first, then passes the chosen project’s id as `project_id` to the other tools. In practice you just ask: “List my fileAI projects and use _Finance_.” If your assistant leaves out `project_id`, the tool replies with the list of projects so it can ask you which one to use. Ask “Which fileAI account am I connected to?” and it calls `whoami` to show the project, workspace and environment. If you ask for a project outside your connection, the tool tells your assistant that either the project’s workspace wasn’t selected when you signed in, or your account can’t open the project, and lists the projects you can reach. To add the workspace, disconnect and reconnect fileAI, and select it when you sign in.

## 

[​

](#safety-guards)

Safety guards

*   **Confirmation for destructive tools.** `delete_files`, `delete_directory`, `delete_file_types` and `delete_forensics_run` only run when called with `confirm: true`, so they can’t fire by accident.
*   **Soft delete by default.** `delete_files` soft-deletes (recoverable) unless `isHardDelete: true` is set.
*   **Access follows the credential.** With sign-in, the assistant can only reach projects you can open in the workspaces you picked. With an API key, it has that key’s project access whoever set up the client, and a read-only key can only read.

`delete_files` with `isHardDelete: true` deletes files permanently. Check what your assistant is about to delete before you approve the call.

## 

[​

](#personal-information)

Personal information

Claude has rules about sending personally identifiable information (PII) through MCP connectors. Make sure your use case is consistent with Claude’s Terms of Service.

## 

[​

](#related)

Related

## Connect a client

Setup steps for Claude, Codex, Cursor, ChatGPT and VS Code.

## Claude details

Projects, file uploads and troubleshooting in Claude.

## Tools reference

Every tool and its parameters.

## Docs for AI tools

Feed these docs to your coding agent.

[

Connect a client

Use fileAI's document tools from Claude, Codex, Cursor, ChatGPT or VS Code.

Next

](/mcp/connect)

⌘I

## On this page

Back to top

*   [What it can do](#what-it-can-do)
*   [Server URLs](#server-urls)
*   [How you connect](#how-you-connect)
    *   [Choosing a project](#choosing-a-project)
*   [Safety guards](#safety-guards)
*   [Personal information](#personal-information)
*   [Related](#related)