Hubspot Auditor MCP Server

HubSpot Auditor

Read-only audit of a HubSpot portal. You get a scored report of what works, what is broken, and what is missing, plus a 30/60/90-day fix plan.

The server speaks MCP over stdio. A CLI runs the same audit. It never sends POST, PUT, PATCH, or DELETE to HubSpot.

What's new in v1.4.3: site checks block more non-public addresses. Please update. See CHANGELOG.md.

What's new in v1.4.2: registry metadata for the official MCP Registry and Smithery. See CHANGELOG.md.

What's new in v1.4.1: the npm package record uses the current account email. See CHANGELOG.md.

What's new in v1.4.0: the CLI and MCP server ship as compiled JavaScript. Install with npx. See CHANGELOG.md.

Quick start

You need Node.js 22 or newer.

npx -y hubspot-auditor --demo --out reports

Open reports/example-report.md.

Who is this for?

RevOps lead cleaning a portal before a process change. You need one pass over duplicates, pipelines, and forms.

• "Audit this portal in demo mode and show the broken checks."
• "Which required contact properties are thin?"
• "Which deal stages have a weak probability?"

You get findings with severity, evidence, and a recommended fix.

Administrator checking consent and sending. You need GDPR fields, spam controls, and sender authentication called out first.

• "Run the demo audit and list the critical findings."
• "What does the email auditor check?"
• "Show the 30-day plan."

You get critical and high items at the top of the plan.

Consultant handing a client a checklist. You need a report you can regenerate after they change a YAML threshold.

• "List every check and its severity."
• "Run the fictional Harbour Glass audit."
• "Write the Markdown and JSON reports."

You get examples/example-report.md and examples/example-report.json from the sample portal. No customer data is in that example.

Agent user who already has HubSpot connected. You want a second server that only scores the portal.

• "Run a read-only audit. Do not change the portal."
• "Use demo true if no token is set."

You get the same report. The token stays in the environment. It is not a tool argument.

What it checks

Rules live in versioned YAML under rules/. Each file has version: 1 and a list of checks. Turn a check off with enabled: false. Thresholds sit under params.

A check returns working, broken, or missing. Evidence is counts and property names. The report does not print contact records.

The score is the percentage of checks that are working. The 30-day plan is critical and high broken items. The 60-day plan is medium broken items plus critical and high missing items. The 90-day plan is what remains.

Live mode reads HubSpot with GET requests and a private app token. If a call is forbidden or the payload has no field for that check, the finding is missing. A failed ticket-pipeline read does not hide the deal pipeline. Fill rates count only contact properties that were requested. Demo mode loads demo/portal.json, a fictional company called Harbour Glass Co.

Logo, favicon, heading, and colour checks run on the fetched landing page. Add params.markers in rules/brand.yaml only when a phrase must appear verbatim. The buyer-stage patterns live in rules/journey.yaml. Pass --site to judge a specific public page. If you omit it, tracking uses the portal's primary site domain. Landing page checks use the CMS page URL.

MCP tools

Example workflow

You: "Run the Harbour Glass demo and tell me the score."

The server calls run_audit with demo: true.

You get a score of 30, with 14 working, 21 broken, and 11 missing. The first 30-day items are sender authentication, GDPR consent, and the missing tracking script.

Setup

You need Node.js 22 or newer.

npm install -g hubspot-auditor
hubspot-auditor --demo --out reports

Or, from a clone:

git clone https://github.com/M-Pineapple/hubspot-auditor.git
cd hubspot-auditor
npm install
npm run build
npm test
npm run audit:demo

npm run audit:demo writes examples/example-report.md, examples/example-report.json, and examples/example-report.pdf.

For a live portal, create a HubSpot private app and copy a token that has read scopes only. Do not grant write scopes. Put the token in the environment. Do not pass it as a tool argument.

export HUBSPOT_ACCESS_TOKEN="paste-a-read-only-private-app-token"
hubspot-auditor --site https://example.com --summary

--site is the public page the tracking checks fetch. --summary prints counts and check ids only.

No write scope is required. A missing read scope becomes a missing finding for that area. HTTP 429 and 5xx are reported as throttling or an outage, not as a missing scope.

The audit does not call webhook subscription edits or a connected-app list. Those HubSpot URLs do not return that data for a private app.

If the system resolver cannot find api.hubapi.com, API reads fall back to DNS over HTTPS at 1.1.1.1 and still check the original host name on the certificate. Sender TXT lookups use the system resolver first. Set HUBSPOT_AUDITOR_DOH=0 to turn the fallback off. The fallback is on unless you set that variable.

publicSiteUrl must be https. Hosts that resolve to loopback, private, link-local, or CGNAT addresses are refused, and each redirect is checked again.

MCP config

Paste this into Claude Desktop, Cursor, or Claude Code. Replace the token. For a demo-only server, you can omit the env block and call run_audit with demo: true.

{
  "mcpServers": {
    "hubspot-auditor": {
      "command": "npx",
      "args": ["-y", "hubspot-auditor"],
      "env": {
        "HUBSPOT_ACCESS_TOKEN": "paste-a-read-only-private-app-token"
      }
    }
  }
}

The same file lives in config/claude-desktop.json, config/cursor-mcp.json, and config/claude-code.json.

From a git clone, run npm run build and point the command at node with args set to ["/path/to/hubspot-auditor/dist/main.js"].

Start the server on its own with:

npm start

How this differs from the official HubSpot MCP

Use the official server when you want an agent to work in the CRM. Use this server when you want a read-only audit.

Example report

The full fictional report is examples/example-report.md. The JSON form is examples/example-report.json. The PDF is examples/example-report.pdf.

Harbour Glass Co scores 30. Fourteen checks are working, 21 are broken, and 11 are missing.

# HubSpot audit: Harbour Glass Co

This report uses a fictional sample portal. It is not a customer account.

Score: **30** (share of checks that are working).

| Status | Count |
| --- | ---: |
| Working | 14 |
| Broken | 21 |
| Missing | 11 |

The broken list starts with sender authentication, GDPR consent on forms, and the tracking code. The 30-day plan takes the critical and high broken items. The 60-day and 90-day plans follow in the same file.

Extend a check

See CONTRIBUTING.md.

More MCP servers by M-Pineapple

• Claude-Project-Coordinator
• CryptoAnalysisMCP
• warp-command-runner
• msty-admin-mcp
• member-berries-apple-mcp
• seashell
• TextEdit-MCP

💖 Support This Project

If HubSpot Auditor has helped you audit a portal, consider supporting its development:

Licence

MIT. Copyright (c) 2026 M-Pineapple.