HubSpot MCP server and Dome
Let agents update your CRM while keeping them off your website and your schema. Connect HubSpot's MCP server to Dome through a HubSpot MCP connector. Each rep consents once, and calls made for them run with their HubSpot permissions. Rules decide which HubSpot tools each agent can call.
Dome provides a tool gatewayand authorization for HubSpot.
Records yes, schema no
manage_crm_objects stays open for record updates. New properties and pipelines are refused.
Nothing goes live
Landing pages, website pages, and blog posts are refused at the Gateway, so an agent can't publish to your site.
Their HubSpot permissions
With per-user OAuth, each rep consents once. An agent acting for them reaches only the records they can.
HubSpot behind the Gatewayin three steps.
Create an MCP connector in HubSpot, add the server to Dome with its client credentials, and apply the rule. Agents reach HubSpot through the Gateway's single MCP endpoint.
Add the HubSpot MCP server
In HubSpot, create an MCP connector with https://api.domesystems.ai/oauth/callback as its redirect URL. Dome runs the OAuth flow with PKCE and holds each rep's tokens.
shelldome tools add --name hubspot \ --url https://mcp.hubspot.com \ --auth-method oauth --credential-type per-user \ --oauth-authorize-url https://mcp.hubspot.com/oauth/authorize/user \ --oauth-token-url https://mcp.hubspot.com/oauth/v3/token \ --oauth-token-endpoint-auth client_secret_post \ --oauth-client-id "$HUBSPOT_CLIENT_ID" \ --oauth-client-secret "$HUBSPOT_CLIENT_SECRET" \ --gateway revenue-gatewaySync the catalog
Run it once your own HubSpot consent is attached. HubSpot's tools vary by subscription and permissions, so the sync lists what your account has.
shelldome tools catalog sync hubspotApply the rule
Scope it to one agent while you try it, and simulate before you deploy.
shelldome rules apply hubspot-crm-only.cedar \ --agent deal-updater --name hubspot-crm-only
Update records,leave the rest.
The permit opens HubSpot to the agent. The forbid refuses the tools that change your schema or publish content.
cedar
permit (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when { resource.connection_name == "hubspot" };
forbid (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when { resource.connection_name == "hubspot" && ["manage_custom_properties", "manage_custom_pipelines", "manage_landing_page", "manage_website_page", "manage_blog_post"].contains(resource.tool_name)};Three agentson HubSpot.
These come from our template library, and each one reads broadly and writes narrowly.
deal-updater
Keep deals current
Reads call notes and email threads, then updates deal stage and next steps on the record.
account-researcher
Brief reps before a call
Pulls the company, its contacts, and open deals into a one-page brief without changing anything in HubSpot.
campaign-reporter
Report on campaigns
Reads campaign and marketing email results and writes the weekly summary, while pages stay with marketing.
Bringing it alltogether.
Connecting HubSpot to registered agents, models, and identity in Dome completes a governed agent application.
Acting for
Agent
Control point
GatewayEvery call decided and audited
RulesGuardsQuotas
Tools
HubSpotMCP server
Models
Common questionsabout HubSpot.
More of whatDome works with.
Model
Claude Fable
Fable 5.1 from Anthropic and Amazon Bedrock in one failover pool, open to one group and capped by quota.
Provider
Anthropic
The Claude API behind the Model Broker: the key held in Dome, every call authorized, metered and audited.
Identity
Okta
Okta tokens verified on every agent call, so rules and audit name the person each agent acted for.
Runtime
LangGraph
LangGraph agents with their model calls on the Model Broker and their MCP tools on the Tool Gateway.
Client
Claude Code
Claude Code on a Dome Gateway with per-developer sign-in, rules on every tool call, and audit by name.
Agent service
TinyFish
TinyFish's web agents behind the Tool Gateway, with rules that decide each run on the site it targets.
Talk with ourFDE team.
Or start free, and register your first agent in minutes. Connect it through a gateway, give it rules, and see every call it makes in one audit trail.
Talk with our FDE team
Our engineers design, build and run governed agents for the part of your business you want to change. You see what they deliver.
MCP servers for AI agents: per-argument rules on every call
Put any remote MCP server behind the Tool Gateway. Agents reach it through one governed endpoint, and rules decide each call on its arguments.