Set up Wield in Cline

#Does Cline run local MCP servers?

Yes. Cline reads MCP servers from a JSON settings file and starts each stdio server as a local process. Wield works the same way. Cline starts wield-mcp on your computer, and the server opens no network port. Wield's tools then reach the browser through a local bridge.

#Config file and location

Cline keeps its MCP settings in one JSON file. Where you find it depends on how you run Cline.

#The Wield snippet

Add this entry under mcpServers:

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

If the file already has other servers, add the wield key next to them. Keep the name wield. Leave autoApprove empty, so Cline keeps asking before it runs a Wield tool. Wield also shows its own Allow window before any write request, and no setting turns that window off.

npx -y wield-mcp init does not add Wield to Cline. It sets up Claude Desktop, Claude Code, Cursor and Codex only. Run init once anyway. It installs the bridge that your browser needs, even if you configure the app by hand.

#Install the browser part

Wield has two parts. The MCP server runs in Cline. The Wield extension runs recipes in your browser. Install both with the quick start, or start at wield.run/install. Wield is not in the Chrome Web Store yet, so the quick start also shows the unpacked install steps for Chromium browsers.

The extension popup should say Bridge connected. If it does not, Cline cannot reach a browser, and no recipe runs.

#Check that it works

1. Restart your AI app so it starts wield-mcp again.
2. In a terminal, run npx -y wield-mcp check. It makes one live, read-only sample through your browser and ends with "Wield is ready".
3. In Cline, ask a plain question, for example: "Use Wield to find a train from Berlin to Munich tomorrow morning."

Cline first calls find_recipe to pick a recipe, then run to execute it in your browser. The answer comes back in the chat. Results pass from the extension to wield-mcp to Cline. They never pass through wield.run.

#Gotchas

#FAQ

#Does Cline support MCP?

Yes. Cline supports local stdio MCP servers through cline_mcp_settings.json. Wield uses the same stdio setup as other MCP servers. See Configuring MCP servers in Cline.

#Why doesn't npx -y wield-mcp init add Wield to Cline?

The installer only writes config for Claude Desktop, Claude Code, Cursor and Codex. Add the Cline entry by hand, as shown above. Run init once as well, so the bridge is installed.

#Does Cline get my passwords or cookies?

No. Recipes run in your browser with the session you already have. Passwords and cookies never leave your computer. Wield never reads, copies or sends them. Cline only receives the results of each run.

#Can Cline book or send something for me?

Only with your approval. Any write, such as a booking or a message, stops before its first write request. Wield then shows a window with every request and its body. Deny is the default, and two minutes without an answer count as a deny. One Allow covers one run.

#Do I need an API key?

No. The free public recipes run without one. The key field is optional and matters only for paid plans. Store a key in ~/.wield/config.json or in the server environment, not in a shared file.