Hubspot

Created By
shinzo-labsa year ago
Overview

what is HubSpot MCP?

HubSpot MCP is a Model Context Protocol implementation for the HubSpot API, providing a standardized interface for accessing and managing CRM data.

how to use HubSpot MCP?

To use HubSpot MCP, you need to obtain an API key from HubSpot and configure it in your project. You can install it via NPX or manually download it from the GitHub repository.

key features of HubSpot MCP?

  • Complete coverage of the HubSpot CRM API
  • Support for all standard CRM objects (companies, contacts, deals, etc.)
  • Advanced association management with CRM Associations v4
  • Batch operations for efficient data management
  • Advanced search and filtering capabilities
  • Type-safe parameter validation with Zod

use cases of HubSpot MCP?

  1. Managing CRM data for businesses using HubSpot.
  2. Automating the creation and updating of CRM objects.
  3. Performing batch operations for data management.

FAQ from HubSpot MCP?

  • What is the Model Context Protocol?

The Model Context Protocol is a standard for managing and accessing data in a consistent manner across different APIs.

  • How do I obtain an API key?

You can obtain an API key by following the steps outlined in the HubSpot API documentation.

  • Is HubSpot MCP free to use?

Yes, HubSpot MCP is free to use, but you need a HubSpot account to access the API.

Server Config

{
  "mcpServers": {
    "hubspot": {
      "command": "npx",
      "args": [
        "@shinzolabs/hubspot-mcp"
      ],
      "env": {
        "HUBSPOT_ACCESS_TOKEN": "your-token-here"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
shinzo-labs
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago