MCP Gateway · Claude Cowork
Connect HubSpot to Claude Cowork
Attribution and territory reviews pull from many HubSpot objects at once, which suits Cowork's longer tasks. With HubSpot delivered to Cowork through a plugin from Speakeasy's synced marketplace, a single session can gather campaign contacts, CRM records and owners and write up the result. Agent hooks send each prompt to Speakeasy before the step runs.
- Category
- Sales & CRM
- Tools
- 13
- Authentication
- OAuth
- Claude Cowork
- Cowork tab in Claude Desktop
Behind the MCP Gateway
Run HubSpot MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every HubSpot call inspected and logged.
Before you start
What HubSpot needs first
A HubSpot user with access to the Development workspace; an account admin for the first connection does the HubSpot side of the setup.
- The remote MCP server is available to all HubSpot accounts.
- You need a user who can open the Development workspace.
- The first connection should be made by an account admin.
In HubSpot
- Open Development > MCP Connectors.
- Create an MCP connector with the Speakeasy redirect URL.
- Copy the Client ID and Client secret.
Set up
Add HubSpot to Claude Cowork in 4 steps
- 01
Add HubSpot from the catalog
An admin finds HubSpot in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.
HubSpot uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.
Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.
- 02
Choose who can use HubSpot
Give teams the
mcp:connectscope on the HubSpot server through team access or a role. Claude Cowork connects to the HubSpot server's own URL, and the server's authorization decides who can connect and which tools they can call. - 03
Connect Claude Cowork
Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork.
New MCP servers join the project's default plugin automatically. Each server's overview page shows which plugin it is published to, with Publish or Update to change it.
Add the importing admin's GitHub username as a marketplace collaborator and accept the invite. Only that admin needs it.
In Claude Organization settings > Plugins & skills, select Add > Sync from GitHub and pick the organization's plugin repository. The Claude GitHub App must be installed on it.
Mark the observability plugin Required, and set the plugin that carries this server to Available to install or Installed by default.
In the Cowork tab's Monitoring settings, set the OTLP endpoint, protocol and headers.
- 04
Sign in and use HubSpot from Claude Cowork
The first time Claude Cowork connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
HubSpot needs its own OAuth grant, so each person connects it once. Until they do, HubSpot calls fail while the rest of the gateway keeps working.
From then on, HubSpot's tools appear in Claude Cowork, limited to what the person's access allows, and every call lands in the gateway's tool logs.
Cowork reads the synced repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.
Use cases
What Claude Cowork users do with HubSpot
Build a campaign attribution report
Cowork gets the contacts a campaign sourced on first touch and the ones it influenced, fetches their records, and writes a report on who they are and which companies they come from.
get_campaign_contacts_by_typeget_crm_objectsget_campaign_analytics
Audit account ownership by team
Cowork lists every team and its members, then checks companies for owners who are inactive or sit outside the right team, and flags each one for reassignment.
Document the CRM's custom fields
Have Cowork go through every property on deals and companies and produce a reference document with each field's label, type and allowed values.
Tools
13 tools
Each HubSpot tool can be allowed or denied per team and role at the MCP Gateway before Claude Cowork sees it.
search_crm_objects
Searches and retrieves CRM records from HubSpot based on filters and criteria.
submit_feedback
Collects and submits feedback to HubSpot on dissatisfaction or user request.
get_campaign_contacts_by_type
Get paginated contact IDs for a campaign filtered by attribution type.
search_owners
Lists and searches for owners who can be assigned to CRM records.
get_campaign_analytics
Get campaign analytics (METRICS or REVENUE_ATTRIBUTION) for one or more campaigns. Each entry in the request list is a full analytics request. Each response contains the campaignObjectId of the requested campaign.
get_campaign_asset_types
List the asset type names available as campaign assets (e.g. LANDING_PAGE, BLOG_POST). Use the returned names as the assetType parameter in getCampaignAssetMetrics.
Control
What Speakeasy can see and stop in Claude Cowork
The gateway covers every client the same way. The rest depends on what Claude Cowork exposes to Speakeasy.
Tool logs
Gateway
Every HubSpot call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the HubSpot tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to HubSpot can reject a tool request before it reaches the server, or withhold a result from Claude Cowork. MCP-scoped policies are enabled per organization.
Prompt blocking
Claude Cowork
Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs.
Session telemetry
Claude Cowork
Cowork's OTLP export ties sessions to people and feeds observability.
Anthropic inference hooks
Claude Cowork
On Claude Enterprise, prompts can be checked before inference (beta).
- Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
- Personal Claude accounts can't be governed in Cowork.
Questions
Frequently asked questions
Does every Cowork member need a GitHub invite to use HubSpot?
How are Cowork's HubSpot sessions tied to people?
How do Claude Cowork users get HubSpot?
Are HubSpot calls from Claude Cowork logged?
Connect more