Cursor: MCP setup

Connect Cursor to mountable.io to list filesystems, inspect usage and manage mount sessions through MCP.

The mountable.io MCP server runs locally over stdio. Install Node.js with npx available to the editor, then create an API key with access only to the filesystems you need.

Add the server

Create ~/.cursor/mcp.json for your user. For a project-specific setup, Cursor also reads .cursor/mcp.json; keep any file containing a real key out of Git.

Merge this mountable entry into the existing mcpServers object rather than replacing other servers:

{
  "mcpServers": {
    "mountable": {
      "command": "npx",
      "args": ["-y", "mountable-cli@0.8.0", "mcp"],
      "env": { "MOUNTABLE_API_KEY": "REPLACE_WITH_YOUR_KEY" }
    }
  }
}

Replace REPLACE_WITH_YOUR_KEY in your private local configuration. Never paste the key into a chat, commit it, or pass it as a command argument. If npx is not on the editor’s PATH, use its absolute path.

Check the connection

Open Cursor’s MCP settings and enable mountable. Restart Cursor after changing the config. With the Cursor CLI, you can check discovery without a model call:

cursor-agent mcp enable mountable
cursor-agent mcp list-tools mountable

The discovery command lists ten tools with CLI 0.8.0.

Ask the agent to call list_filesystems. The result contains the filesystems your key can access; an empty list is valid. Review the call before approving it. An authentication error means you should check the key and its grants, then restart the server.

The MCP tools manage filesystems, usage, mount sessions and webhooks. To read or write file contents, use a mount or the Python/TypeScript SDKs. Mounting remains a separate local command; wait for its mounted event before using the directory.

See the ten MCP tools, permissions, billing and Cursor’s configuration guide.