Builtwith MCP Server

BuiltWith API as an MCP server for Claude Desktop, Cursor, and other AI clients

Local serverstdio

What is the Builtwith MCP server?

BuiltWith API as an MCP server for Claude Desktop, Cursor, and other AI clients. That is what the builtwith mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

Query the BuiltWith API from your app, terminal, or AI agent.

Getting it running

Installation goes through your MCP client rather than a global install: point it at @modelcontextprotocol/inspector on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

The tools it exposes

The server publishes 14 tools. What each one is for:

  • Method — Description
  • free — Free technology summary
  • domain — Full domain technology lookup
  • lists — Sites using a technology
  • relationships — Related domains
  • keywords — Domain keyword extraction
  • trends — Technology adoption trends
  • companyToUrl — Company name to domains
  • domainLive — Live domain detection
  • trust — Trust & fraud signals
  • tags — IP & attribute lookups
  • recommendations — Technology suggestions

What it needs from you

Configuration is passed through the environment: BUILTWITH_API_KEY, YOUR_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Builtwith.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Plenty of payments and commerce servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Builtwith's toolset — Method, free, domain and 11 more — is a fair guide to whether it matches your workflow. It is maintained by zachcaceres; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
MethodDescription
freeFree technology summary
domainFull domain technology lookup
listsSites using a technology
relationshipsRelated domains
keywordsDomain keyword extraction
trendsTechnology adoption trends
companyToUrlCompany name to domains
domainLiveLive domain detection
trustTrust & fraud signals
tagsIP & attribute lookups
recommendationsTechnology suggestions
redirectsRedirect chain history
productE-commerce product search

How to install the Builtwith MCP server

Or passing the key directly:

```json
{
  "mcpServers": {
    "builtwith": {
      "command": "npx",
      "args": ["-y", "builtwith-mcp", "--api-key", "YOUR_KEY"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
BUILTWITH_API_KEYCredential the server authenticates with.Yes
YOUR_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Builtwith to Method.
  • Use Builtwith to free.
  • Use Builtwith to domain.

Frequently asked questions

It connects Builtwith to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (Method, free, domain, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Builtwith directly.