Use with Cursor
Cursor reads MCP servers from a JSON config file. You can configure them either globally or per-project.
Config file location
| Scope | Path |
|---|---|
| Global | ~/.cursor/mcp.json |
| Project | .cursor/mcp.json (in your repo root) |
Per-project config takes precedence over global config for that workspace.
Example
json
{
"mcpServers": {
"native-time": {
"command": "/home/you/.local/bin/native-mcp",
"args": ["time"]
},
"native-time-paris": {
"command": "/home/you/.local/bin/native-mcp",
"args": ["time", "--default-tz", "Europe/Paris"]
}
}
}Use the absolute path to the binary — Cursor does not always inherit your shell's PATH.
Apply
Reload Cursor (or its MCP subsystem from the command palette). The new servers should appear in the agent's available-tools panel on the next chat.
Project-scoped + checked into git
Putting .cursor/mcp.json in version control gives every collaborator the same MCP setup. Since native-mcp is a single binary on a known path, this works as long as everyone has run the installer.