What it can do
The server exposes 32 tools. Grouped by task:
See the tools reference for every parameter.
Server URLs
Use the URL for the instance your workspace lives on. Each instance exposes the same tools; only the hostname changes.
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. If you’re not sure, use the default URL.
How you connect
The server accepts two kinds of credential:
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
An API key belongs to one project, so tools run in that project and ignoreproject_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.”
Safety guards
- Confirmation for destructive tools.
delete_files,delete_directory,delete_file_typesanddelete_forensics_runonly run when called withconfirm: true, so they can’t fire by accident. - Soft delete by default.
delete_filessoft-deletes (recoverable) unlessisHardDelete: trueis set. - Your role applies. Anything you can’t do in the fileAI app, the assistant can’t do either.
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
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.