Get the FREE Ultimate OpenClaw Setup Guide →

builtwith

MCP server from Cyreslab-AI/builtwith-mcp-server

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio cyreslab-ai-builtwith-mcp-server node /absolute/path/to/builtwith-mcp-server/build/index.js \
  --env BUILTWITH_API_KEY="your-api-key-here"

How to use

BuiltWith MCP Server provides a focused interface for querying website technology stacks via the BuiltWith API. Once running, you can ask an MCP-compatible assistant questions like which technologies a domain uses, see technology categories (Analytics, CMS, Frameworks, etc.), and retrieve detailed information such as descriptions and detection dates. The server exposes a domain_lookup tool that returns the technology footprint for a given domain. To use it, ensure the server is running with your BuiltWith API key (BUILTWITH_API_KEY) and configure your MCP client to target the builtwith MCP server via the node command and path to the built index. Typical usage involves sending a domain query (e.g., example.com) and optionally requesting detailed information for a richer result set.

How to install

Prerequisites:

  • Node.js 18 or higher
  • npm (comes with Node.js)
  • BuiltWith API key
  1. Clone the repository git clone https://github.com/Cyreslab-AI/builtwith-mcp-server.git cd builtwith-mcp-server

  2. Install dependencies npm install

  3. Build the project npm run build

  4. Run the server locally (pass your BuiltWith API key as an environment variable) BUILTWITH_API_KEY=your-api-key-here node build/index.js

  5. Configure MCP client settings (example in MCP settings file shown in README) with the command pointing to the built index and the environment variable for BUILTWITH_API_KEY.

Note: If you run into issues with the MCP SDK dependency, follow the troubleshooting steps in the README to switch to a GitHub-based dependency or install the SDK locally and point the server to it.

Additional notes

Tips and considerations:

  • Ensure your BUILTWITH_API_KEY is kept secure and not committed to version control.
  • If the MCP SDK dependency is unavailable in npm, the project is configured to fall back to a GitHub-based dependency; follow the README’s guidance to reference the SDK locally.
  • In MCP client configurations, include env settings only for keys that the server needs (avoid exposing unnecessary credentials).
  • When testing, use concrete domains (e.g., example.com) to validate domain_lookup responses and ensure the API key has proper access to the BuiltWith API.
  • If you update the server or SDK, re-run npm install and npm run build to ensure changes are reflected in the built index file.

Related MCP Servers

Sponsor this space

Reach thousands of developers