Set up Wield in Cursor

#Does Cursor run local MCP servers?

Yes. Cursor starts local servers that use stdio, and it shows each server's state in its MCP settings. Wield works this way. Cursor launches wield-mcp, which sends each request to your browser through a local bridge and the Wield extension.

#Config file and location

Cursor also supports ${workspaceFolder} and ${env:NAME} interpolation. Wield does not need either.

#The Wield snippet

{ "mcpServers": { "wield": { "command": "npx", "args": ["-y", "wield-mcp"] } } }

The command must be on your PATH, or you can use the full path to npx. If Cursor rejects the entry, add "type": "stdio" to the wield block. The Cursor docs list type as required, but their examples leave it out.

The simpler route is npx -y wield-mcp init. Answer yes for Cursor, and the installer writes the entry for you and backs up the file first.

#Check that it works

1. Open Cursor's MCP settings. The wield server appears with its state. Toggle it off and on after you edit the file.
2. Ask the agent for a Wield task, for example "Search Kleinanzeigen for a used road bike in Hamburg under 400 €."
3. In a terminal, run npx -y wield-mcp check. It ends with "Wield is ready" when the browser path works.

#Gotchas

• Minimal PATH. GUI apps often start with a short PATH. If npx is not found, use the absolute path that init prints.
• Extension and bridge. The MCP entry alone is not enough. Install the extension and bridge from /install.
• Browser open. Wield runs only while your Chromium browser is open. The window does not need to be visible.
• Writes wait for you. A booking or message stops before its first write request and shows an Allow window. Deny is the default.

#FAQ

#Should I use the global file or the project file?

Use ~/.cursor/mcp.json when you want Wield in every project. Use .cursor/mcp.json when only one project needs it.

#Why does Cursor show no Wield tools?

The usual causes are a server that is not toggled on, an npx that is not on the PATH, or a browser where the extension is not connected. Run npx -y wield-mcp doctor. It checks each link in the chain and prints a fix for each problem.

#Does Wield need Cursor's environment interpolation?

No. For Pro or Team features, set WIELD_API_KEY in the server's environment. The free public recipes need no key.

#Where are the Wield logs?

Wield logs every request on your computer only, in ~/.wield/logs. The executor log records the method, host, path, status and timing of each request that a recipe makes. The MCP log records the requests that wield-mcp makes to wield.run. Neither log contains request bodies, query values, parameters or results.