🔍 BuiltWith MCP Server 🚀
🌟 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
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/list"
}
🧩 Supported Tools
The hosted MCP exposes the following tools:
domain-lookup– Live technology detection for a domaindomain-api– Full domain metadatarelationships-api– Related websitesfree-api– Category and group countscompany-to-url– Company → domain discoverytags-api– IP / attribute based discoveryrecommendations-api– Technology recommendationsredirects-api– Live and historical redirectskeywords-api– Keyword intelligencetrends-api– Technology trend dataproduct-api– Ecommerce product searchtrust-api– Trust scoringfinancial-api– Financial datasocial-api– Social profile associationsvector-search– Semantic similarity search across technologies and categoriespayment-balance– Check your API credit balancepayment-config– Retrieve your payment configurationpayment-purchase– Purchase API credits using your saved Stripe payment method
⚙️ Client Configuration (Claude, Cursor, IDEs)
Add BuiltWith MCP to your MCP-compatible client configuration.
Example
{
"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
- macOS:
-
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
- macOS:
🛠️ 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/Cursorhttpfor remote/connector style MCP usage on/mcp
Installation
git clone https://github.com/builtwith/builtwith-mcp.git
cd builtwith-mcp
npm install
Local (stdio) MCP configuration
{
"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:
MCP_TRANSPORT=http PORT=8787 node bw-mcp-v1.js
MCP endpoint:
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:
http://127.0.0.1:8787/health
🚀 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
- 🗣️ User asks a technology question in an AI assistant
- 🔌 The assistant calls the BuiltWith MCP server
- 🔍 MCP translates intent into BuiltWith API calls
- 📊 BuiltWith returns structured technology data
- 💬 The AI assistant presents human-friendly insights
📖 BuiltWith API Documentation
📄 License
MIT License — see the LICENSE file for details.
Built for AI-native workflows by BuiltWith
Just say which.
Recommend MCP Servers 💡
mcp-server-proj
An MCP server for cartographic projections and coordinate transformations, supporting various coordinate system formats like EPSG codes, WKT, and Proj strings.
@Panth1823/formula1-mcp
Provides real-time and historical Formula 1 racing data via the Model Context Protocol
mem0-mcp
This demonstrates a structured approach for using an MCP server with mem0 to manage coding preferences efficiently. The server can be used with Cursor and provides essential tools for storing, retrieving, and searching coding preferences.
jen6/ticktick-mcp
Enhance TickTick workflow with MCP server for better task filtering and management.
duckdb-mcp-server
A Model Context Protocol (MCP) server that connects AI assistants to DuckDB for powerful data analysis using SQL, supporting various data sources including local files and S3.
lspace-server
Lspace is an open-source MCP server and standalone application that captures insights from AI sessions, making them available across tools for persistent, searchable knowledge.