Bizintel MCP Server

Local business intel for AI agents: audits, lead scoring, tech stack, prospecting. The bizintel mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 8 defined tools rather than through you.

What it actually does

BizIntel is a paid MCP server that gives AI agents instant access to the kind of local-business intelligence sales teams used to pay analysts to gather. One call to audit_website returns a 0-100 score across SSL, mobile-readiness, page speed, contact form presence, and online booking — plus a tech-stack fingerprint (CMS, booking platform, email provider, analytics). Agents pointed at "find dentists in Austin with no booking system" get a ranked, contactable list in seconds, not hours.

Its toolset

Everything the assistant can do here goes through one of these:

• audit_website — url
• search_businesses — niche, city, state, limit
• get_business_details — business_name, city
• bulk_audit — urls (≤20)
• score_lead — business_name, city, niche
• find_no_website — niche, city, state, limit
• find_no_booking — niche, city, state, limit
• get_tech_stack — url

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration

You will need one environment variable: YELP_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Bizintel's toolset — audit_website, search_businesses, get_business_details and 5 more — is a fair guide to whether it matches your workflow. It is maintained by bch1212; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the bizintel mcp server does with a few real requests.