TL;DR — Use Filewisp MCP in Cursor to bring project documents, specifications, and shared file context into your development workflow.
Code is rarely the only context a development task needs. Product requirements, architecture notes, customer examples, and release checklists often live in files outside the repository. Filewisp MCP lets Cursor search that context from the same workspace.
Cursor can work with the code in your project, but useful decisions may be documented elsewhere. A controlled Filewisp connection helps you locate those documents without manually exporting them into the project.
This works particularly well for teams that keep shared material in Filewisp and source code in Git.
Open the Filewisp MCP server page, create an API key, and add the MCP server to Cursor using the client’s MCP configuration flow.
Use a key that exposes only the spaces Cursor needs. If a project has separate client or internal workspaces, keep those boundaries separate instead of using one broad credential.
After connecting, you can ask Cursor to:
The goal is not to replace code review or source control. It is to reduce the time spent hunting for the surrounding context of a change.
MCP access should follow the same rules as any other integration. Create scoped keys, avoid putting secrets in tracked configuration files, rotate credentials when needed, and revoke unused keys.
For the broader workflow, see secure file sharing and semantic file search.