Convert MCP configuration: Cursor and VS Code

Move MCP configuration between Cursor and VS Code: complete example, format limits and checks. Try the converter with sample data before using your own file.

Published on 1 October 2026 · by tracevero · Reading time 3 minutes (510 words)

An existing MCP configuration can save work when switching editors, provided its meaning survives the move. Start with a copy and one server. Compare its name, command, arguments and environment afterwards. The converter offers a sample you can try first. It computes a file without launching a process. Inspect the result before deciding whether to add it to your own setup.

Choose the file path and format together

Cursor project definitions belong in .cursor/mcp.json. The VS Code format at .vscode/mcp.json uses servers; the portable project format at .mcp.json uses mcpServers. Selecting “VS Code” in this converter specifically means the former format. The VS Code guide explains both locations. Renaming a file does not change the structure inside it.

What can be transferred?
Input	Converter	Next step
Local command, args, env	Converted	Compare values
HTTP URL or additional options	No output	Configure the target client explicitly
TOML or client variables	No output	Check the provider format

Transfer a complete example

This Memory example contains a deliberately replaceable storage path. Copy it as a starting point or click “Convert sample” in the converter. Select Cursor as the source and VS Code as the target. Keep personal credentials out of this experiment. Actually starting the server requires the appropriate runtime and an existing test directory. The Memory guide covers the subsequent storage test.

{
  "mcpServers": {
    "memory": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-memory"
      ],
      "env": {
        "MEMORY_FILE_PATH": "/absolute/path/mcp-test/memory.jsonl"
      }
    }
  }
}

Suggested verification workflow for your environment.

Compare the result before applying it

Inspect the output: the server is still named memory. In the VS Code format it appears under servers with type: stdio.
Compare every argument in order and check the storage path. Conversion does not replace paths or install packages.
Download the result if needed. Add the individual server to your existing configuration without overwriting unrelated definitions.
Start with a test object in the target client. Record the file, client version, actual package version and observed result separately.

Understand a rejected configuration

For unknown options the converter produces no incomplete replacement file. Do not remove those options merely to obtain output: they may determine permissions, working directory or authentication. It also does not silently move ${workspaceFolder} into another context. For startup failures use the troubleshooting navigator. Successfully rewritten JSON confirms conversion of the supported fields, not a working connection.

Will my servers be started?: No. Conversion only computes text. A server starts when you use the configuration in a client.
Does the example work immediately?: Replace the storage path and check the runtime and test directory first. Output is not proof of installation.
Can I convert HTTP servers?: This converter supports local startup definitions. Use the target client guide for remote connections.
Why is TOML rejected?: This format conversion is unsupported. An empty success message would imply a check that did not happen.

Provider documentation checked on 1 October 2026. Verification workflows are editorial suggestions.

VS Code: MCP configuration
Show retrieval command
curl -s https://code.visualstudio.com/docs/agent-customization/mcp-servers
Cursor: MCP
Show retrieval command
curl -s https://cursor.com/docs/mcp

Put it into practice

All posts