​
Choosing your instance

The default MCP server is:
fileAI also runs instance-specific MCP servers. An instance exposes the same tools and differs only in the hostname:
A workspace belongs to exactly one instance, and an API key only authenticates against the host that issued it. Use the same instance here as the one you use for the fileAI API.
Use the default URL unless you know your workspace is on an instance; every configuration below uses the default host, so swap in your instance’s URL from the table above wherever https://mcp.file.ai/mcp appears.

​
Configuring Cursor

HTTP Transport
  1. Open Cursor Settings (Ctrl/Cmd + ,)
  2. Navigate to Tools & Integration → MCP Tools
  3. Click + New MCP Server Screenshot 2025-08-18 at 9.55.22 AM.png
Use the configuration below:
Your mcp.json should look like below: Screenshot 2025-08-18 at 9.56.25 AM.png Verify that the MCP Server is set up correctly. You should see that tools are enabled. Screenshot 2025-08-18 at 11.32.45 AM.png

​
Configuring Claude

To add the fileAI MCP Server to Claude:
  1. Go to your Claude Integrations page
  2. Click + Add integration
  3. In the URL field, enter:
  1. Under request headers, add:
Replace YOUR_API_KEY_HERE with your actual fileAI API key. _Please note that Claude has restrictive rules regarding the ability to send PII via MCP. Please ensure that your use case is consistent with Claude’s Terms of Service. _

​
Configuring Windsurf, Cline Github Copilot and other MCP clients

Visit mcp.file.ai to get instructions on how to install fileAI’s MCP Server on other clients. If your workspace is on an instance, use its MCP URL from the table above instead.