Connect Other AI Apps

Open Settings › AI › Other AI apps, click Show setup, and paste the block for your app into its settings file, and that app can search, read and edit your project.

Where: Settings (the menu button, top right) › AI › Connect an AI app › Other AI apps

What it is

Every app other than Claude Desktop is set up by hand, and Settings gives you the exact block, with the paths for your computer already filled in. There are five blocks because the apps disagree on the shape, and an app given the wrong one usually ignores it without any error.

How to use it

1. Open the project you want the AI to work on, then open Settings › AI.
2. Click Show setup beside Other AI apps.
3. Copy the block for your app and paste it into the settings file named under Where each app keeps its settings file.
4. Restart the app, or reload its MCP servers, so it starts the Filamental server.

Claude Desktop, Claude Code, Cursor, Gemini CLI, LM Studio read mcpServers:

{
  "mcpServers": {
    "filamental": {
      "command": "node",
      "args": [
        "--no-warnings",
        "/absolute/path/to/filamental-mcp/dist/index.js",
        "--vault",
        "/absolute/path/to/your/project"
      ]
    }
  }
}

VS Code and Copilot read servers, and each entry declares its type. Paste the mcpServers version into VS Code and it's simply ignored, with no error, which is a frustrating twenty minutes if you don't know to look:

{
  "servers": {
    "filamental": {
      "type": "stdio",
      "command": "node",
      "args": ["--no-warnings", "/absolute/path/to/filamental-mcp/dist/index.js", "--vault", "/absolute/path/to/your/project"]
    }
  }
}

Zed reads context_servers, with the same command and args.

Codex reads a TOML table in config.toml:

[mcp_servers.filamental]
command = "node"
args = ["--no-warnings", "/absolute/path/to/filamental-mcp/dist/index.js", "--vault", "/absolute/path/to/your/project"]

The block in Settings already escapes Windows backslashes. If you type a path yourself, use forward slashes.

Where each app keeps its settings file

The portable version, for a file you commit

The blocks above carry two paths that only exist on your computer. The portable one travels:

{
  "mcpServers": {
    "filamental": {
      "command": "npx",
      "args": ["-y", "filamental-mcp", "--vault", "./your-space-folder"]
    }
  }
}

It fetches the server from npm rather than your install, and reads the project path relative to the folder the app starts in, so a .mcp.json holding it works for everyone who clones the repository. Each person still has to open the folder in Filamental once, because of the index. It's usually a little slower to start, so on your own computer the direct block is the better one.

Tips

• The block names the project that was open when you copied it. That app stays on that project. Take out "--vault" and the path after it, and it follows whichever project you open in Filamental, as Claude Desktop does.
• Any app that can start a local process and talk to it over stdio will work, not only the ones named. Open WebUI is the exception, since it only supports MCP over HTTP.
• Node.js 22 or later has to be installed, and the project opened in Filamental once on that computer. See Connect an AI App.

How this helps you

Use it when your AI lives in a terminal or an editor: Claude Code beside a repository, Copilot in VS Code, Codex at the command line. The assistant you already have open reaches the project the same way, and a team can point at one project by committing one file.

Related

• Connect Claude Desktop: the one-click route.
• Connect an AI App: what a connected AI can do.
• Folder Access: for an AI that reads your files directly.
• AI on Your Own Computer: Filamental AI on LM Studio, which isn't the same as LM Studio over MCP.