@wpbevel/bridge

A local MCP server that runs where the files are. A remote Bevel site cannot read a laptop folder and MCP carries no file bytes, so a desktop assistant (Claude Desktop, Cursor, Claude Code) needs a hand on the user's machine. This is that hand: "use the logo in ~/Brand" uploads it with no click.

Setup

Create a connection on the site under Bevel → MCP Connectors and copy its URL (the one with the token). Then:

claude mcp add bevel-bridge -e BEVEL_MCP_URL="https://site.example/wp-json/bevel-mcp/v1/mcp?token=…" -- npx -y @wpbevel/bridge

For Claude Desktop or Cursor, the same server in their MCP config:

{
  "mcpServers": {
    "bevel-bridge": {
      "command": "npx",
      "args": ["-y", "@wpbevel/bridge"],
      "env": { "BEVEL_MCP_URL": "https://site.example/wp-json/bevel-mcp/v1/mcp?token=…" }
    }
  }
}

Keep the site's own connector too: the bridge only moves files; building happens through the site.

Tools

• list_files {folder, extensions?, recursive?} lists images and fonts in a folder.
• upload_files {paths, family?, title?, alt?} sends files to the site. It asks the site for an upload link, POSTs each file, and returns the media id, URL and tone for images, or the family, weight and style for fonts. Paths accept ~ and globs. Font files need family.

The same bytes always return the same asset, and a busy link is retried with backoff.

Node 18.17 or newer. No dependencies.