Does HubSpot Have an MCP Server? Both of Them, Explained

• HubSpot MCP server (remote). This is the one most people mean. It is a hosted bridge that lets an authorized MCP client connect to a specific HubSpot account and work with live CRM records. If your goal is an AI assistant that can look up a deal, summarise a ticket history, or write a note back to a contact, this is the server.
• Developer MCP server (local). CLI-based and aimed at developers building on HubSpot. It helps agentic development tools scaffold and manage projects on the Developer Platform. It needs Developer Platform v2025.2 and is set up with the hs mcp setup command. Useful, but it is a build-time tool, not a way to put CRM data in front of a revenue team.

• Read: contacts, companies, deals, tickets, leads, users, appointments, courses, listings, projects, services, custom objects and segments; calls, emails, meetings, notes and tasks; blog posts, landing pages, site pages, campaigns and marketing events; content analytics; conversations from connected inboxes; marketing email drafts and analytics; account and team information. Revenue objects such as carts, invoices, orders, line items, products, quotes and subscriptions are readable in beta.
• Write: create and edit contacts, companies, deals, tickets, leads, line items, products, appointments, courses, listings, projects, services and custom object records; log activities; create, edit and publish landing pages, website pages and blog posts; manage campaigns, email drafts, pipelines, custom properties and static segments. Quote writes are in beta.

Some areas depend on the subscription. AEO tools need Marketing Hub Professional or Enterprise, and quote writes need Revenue Hub Professional or Enterprise. HubSpot says tool availability varies by subscription, permissions and account configuration, and suggests running get_user_details to see what a given account can reach.

1. Create an MCP connector in your HubSpot account under Development, then MCP Connectors. HubSpot generates OAuth credentials.
2. Point your client at https://mcp.hubspot.com with the connector’s client ID, client secret and redirect URL. The client must support OAuth with PKCE.
3. Authorize by choosing the HubSpot account and granting permissions. Scopes come from the server’s tools and the permissions you grant, not from a list you define.
4. Verify with the get_user_details tool.

Developers who want the local server instead install the HubSpot CLI and run hs mcp setup.

• Sensitive data. If an account has sensitive data turned on, HubSpot blocks Activity objects (calls, emails, meetings, notes, tasks) through the MCP server. The standard CRM APIs are not affected.
• Tier-dependent tools. Several tool groups require specific Hub subscriptions, and free-tools accounts cannot create custom pipelines through the server.
• Reinstall on scope changes. When HubSpot adds tools, existing installs must reconnect to grant the new scopes.
• Beta areas. Revenue object reads and quote writes were marked beta on October 6, 2026.

This is why the answer for eLead is different from the answer here. A restricted API with no MCP layer leaves you building middleware. HubSpot does not have that problem.