MCP Market
MCP install guide

Cursor MCP JSON config example

Copy a working Cursor mcp.json example and learn how to adapt install commands into MCP config.

Who is this for?

Users who already have an MCP command and need the correct Cursor JSON format.

Config path and example

~/.cursor/mcp.json

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "./"]
    }
  }
}

Installation steps

1

Start with mcpServers

Cursor expects MCP servers under a top-level mcpServers object.

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "./"]
    }
  }
}
2

Split command and args

The first token becomes command. Everything after it becomes args.

3

Keep server names readable

Use stable names like filesystem, github, postgres, or browser.

4

Validate JSON

A missing comma or quote can prevent Cursor from loading the server.

Common setup issues

Putting the full command in command

Do not set command to the entire string. Use command: npx and args: [...] instead.

Wrong path

Make sure you are editing the Cursor config file used by your current profile.

FAQ

What should command contain?

Only the executable, such as npx, uvx, docker, node, or python.

What should args contain?

All remaining command tokens, for example -y and the package name.