> ## Documentation Index > Fetch the complete documentation index at: https://docs.formal.ai/llms.txt > Use this file to discover all available pages before exploring further. # HubSpot > Search and update CRM contacts, companies, deals, tickets, and campaigns. Data Publisher: HubSpot Route HubSpot MCP traffic through Formal to control and log what AI agents do in HubSpot: * **Block** tools you don't want agents to call, such as `manage_crm_objects`. * **Mask** sensitive data in tool results, such as emails and phone numbers in `search_crm_objects` responses. * **Keep credentials at the Connector**, so users and agents never see HubSpot tokens. * **Log** every tool call with the user, the MCP client and its parameters. Cloud agents Laptop / VM Endpoint [https://mcp.hubspot.com/anthropic](https://mcp.hubspot.com/anthropic) Connector ![](https://docs.formal.ai/static/brands/hubspot.png) ## 0. Prepare your Connector The Connector needs an MCP listener and a hostname with wildcard DNS and TLS. Set them up once by following [Deploy the Connector](https://docs.formal.ai/docs/guides/core-concepts/connectors/mcp-gateway.md#deploy-the-connector). Every MCP server reuses them. ## 1. Add HubSpot MCP server to your Resources > [tab] UI > > 1. Open the [Admin Catalog](https://app.formal.ai/catalog) and click **Add MCP**. > 2. Select the **HubSpot** template. > 3. Enter a DNS-label **Name**, such as `hubspot`. > 4. Choose the **Space** containing your Connector, such as `default`. > 5. Configure upstream authentication as described below, then save. > > If no Connector is in the selected Space, the **Configuration** tab shows **MCP clients can't connect directly yet**. > The reason reads: `No Connector is in this server's Space.` > > Adding HubSpot to the Admin Catalog > [tab] Terraform > > Set `space_id` to the ID of the Space containing your Connector. > > ```hcl theme={"languages":{"custom":["/languages/cel.json","/languages/rego.json"]}} > resource "formal_resource" "hubspot" { > name = "hubspot" > technology = "mcp" > hostname = "mcp.hubspot.com" > space_id = "" > native_users_v3_enabled = true > port = 443 > tags = { > "mcp-endpoint" = "/anthropic" > } > } > > resource "formal_resource_oauth_settings" "hubspot" { > resource_id = formal_resource.hubspot.id > } > ``` > [tab] Pulumi > > Set `spaceId` to the ID of the Space containing your Connector. > > ```ts theme={"languages":{"custom":["/languages/cel.json","/languages/rego.json"]}} > import * as formal from "@formalco/pulumi"; > > const resource = new formal.Resource("mcp", { > name: "hubspot", > technology: "mcp", > hostname: "mcp.hubspot.com", > port: 443, > spaceId: "", > tags: { "mcp-endpoint": "/anthropic" }, > nativeUsersV3Enabled: true, > }); > > new formal.ResourceOauthSettings("mcpOAuth", { > resourceId: resource.id, > }); > ``` > [tab] API > > Create a Resource with the MCP endpoint and its Space ID. > > ```bash theme={"languages":{"custom":["/languages/cel.json","/languages/rego.json"]}} > export FORMAL_API_KEY="" > RESOURCE_RESPONSE=$(curl --fail --silent --show-error \ > --request POST \ > https://api.formal.ai/core.v1.ResourceService/CreateResource \ > --header "x-api-key: ${FORMAL_API_KEY}" \ > --header "Content-Type: application/json" \ > --data-binary @- < { > "name": "hubspot", > "hostname": "mcp.hubspot.com", > "port": 443, > "technology": "mcp", > "spaceId": "", > "tags": [ > { > "key": "mcp-endpoint", > "value": "/anthropic" > } > ] > } > JSON > ) > RESOURCE_ID=$(printf '%s' "${RESOURCE_RESPONSE}" | jq -r '.resource.id') > curl --fail --silent --show-error \ > --request POST \ > https://api.formal.ai/core.v1.ResourceService/CreateResourceOAuthSettings \ > --header "x-api-key: ${FORMAL_API_KEY}" \ > --header "Content-Type: application/json" \ > --data-binary @- < { > "resourceId": "${RESOURCE_ID}" > } > JSON > ``` ## 2. Setup Authentication > [tab] Linked Accounts (Recommended) > > Each user links their own HubSpot account once in the Employee Catalog, and the Connector sends that user's token to HubSpot. > > ![Linked Accounts selected under How does Formal authenticate to this resource?](https://mintcdn.com/formal/vzPMpIcsF4BYmdx8/assets/images/mcp-servers/auth-linked-accounts.png?fit=max\&auto=format\&n=vzPMpIcsF4BYmdx8\&q=85\&s=dc448db2a373faa6e1bf49fd5ffaf7c4) > > HubSpot doesn't support Formal's App, so register your own OAuth app. > > See [HubSpot OAuth documentation](https://developers.hubspot.com/docs/apps/developer-platform/build-apps/integrate-with-the-remote-hubspot-mcp-server) and [register an app](https://app.hubspot.com/). > > **1. Create a connector** > > Open [HubSpot](https://app.hubspot.com/), go to **Development > MCP Connectors**, and click **Create MCP connector**. > > **2. Set the callback** > > Enter a **Name** and paste Formal's **Redirect URI** into **Redirect URL**. > > **3. Create the OAuth client** > > Click **Create**; HubSpot determines scopes automatically from available tools and permissions granted during installation. > > **4. Get credentials** > > Copy the **Client ID** and **Client secret** from the connector's details page. > > **5. Enter the app in Formal** > > > [tab] UI > > > > Back in the Admin Catalog, enter the **Client ID** and **Client secret**, then save. > > Users then link their accounts on the HubSpot server's page in the [Employee Catalog](https://catalog.formal.ai). > > > > ![Your OAuth App selected in the Admin Catalog, with the Redirect URI, Client ID and Client secret fields](https://mintcdn.com/formal/R-3CwVgs8IU6liji/assets/images/mcp-servers/your-oauth-app.png?fit=max\&auto=format\&n=R-3CwVgs8IU6liji\&q=85\&s=00584678f4f2696805678de060eaea0a) > > > [tab] Terraform > > > > Use these OAuth settings instead of the ones from step 1. > > > > ```hcl theme={"languages":{"custom":["/languages/cel.json","/languages/rego.json"]}} > > variable "hubspot_oauth_client_secret" { > > type = string > > sensitive = true > > } > > > > resource "formal_resource_oauth_settings" "hubspot" { > > resource_id = formal_resource.hubspot.id > > upstream_oauth_mode = "pre_registered" > > client_id = "" > > client_secret_wo = var.hubspot_oauth_client_secret > > client_secret_wo_version = 1 > > } > > ``` > > > [tab] Pulumi > > > > Use these OAuth settings instead of the ones from step 1. > > Store the secret with `pulumi config set --secret hubspotOauthClientSecret`. > > > > ```ts theme={"languages":{"custom":["/languages/cel.json","/languages/rego.json"]}} > > import * as pulumi from "@pulumi/pulumi"; > > > > const config = new pulumi.Config(); > > > > new formal.ResourceOauthSettings("mcpOAuth", { > > resourceId: resource.id, > > upstreamOauthMode: "pre_registered", > > clientId: "", > > clientSecret: config.requireSecret("hubspotOauthClientSecret"), > > }); > > ``` > > > [tab] API > > > > Use this call instead of the `CreateResourceOAuthSettings` call from step 1. > > The OAuth app is fixed at creation. > > > > ```bash theme={"languages":{"custom":["/languages/cel.json","/languages/rego.json"]}} > > curl --fail --silent --show-error \ > > --request POST \ > > https://api.formal.ai/core.v1.ResourceService/CreateResourceOAuthSettings \ > > --header "x-api-key: ${FORMAL_API_KEY}" \ > > --header "Content-Type: application/json" \ > > --data-binary @- < > { > > "resourceId": "${RESOURCE_ID}", > > "upstreamOauthMode": "pre_registered", > > "clientId": "", > > "clientSecret": "" > > } > > JSON > > ``` > [tab] Shared Credentials > > An administrator stores one HubSpot token in Formal, and the Connector sends it on every user's requests without showing it to them. > > ![Shared Credentials selected under How does Formal authenticate to this resource?](https://mintcdn.com/formal/R-3CwVgs8IU6liji/assets/images/mcp-servers/auth-shared-credentials.png?fit=max\&auto=format\&n=R-3CwVgs8IU6liji\&q=85\&s=91032e202518088292ee1cf39451b9ef) > > HubSpot's MCP endpoint doesn't accept API tokens, so use Linked Accounts. > [tab] Pass Through > > Each user sends their own HubSpot sign-in or token from their MCP client, and Formal forwards it unchanged without storing it. > > ![Pass Through selected under How does Formal authenticate to this resource?](https://mintcdn.com/formal/R-3CwVgs8IU6liji/assets/images/mcp-servers/auth-pass-through.png?fit=max\&auto=format\&n=R-3CwVgs8IU6liji\&q=85\&s=c14ae61de2dba8b567626cba03aae2cf) > > Nothing in the request identifies the Formal user. Formal attributes these requests only when they come through the [Formal Endpoint](https://docs.formal.ai/docs/guides/core-concepts/connectors/mcp-gateway.md#identity-headers). Pass-through servers have no Connector address, so cloud agents can't use them. > > For OAuth, each MCP client signs in to HubSpot itself. ## 3. Route Endpoint traffic Auth is managed at the Connector level when you use Linked Accounts or Shared Credentials, so the Endpoint needs to forward the MCP traffic to it. Laptops and VMs with the Formal Endpoint keep using `https://mcp.hubspot.com/anthropic`, and a network rule sends that traffic to the Connector. > [tab] UI > > 1. Go to [Network Rules](https://app.formal.ai/network-rules) and create a rule named `hubspot-mcp`. > 2. Paste this expression, set the rule to **Active**, then save: > > ```javascript theme={"languages":{"custom":["/languages/cel.json","/languages/rego.json"]}} > { > "condition": { > "pre_tcp": process.is_agent, > // Every MCP server added to Formal: process.is_agent && resource.technology == "mcp" > "pre_tls": process.is_agent && hostname == "mcp.hubspot.com", > "post_tls": true > }, > "outputs": { > "forward_to_connector": true > } > } > ``` > [tab] Terraform > > ```hcl theme={"languages":{"custom":["/languages/cel.json","/languages/rego.json"]}} > resource "formal_network_rule" "hubspot_mcp" { > name = "hubspot-mcp" > description = "Forward HubSpot MCP traffic from agents to the Connector" > status = "active" > > # Every MCP server added to Formal: set pre_tls to process.is_agent && resource.technology == "mcp" > cel_expression = <<-EOT > { > "condition": { > "pre_tcp": process.is_agent, > "pre_tls": process.is_agent && hostname == "mcp.hubspot.com", > "post_tls": true > }, > "outputs": { > "forward_to_connector": true > } > } > EOT > } > ``` > [tab] Pulumi > > ```ts theme={"languages":{"custom":["/languages/cel.json","/languages/rego.json"]}} > import * as formal from "@formalco/pulumi"; > > new formal.NetworkRule("hubspotMcp", { > name: "hubspot-mcp", > description: "Forward HubSpot MCP traffic from agents to the Connector", > status: "active", > // Every MCP server added to Formal: set pre_tls to process.is_agent && resource.technology == "mcp" > celExpression: ` > { > "condition": { > "pre_tcp": process.is_agent, > "pre_tls": process.is_agent && hostname == "mcp.hubspot.com", > "post_tls": true > }, > "outputs": { > "forward_to_connector": true > } > } > `, > }); > ``` > [tab] API > > ```bash theme={"languages":{"custom":["/languages/cel.json","/languages/rego.json"]}} > export FORMAL_API_KEY="" > # Every MCP server added to Formal: set pre_tls to process.is_agent && resource.technology == "mcp" > CEL_EXPRESSION=$(cat <<'CEL' > { > "condition": { > "pre_tcp": process.is_agent, > "pre_tls": process.is_agent && hostname == "mcp.hubspot.com", > "post_tls": true > }, > "outputs": { > "forward_to_connector": true > } > } > CEL > ) > jq -n --arg cel "${CEL_EXPRESSION}" '{ > name: "hubspot-mcp", > description: "Forward HubSpot MCP traffic from agents to the Connector", > status: "active", > celExpression: $cel > }' | curl --fail --silent --show-error \ > --request POST \ > https://api.formal.ai/core.v1.DesktopService/CreateDesktopRoutingRule \ > --header "x-api-key: ${FORMAL_API_KEY}" \ > --header "Content-Type: application/json" \ > --data-binary @- > ``` The rule matches [known agents](https://docs.formal.ai/docs/guides/network-rules.md#known-agent-identities) only. See [Identity headers](https://docs.formal.ai/docs/guides/core-concepts/connectors/mcp-gateway.md#identity-headers). Cloud agents such as Claude, ChatGPT and Cursor Cloud Agents don't run the Endpoint. Point them at this server's Connector address, `https://hubspot./mcp`. Find it in the [Admin Catalog](https://app.formal.ai/catalog): open HubSpot, then copy **Connector address** on the **Configuration** tab. ## 4. Create policies ### Tools The Admin Catalog lists these tools for HubSpot: | Tool | Description | | - | - | | `search_crm_objects` | Search CRM records. | | `get_crm_objects` | Retrieve CRM records by identifier. | | `manage_crm_objects` | Create or update CRM records. | | `get_properties` | List properties for a CRM object. | | `search_properties` | Search CRM property definitions. | | `search_owners` | Search HubSpot owners. | | `query_crm_data` | Run a structured query across CRM data. | | `discover_hubspot_schema` | Discover available HubSpot objects and fields. | | `get_user_details` | Retrieve authenticated user details. | | `get_organization_details` | Retrieve HubSpot account details. | | `search_conversations` | Search customer conversations. | | `get_conversation_channel_metadata` | Retrieve conversation channel metadata. | | `read_campaign_data` | Retrieve marketing campaign data. | | `get_campaign_attribution_reports` | Retrieve campaign attribution reports. | | `get_marketing_email_analytics` | Retrieve marketing email performance. | | `get_content_analytics` | Retrieve content performance analytics. | | `manage_landing_page` | Create or update a landing page. | | `render_landing_page_ui` | Render a landing page editing interface. | | `read_landing_page_ui` | Read the current landing page interface state. | | `import_claude_design_from_url` | Import a generated design from a URL. | ### Policies examples > [tab] Block a tool > > This policy blocks the tools that change data, so agents can only read HubSpot. > > ```rego theme={"languages":{"custom":["/languages/cel.json","/languages/rego.json"]}} > package formal.v2 > > import future.keywords.if > import future.keywords.in > > write_tools := { > "manage_crm_objects", > "manage_landing_page", > "import_claude_design_from_url", > } > > request := { > "action": "block", > "type": "block_with_custom_message", > "message": "Writing to HubSpot is not allowed.", > } if { > input.resource.name == "hubspot" > input.mcp.method == "tools/call" > input.mcp.tool_name in write_tools > } > ``` > [tab] Mask a tool's output > > This policy replaces email addresses in results returned by `search_crm_objects`, `get_crm_objects`, and `get_user_details`. > > ```rego theme={"languages":{"custom":["/languages/cel.json","/languages/rego.json"]}} > package formal.v2 > > import future.keywords.if > import future.keywords.in > > email_pattern := `[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Za-z]{2,}` > > response := { > "action": "rewrite", > "body": regex.replace(input.http.body, email_pattern, "[REDACTED-EMAIL]"), > "reason": "Mask emails in HubSpot results", > } if { > input.resource.name == "hubspot" > input.mcp.tool_name in {"search_crm_objects", "get_crm_objects", "get_user_details"} > regex.match(email_pattern, input.http.body) > } > ``` See [MCP resources](https://docs.formal.ai/docs/guides/policies/evaluation.md#mcp-resources) for the `input.mcp` fields and [Rewrite Action](https://docs.formal.ai/docs/guides/policies/enforcement.md#rewrite-action) for body rewrites. ## 5. Check the logs Open [Logs](https://app.formal.ai/logs) and search for `resource.name:hubspot`. Each HubSpot tool call is one `request` log with the user, the MCP client and the tool. Open a log to see its tool parameters and the policies it triggered. A blocked write shows the block policy and its message. A masked search shows the rewrite policy. HubSpot tool calls in Logs, including a masked response and a blocked write See [Logs](https://docs.formal.ai/docs/guides/observability/logs.md) for search syntax and filters. ## Troubleshooting > [accordion] The agent says Formal has no current sign-in > > The agent relays: `Formal has no current hubspot sign-in for you. Link or re-link your hubspot account in Formal…` > > **Cause:** The user never linked HubSpot, or the token expired and couldn't be refreshed. > > **Fix:** Open the server in the [Employee Catalog](https://catalog.formal.ai) and link HubSpot again. > [accordion] The agent says HubSpot rejected your credentials > > The agent relays: `hubspot rejected your credentials. Link or re-link your hubspot account in Formal…` > > **Cause:** HubSpot no longer accepts the linked token, for example after the user revoked access in HubSpot. > > **Fix:** Link HubSpot again from the [Employee Catalog](https://catalog.formal.ai). > [accordion] Laptop traffic doesn't appear in Logs > > **Cause:** The Endpoint isn't running, or the network rule doesn't match the client. > > **Fix:** Check the Endpoint is connected. The rule above only matches [known agents](https://docs.formal.ai/docs/guides/network-rules.md#known-agent-identities). Other clients, such as a browser, reach HubSpot directly unless the rule also matches them. See [Network rules](https://docs.formal.ai/docs/guides/network-rules.md). > [accordion] MCP clients can't connect directly yet > > **Cause:** The **Configuration** tab lists the reason, most often `No Connector is in this server's Space.` > > **Fix:** Edit the server and choose the Space containing its Connector. ## Next Steps > [card] [MCP Gateway](https://docs.formal.ai/docs/guides/core-concepts/connectors/mcp-gateway.md) > > Configure Connector routing and downstream access > [card] [All MCP servers](https://docs.formal.ai/docs/guides/core-concepts/connectors/mcp-servers/index.md) > > Browse every MCP server template This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.