Boolsai Directory

What the Boolsai Directory MCP server does

The Boolsai Directory MCP server provides structured queries over a pre-indexed collection of tens of thousands of ecommerce sites. Its records organize sites by technology vendor, account ID, country, founder, city, market, and stack archetype. This makes it suitable for competitive research, agency prospecting, ecommerce due diligence, and exploratory commerce-data work.

The directory is separate from Boolsai Scan. Directory queries work against indexed data, while Boolsai Scan examines a public site live. A workflow can therefore use the directory to find candidate sites and the scanner to inspect a specific site in more detail, although this server itself does not perform the live scan.

How it works

The Boolsai Directory MCP server uses the Streamable HTTP MCP transport. Send MCP requests to https://directory.boolsai.ai/mcp; an MCP client exposes the available operations to an agent. The service is publicly accessible and does not require an API key or other authentication according to the repository documentation.

Queries can start with a general directory summary, a vendor or identifier lookup, or a geographic and founder-based search. Site-level tools return dossiers, comparisons, or similar-site results. Stack archetype queries provide another way to group sites by their observed technology composition.

Setup and configuration

Add the server as a remote MCP endpoint in a compatible client:

{
  "mcpServers": {
    "boolsai-directory": {
      "url": "https://directory.boolsai.ai/mcp"
    }
  }
}

The repository specifically documents setup for Claude Desktop, Claude Code, and Cursor. Restart the client after adding the endpoint so its tools become available. Claude.ai users can also add the URL through the custom connector settings described in the project documentation. No environment variables or local server process are specified for this remote deployment.

Tools and capabilities

The server exposes these ten tools:

• summary — inspect a directory-level summary.
• site_dossier — retrieve a dossier for a site.
• sites_using_vendor — find sites associated with a vendor.
• lookup_id — search by an account or other indexed identifier.
• brands_in_city — find brands in a city.
• brands_in_market — find brands in a market.
• stack_archetype — query sites by stack archetype.
• compare_sites — compare selected sites.
• similar_sites — find sites resembling a supplied site or set of sites.
• brands_by_founder — search brands by founder.

These operations support questions such as which stores use a particular vendor, which brands operate in a market, and how selected ecommerce sites compare.

Limitations and notes

The directory is described as pre-indexed, so it should not be treated as a substitute for a current live scan of an arbitrary site. Use Boolsai Scan for that separate capability. The supplied material does not define tool parameter schemas, result-field guarantees, freshness intervals, or pagination behavior. The server is one component of a four-server Boolsai suite; the other endpoints cover live scanning, historical pattern search, and signals, but those tools are not part of this directory endpoint.