Builtwith MCP

MCP数据服务

提供方 builtwith

数据服务 未标注 Token 社区 / 第三方 Claude DesktopClaudeCursor

BuiltWith MCP是一款模型上下文协议服务器,允许AI助手直接查询BuiltWith的技术检测数据,支持自托管或托管服务。

一句话选型结论

按资料字段整理

Builtwith MCP 属于数据服务类 MCP 服务器,传输方式未标注,Token,可直接接入 Claude Desktop、Claude、Cursor,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类数据服务 传输方式未标注 鉴权Token 部署方式未标注
GitHub 星标 39 仓库热度,无公开仓库时显示未标注
工具数 22 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

数据服务
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量22暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

AI助手集成JavaScript本地部署技术检测数据分析API服务自托管

安装与配置

未标注 Token
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后客户端会列出约 22 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
数据库查询

用自然语言查库、取数,不用手写 SQL。

数据同步与清洗

把多来源数据拉到一处做整理。

报表取数

按口径快速拉出统计结果。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注 22 个工具,覆盖面较广,能满足多种调用。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好Token对应的凭据,并按最小权限配置。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在数据服务场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Builtwith MCP当前 22 未标注 未标注 无 2026-05-17
Memory 9d25f64e 9 未标注 未标注 无 2026-05-17
Getzep MCP 9 stdio · 本地进程 本地部署 有 2026-05-17
anything-llm 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Prisma MCP Server 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Astr Bot 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

数据服务
字段来自项目仓库与公开索引,中文说明由本站标注
提供方builtwith上游标注的维护方 builtwith
分类数据服务本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式Token远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

7.8 KB
来自项目仓库与上游目录的原文,未做删改

🔍 BuiltWith MCP Server 🚀

Domain API v25

Domain lookups now use API v25. Technology records include numeric confidence scores from 0 to 1. Full JSON responses include Meta.company_reg, an array of company registration records with string type and number fields; registration numbers preserve leading zeros. The array is empty when unavailable or metadata is excluded. See the API reference. Full domain methods preserve both fields; live technology lookups include confidence and return technology records only.

🌟 Overview

BuiltWith MCP is a Model Context Protocol (MCP) server that allows AI assistants (Claude, Cursor, IDE agents, etc.) to query BuiltWith’s technology detection data directly and natively.

It enables natural-language questions like:

> “What technologies does example.com use?”
> “Does this site run Shopify or Magento?”
> “What analytics stack is used by nytimes.com?”

BuiltWith MCP supports bring-your-own BuiltWith API key and can be used either as a hosted service or self-hosted.


Claude DEMO

Shows how to get this working in Claude as a Connector

https://github.com/user-attachments/assets/1199362a-c813-497e-8569-15b9a3ce9713

🌐 Hosted MCP (Recommended)

BuiltWith provides a hosted MCP endpoint — no local Node process required.

Endpoint```

https://api.builtwith.com/mcp


### Authentication

Bring your own BuiltWith API key:```
Authorization: Bearer YOUR_BUILTWITH_API_KEY

Example MCP request```json

{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/list"
}


---

## Python SDK integration

The official Python SDK connects to
this existing hosted MCP server. Install `pip install "builtwith-official[mcp]"`
and set `BUILTWITH_API_KEY` in your environment:```python
from builtwith_official.mcp import connect_mcp

async def discover_tools() -> None:
    async with connect_mcp() as session:
        print(await session.list_tools())
        # Uses API credits when invoked:
        # result = await session.call_tool("domain-api", {"lookup": "example.com"})

The client uses the existing tool names and schemas; it does not run another server.
See the Python MCP guide.

🧩 Supported Tools

The hosted MCP exposes the following tools:

  • domain-lookup – Live technology detection for a domain
  • domain-api – Full domain metadata
  • change-api – Technology additions and removals with business context
  • lists-api – Sites using a technology, including OTHERTECHS and numeric attribute filters such as SPEND, REVENUE, and EMPLOYEES
  • relationships-api – Related websites
  • free-api – Category and group counts
  • company-to-url – Company → domain discovery
  • tags-api – IP / attribute based discovery
  • recommendations-api – Technology recommendations
  • redirects-api – Live and historical redirects
  • keywords-api – Keyword intelligence
  • trends-api – Technology trend data
  • product-api – Ecommerce product search
  • trust-api – Trust scoring
  • vat-api – VAT, GST, and other company registration numbers for websites
  • vat-types-api – Reference list of registration types returned by vat-api (no API key required)
  • whoami-api – Account limits, credit costs, and endpoint inventory (no API credits)
  • usage-api – Current credit balance (no API credits)
  • mcp-registry-api – Search and browse the BuiltWith MCP registry (v1) of other remote MCP servers (no API credits)
  • mcp-registry-v2-api – Search and browse the BuiltWith MCP registry (v2) of other remote MCP servers, with per-endpoint auth flags and first/last detected dates (no API credits)
  • vector-search – Semantic similarity search across technologies and categories
  • ask-api – Natural language website list lookup (e.g. "Magento websites in Spain"); supports full reports and pagination
  • payment-balance – Check your API credit balance
  • payment-config – Retrieve your payment configuration
  • payment-purchase – Purchase API credits using your saved Stripe payment method
  • agent-auth-start – Start Agent Device-Code Authorization (no API key required)
  • agent-auth-token – Poll for authorization result and retrieve access token (no API key required)

⚙️ Client Configuration (Claude, Cursor, IDEs)

Add BuiltWith MCP to your MCP-compatible client configuration.

Example```json

{
"mcpServers": {
"builtwith": {
"url": "https://api.builtwith.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_BUILTWITH_API_KEY"
}
}
}
}


### Configuration locations

* **Claude Desktop**

  * macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
  * Windows: `%APPDATA%\Claude\claude_desktop_config.json`
* **Cursor / Claude Dev (VS Code)**

  * macOS: `~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json`
  * Windows: `%APPDATA%\Code\User\globalStorage\saoudrizwan.claude-dev\settings\cline_mcp_settings.json`

---

## 🛠️ Self-Hosting (Optional)

You can also run the BuiltWith MCP server locally or inside your own infrastructure.

### What changed (February 14, 2026)

The local server now supports both standard MCP transports:

* `stdio` (default) for local MCP clients like Claude Desktop/Cursor
* `http` for remote/connector style MCP usage on `/mcp`

### Installation```bash
git clone https://github.com/builtwith/builtwith-mcp.git
cd builtwith-mcp
npm install

Local (stdio) MCP configuration```json

{
"mcpServers": {
"builtwith": {
"command": "node",
"args": ["[PATH-TO]/bw-mcp-v1.js"],
"env": {
"BUILTWITH_API_KEY": "YOUR_BUILTWITH_API_KEY"
}
}
}
}


> Note: The hosted endpoint is recommended for most users. Self-hosting is useful if you need custom routing, rate-limiting, or private network access.

### Local HTTP MCP endpoint

Run in HTTP mode:```bash
MCP_TRANSPORT=http PORT=8787 node bw-mcp-v1.js

MCP endpoint:```text
http://127.0.0.1:8787/mcp


Optional headers/environment:

* `Authorization: Bearer YOUR_BUILTWITH_API_KEY` (per-request API key for HTTP mode)
* `BUILTWITH_API_KEY` (used by stdio mode, and as fallback when no HTTP bearer token is provided)
* `MCP_ALLOWED_ORIGINS` (comma-separated CORS/origin allowlist for HTTP mode)

Health check:```text
http://127.0.0.1:8787/health

🔐 Agent Device-Code Authorization

Agents can obtain a temporary bw- prefixed API token without the user pasting their key — the user approves access in their browser.

Flow:

  1. Call agent-auth-start → receive device_code and verification_uri
  2. Direct the user to open verification_uri in their browser
  3. Poll agent-auth-token every 5 seconds with the device_code
  4. On approval, receive an access_token (bw-...) valid for the chosen duration (1 hour / 1 day / 30 days)
  5. Use the token as KEY=bw-... on any BuiltWith API endpoint

No API key is required to call agent-auth-start or agent-auth-token.


🚀 Usage Examples

Once configured, try asking your AI assistant:

  • “What technologies is example.com using?”
  • “What CMS does nytimes.com run on?”
  • “Does amazon.com use Google Analytics?”
  • “What JavaScript frameworks are used by spotify.com?”
  • “What hosting provider does netflix.com use?”
  • “Compare the technology stacks of facebook.com and twitter.com”

🧠 How It Works

  1. 🗣️ User asks a technology question in an AI assistant
  2. 🔌 The assistant calls the BuiltWith MCP server
  3. 🔍 MCP translates intent into BuiltWith API calls
  4. 📊 BuiltWith returns structured technology data
  5. 💬 The AI assistant presents human-friendly insights

📖 BuiltWith API Documentation

  • https://api.builtwith.com/
  • https://api.builtwith.com/domain-api

📄 License

MIT License — see the LICENSE file for details.


Built for AI-native workflows by BuiltWith

Just say which.

常见问题

6 问
答案由本站依据条目字段整理,不引用上游原文
Builtwith MCP 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Builtwith MCP 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Builtwith MCP 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Builtwith MCP 需要 API Key 吗?

资料标注需要Token认证,使用前准备好对应凭据,并按最小权限配置。

Builtwith MCP 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Builtwith MCP 能提供哪些能力?

资料显示约 22 个工具;能力标签包括 数据分析、JavaScript、Claude、自托管。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。