Connect HubSpot to Cline CLI
Give Cline CLI governed access to HubSpot’s 30 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add HubSpot to Cline CLI in four steps
Admins approve the server once. Everyone in Cline CLI then gets it through the same governed connection.
- 1
Approve HubSpot in Runlayer
Add HubSpot from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Cline CLI to Runlayer
Users add the Runlayer Plugin to Cline CLI by following Runlayer’s setup guide. Cline CLI reaches HubSpot’s 30 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Cline CLI setup guide - 3
Sign in to HubSpot
Sign in the way HubSpot requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use HubSpot from Cline CLI
HubSpot’s approved tools appear in Cline CLI. Every call is checked against policy and recorded.
Tools
30 HubSpot tools in Cline CLI
Runlayer policy decides which of these Cline CLI users can call. 16 read data only and 5 can change or delete data.
Discover HubSpot schema
Searches HubSpot schema to discover available data types or look up known types directly.
Get AEO metrics
Portal-level AEO analytics: brand visibility, mentions, citations, competitor share-of-voice, and per-assistant breakdowns for a date window.
Get campaign attribution reports
REQUIRED FIRST STEP: before your first call, invoke tool_guidance for "get_campaign_attribution_reports" and follow it.
Get content analytics report
Run a content analytics report across landing pages, website pages, and blog posts in the portal.
Get conversation channel metadata
List inboxes, channels, and channel instances in this portal.
Get CRM objects
Fetches multiple CRM objects of the same object type in a single request.
Get marketing email analytics
Provides analytics data for marketing emails based on sends in the given date range.
Get organization details
Get organization-wide teams, job titles (roles), seats, and account info (timezone, currency, account type, portal name).
Control
What Runlayer can see and stop in Cline CLI
Some controls apply to every client at the gateway. Others depend on what Cline CLI exposes to Runlayer.
Gateway policy (available)
Every HubSpot call from Cline CLI passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Cline CLI as the client, the tool, and the policy and scanner decisions.
Client hooks (available)
Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.
Stop a call before it runs (available)
Runlayer can deny a tool call before Cline CLI runs it.
Block output after it runs (not available)
Cline CLI ignores Runlayer after a tool runs, so Runlayer cannot block its output. The gateway still applies policy to the call.
Redact output in place (not available)
Runlayer cannot mask tool output in Cline CLI. The gateway still applies policy to the call.
In Cline CLI
- If Runlayer’s hook times out or crashes, Cline CLI lets the tool call through.
- This covers the Cline CLI, not the Cline extension for VS Code.
Frequently asked questions
Connect more
