Introducing Filewisp MCP — Use Your Files Directly from Claude, ChatGPT, and Cursor

If you live in Claude, ChatGPT, or Cursor all day, switching tabs to find a file you uploaded last week is friction you shouldn't have to deal with. Today we're shipping a Model Context Protocol (MCP) server for Filewisp, so your AI assistant of choice can reach into your files directly.

What you can do now

Once connected, your assistant gets a focused set of tools covering the full file lifecycle:

• Search your files by name or content — semantic and fuzzy, across every space, no more "I think I called it final_v2_FINAL.pdf"
• List spaces and files — browse what you have without opening the dashboard
• Upload new files straight from a conversation
• Fetch a file — get a temporary signed link to open or download it
• Delete files you no longer need
• Manage share links — create, list, update, or revoke shares, with expiration and access controls, all from the chat

Setting it up

Head to the MCP page in your Filewisp dashboard, generate an API key scoped to the spaces you want to expose, and point your client at our MCP endpoint. We support Claude (Desktop and Code), ChatGPT, and Cursor today, with the same connection flow used by any other MCP-compatible client.

Why this matters

Most of the value in Filewisp is the files themselves — the context they hold. MCP closes the loop between "I have a file" and "I want my AI assistant to actually use it," without exporting, copy-pasting, or re-uploading anything.

We're actively expanding the tool surface based on how people use it in practice, so expect more capabilities here soon.