ClawHub

Maverick Hubspot Mcp

Search, read, and update HubSpot CRM contacts, companies, deals, tickets, associations, owners, and pipelines via HubSpot's hosted MCP server. Thin pass-through to HubSpot's official MCP; the live tool catalog is whatever that server advertises. Use when the user asks about HubSpot CRM records, pipeline state, owners, or customer activity.

Audits

Pass
ClawScanPass

Agentic behavior and permission review.

Static analysisReview

Pattern checks against bundled files.

VirusTotalPass

Multi-engine malware detections and file reputation.

Install

openclaw skills install maverick-hubspot-mcp

HubSpot

How to use this skill

This skill is a thin pass-through to HubSpot's hosted MCP server at https://mcp.hubspot.com. The live server is the source of truth for what tools exist, what they're called, what arguments they take, and any per-server instructions the server publishes.

Always invoke through bash {baseDir}/scripts/invoke.sh — never call mcporter directly. The wrapper seeds the OAuth vault from the env-supplied tokens when needed, then calls mcporter.

Step 1 - Discover the live tool catalog and any server-published usage instructions. Always run this first; do not rely on tool names from memory:

bash {baseDir}/scripts/invoke.sh list maverick-hubspot-mcp --schema

The output includes the server's Instructions: field, if published, and a JSON Schema for every tool's parameters. Treat this as the authoritative reference for the rest of the session.

Step 2 - Call any tool from the catalog using the form maverick-hubspot-mcp.<tool>:

bash {baseDir}/scripts/invoke.sh call maverick-hubspot-mcp.<tool> <arg>=<value> ...

Add --output json for structured output and transport-error envelopes:

bash {baseDir}/scripts/invoke.sh call --output json maverick-hubspot-mcp.<tool> ...

Safety

Write-capable tools can create or update HubSpot CRM records, activities, associations, products, line items, and related pipeline data visible to the connected account. Confirm clear user intent before making changes, read the current record state before editing, and use HubSpot property names exactly as the live tool schema requires.

Authentication

HubSpot's MCP server uses OAuth through a HubSpot MCP auth app. The provider documentation requires an app client ID, client secret, and matching redirect URL, and states that PKCE is required for HubSpot MCP OAuth.

Credentials are available to the agent runtime through required env vars. The wrapper seeds mcporter's vault as needed before each call. mcporter handles authentication automatically: it reads tokens and client information from the vault, sends tokens with each request, and refreshes them on expiry.

The only failure mcporter cannot recover from on its own is grant revocation. It manifests as calls persistently failing with auth errors that do not clear on retry; ask the user to re-authorize the integration.

References