MCP config generator

{
  "name": "filesystem",
  "transport": "stdio",
  "command": "npx",
  "args": [
    "-y",
    "@modelcontextprotocol/server-filesystem",
    "/Users/you/projects"
  ],
  "env": [],
  "clients": [
    "claude",
    "cursor",
    "codex",
    "vscode",
    "opencode"
  ],
  "scope": "both"
}

MCP server: filesystem (stdio)
Checked against vendor documentation on 2026-10-13. Client formats change, so if a client rejects this output, compare it with the documentation linked below.

Checks (3)
- Note: A path in the command or arguments points into a home folder. It will not exist on a teammate machine, so replace it before you commit a project-scope file.
- Note: Project-scope files (.mcp.json, .cursor/mcp.json, .codex/config.toml, .vscode/mcp.json, opencode.json) are usually committed to git, so everyone who clones the repository gets these servers. Add a file to .gitignore if it should stay private.
- Note: Commands use POSIX shell quoting (macOS, Linux, WSL, Git Bash). PowerShell and cmd.exe quote differently.

== Claude Code ==
File, user scope: ~/.claude.json. Top-level mcpServers key. The file also holds other Claude Code state.
File, project scope: .mcp.json. At the project root. Claude Code asks you to approve its servers.

{
  "mcpServers": {
    "filesystem": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "/Users/you/projects"
      ]
    }
  }
}

Equivalent command, user scope:
claude mcp add --transport stdio --scope user filesystem -- npx -y @modelcontextprotocol/server-filesystem /Users/you/projects

Equivalent command, project scope:
claude mcp add --transport stdio --scope project filesystem -- npx -y @modelcontextprotocol/server-filesystem /Users/you/projects

- Note: Merge the entry into the top-level mcpServers key of ~/.claude.json and keep the rest of that file.
- Note: The default scope of claude mcp add is local: private to you and stored in ~/.claude.json under the current project. The commands here pass --scope user or --scope project, so they write the files listed above.
- Note: An entry that has a url and no type is read as a stdio server and fails, so the type field is always written.
Documentation: https://code.claude.com/docs/en/mcp

== Cursor ==
File, user scope: ~/.cursor/mcp.json
File, project scope: .cursor/mcp.json. At the project root.

{
  "mcpServers": {
    "filesystem": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "/Users/you/projects"
      ]
    }
  }
}

- Note: No add command is documented for Cursor, so edit the file.
- Note: Cursor merges both files, and the project entry wins when the same server name appears in both.
- Note: Cursor resolves ${env:NAME}, ${userHome}, and ${workspaceFolder} in command, args, env, url, and headers.
Documentation: https://cursor.com/docs/mcp

== Codex ==
File, user scope: ~/.codex/config.toml
File, project scope: .codex/config.toml. Read only for trusted projects.

[mcp_servers.filesystem]
command = "npx"
args = ["-y", "@modelcontextprotocol/server-filesystem", "/Users/you/projects"]

Equivalent command:
codex mcp add filesystem -- npx -y @modelcontextprotocol/server-filesystem /Users/you/projects
Adds the server through the Codex CLI. Run codex mcp list to confirm it, and check the entry in the config file.

- Note: The top-level table is mcp_servers, not mcpServers.
- Note: Codex reads project configuration only for trusted projects. The Codex app, CLI, and IDE extension share this configuration.
Documentation: https://developers.openai.com/codex/mcp

== VS Code ==
File, user scope: mcp.json in your VS Code user profile folder. Run MCP: Open User Configuration from the Command Palette. The location depends on your operating system and profile, so no fixed path is given.
File, project scope: .vscode/mcp.json. In the workspace folder.

{
  "servers": {
    "filesystem": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "/Users/you/projects"
      ]
    }
  }
}

Equivalent command:
code --add-mcp '{"name":"filesystem","command":"npx","args":["-y","@modelcontextprotocol/server-filesystem","/Users/you/projects"]}'
The documentation says this adds the server to your user profile or to a workspace.

- Note: VS Code uses the root key servers, not mcpServers.
- Note: VS Code can prompt for a secret when the server first starts and then store it. Add an inputs entry with type promptString and password set to true, and reference it as ${input:id}.
Documentation: https://code.visualstudio.com/docs/agents/reference/mcp-configuration

== OpenCode ==
File, user scope: ~/.config/opencode/opencode.json
File, project scope: opencode.json. At the project root.

{
  "mcp": {
    "filesystem": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "/Users/you/projects"
      ],
      "enabled": true
    }
  }
}

- Note: No add command is documented for OpenCode, so edit the file.
- Note: This is the layout in the main OpenCode documentation, with servers directly under mcp and the arguments inside the command array. The v2 documentation pages show servers under mcp.servers and use disabled in place of enabled, so check which version you run.
Documentation: https://opencode.ai/docs/mcp-servers/