Skip to content
unfenced.ai

Claude Desktop integration

On this page

Claude Desktop can connect to Unfenced through a custom remote connector. If you use local MCP configuration instead, the npm bridge forwards the same tools to Unfenced.

Connect through Claude settings

If your Claude account offers custom connectors, open Settings → Connectors → Add custom connector. Enter:

Agent prompt
https://unfenced.ai/api/mcp

Leave OAuth Client ID and Secret blank. Connect, sign in to Unfenced, and approve access. This path uses OAuth; you do not paste an API key. The connector is also available through Claude's web and mobile apps on the same account.

Use the local bridge instead

For local stdio MCP configuration, install a supported Node.js release and create an Unfenced API key. The bridge's current Node requirement is in the package documentation.

Open Claude Desktop's developer settings and edit its MCP configuration. Merge this server into the existing mcpServers map:

JSON
{
  "mcpServers": {
    "unfenced": {
      "command": "npx",
      "args": ["-y", "-p", "@unfenced-ai/mcp", "unfenced-mcp"],
      "env": {
        "UNFENCED_URL": "https://unfenced.ai/api",
        "UNFENCED_TOKEN": "YOUR_API_KEY"
      }
    }
  }
}

Replace YOUR_API_KEY in this private local file with your Unfenced key. Do not share or commit the file. Restart Claude Desktop afterward.

The bridge runs on your machine, but the browser and website access run on Unfenced. You still need an Unfenced account. The -p argument selects the npm package; unfenced-mcp is its executable.

Try your first fetch

Enable the connector in a conversation if required, then ask:

Agent prompt
Use Unfenced fetch_page to read https://example.com.
Return a short summary and the source URL.

Look for an Unfenced tool call and a summary of Example Domain.

If it does not connect

  • Custom connector unavailable: use the bridge if your client supports local MCP configuration.
  • Bridge will not start: check Node and npx are available to Claude Desktop.
  • Unauthorized: verify the key or reconnect the OAuth connector.
  • No tools after a change: restart the app or reconnect the server.

What to try next

Read authenticated pages or compare several sources. The Unfenced MCP package guide documents the bridge.

Configuration reviewed: 2026-10-04. Check the connection in your client before relying on it.

Request accessSign in