Updated March 2026

Install Wappalyzer

Pick your client, copy the command, done.

Local setup required. This server has to be cloned and prepared on your machine before you register it in Claude Code.

Run this once to clone and prepare the server before adding it to Claude Code.

Run in terminal

npm install

After the local setup is done, run this command to point Claude Code at the built server.

Run in terminal

claude mcp add -e "WAPPALYZER_API_KEY=${WAPPALYZER_API_KEY}" wappalyzer -- node "<FULL_PATH_TO_MCP>/dist/index.js"

Replace <FULL_PATH_TO_MCP>/dist/index.js with the actual folder you prepared in step 1.

Required:WAPPALYZER_API_KEY+ 3 optional

Environment Variables

Set these before running Wappalyzer.

VariableDescriptionRequired

WAPPALYZER_API_KEYYour Wappalyzer API keyYes

WAPPALYZER_API_BASE_URLBase URL for the Wappalyzer APINo

WAPPALYZER_METADATA_BASE_URLBase URL for metadata resourcesNo

WAPPALYZER_HTTP_TIMEOUT_MSHTTP request timeout in millisecondsNo

Once configured, Wappalyzer gives your AI agent access to:

lookup_siteIdentify web technologies and metadata for a specific URL.

urllivesetsdenoisemax_age

lookup_subdomainsRetrieve a list of subdomains for a given domain.

domainlimitafter

get_credit_balanceCheck the remaining API credit balance.

After setup, try these prompts with your AI agent:

→What technologies are used on https://www.example.com?

→Find all subdomains for example.com.

→Check my current Wappalyzer API credit balance.

→Identify the company and contact information for the website https://www.wappalyzer.com/.

Prerequisites & system requirements

An MCP-compatible client (Claude Code, Cursor, Windsurf, Claude Desktop, or Codex)
Node.js 18+ with npm/npx installed
WAPPALYZER_API_KEY — Your Wappalyzer API key

Save the docs, env vars, and workflow around Wappalyzer in Conare so Claude Code, Codex, and Cursor remember it next time.