BuiltWith MCP Server

What does “BuiltWith” MCP Server do?

The BuiltWith MCP (Model Context Protocol) Server is a specialized tool designed to connect AI assistants with the BuiltWith technology detection API. Its primary function is to enable AI agents to analyze and identify the technology stack behind any website. By bridging the gap between natural language queries and the BuiltWith API, this MCP server allows developers and AI-powered workflows to obtain detailed insights about frameworks, analytics tools, hosting services, content management systems, and more used on any given domain. This capability enhances development workflows by enabling quick technology audits, competitive analysis, and data-driven decisions through seamless API integration.

List of Prompts

No explicit reusable prompt templates are mentioned in the repository.

List of Resources

No explicit MCP resources are documented in the repository.

List of Tools

• Domain Lookup: Provides comprehensive technology profiles for any website by querying the BuiltWith API. This allows users to discover the frameworks, services, analytics, and hosting providers used by a domain.

Use Cases of this MCP Server

• Technology Stack Discovery: Instantly identify the frameworks, analytics tools, hosting platforms, and other technologies used by any website, helping developers in planning integrations or migrations.
• Competitive Analysis: Compare the technology stacks of multiple competitors to inform technical strategy or business decisions.
• CMS and Platform Identification: Find out which content management system (CMS) or e-commerce platform a site is running on, aiding in targeted outreach or compatibility checks.
• Third-party Service Auditing: Determine if a website uses specific analytics, marketing, or security services to assess partnerships or compliance.
• Developer Tooling Integration: Seamlessly integrate technology lookup capabilities into developer environments, making it easy to research sites during the development lifecycle.

How to set it up

Windsurf

1. Ensure Node.js is installed on your system.
2. Clone the repository and install dependencies:

   git clone https://github.com/builtwith/mcp.git
   cd mcp
   npm install
   

3. Obtain your BuiltWith API key from BuiltWith API.
4. Add the following configuration snippet to your Windsurf MCP configuration file:

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

5. Save the configuration and restart Windsurf. Verify the server is running.

Claude

1. Install Node.js if not already installed.
2. Clone the BuiltWith MCP repository and install dependencies.
3. Copy your API key for BuiltWith.
4. Edit claude_desktop_config.json located at:
   • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
   • Windows: %APPDATA%\Claude\claude_desktop_config.json
5. Add the MCP server configuration:

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

6. Save and restart Claude. Confirm integration.

Cursor

1. Install Node.js.
2. Clone the repository and install dependencies.
3. Add your API key.
4. Edit the MCP settings file at:
   • 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
5. Insert the configuration:

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

6. Save and restart Cursor for changes to take effect.

Cline

1. Make sure Node.js is installed.
2. Clone and set up the MCP server as above.
3. Edit the MCP configuration file (refer to Cursor’s config path above).
4. Add the server configuration as described previously.
5. Save, restart Cline, and verify the MCP server is accessible.

Securing API Keys:
Always store sensitive API keys using environment variables. For example:

{
    "env": {
        "BUILTWITH_API_KEY": "[YOUR-API-KEY]"
    },
    "inputs": {}
}

How to use this MCP inside flows

Using MCP in FlowHunt

To integrate MCP servers into your FlowHunt workflow, start by adding the MCP component to your flow and connecting it to your AI agent:

Click on the MCP component to open the configuration panel. In the system MCP configuration section, insert your MCP server details using this JSON format:

{
  "builtwith": {
    "transport": "streamable_http",
    "url": "https://yourmcpserver.example/pathtothemcp/url"
  }
}

Once configured, the AI agent is now able to use this MCP as a tool with access to all its functions and capabilities. Remember to change “builtwith” to whatever the actual name of your MCP server is and replace the URL with your own MCP server URL.

Overview

Based on the available documentation, the BuiltWith MCP Server offers clear setup instructions and a well-defined use case but lacks advanced MCP features such as resources, prompt templates, roots, or sampling. It is a simple, purpose-built MCP server.

MCP Score

Overall, this MCP scores around 4/10: it is functional and well-documented for its single use case, but lacks depth in MCP-specific features such as resources, prompt templates, and sampling support, and has minimal community engagement so far.