HubSpot MCP Server

Created By
KaranThink41a year ago
MCP server for integrating with HubSpot CRM, allowing seamless creation, retrieval, and management of summary records as Note engagements, all linked to a dedicated shared contact record.
Overview

what is HubSpot MCP Server?

HubSpot MCP Server is a Model Context Protocol (MCP) server designed for seamless integration with HubSpot CRM, enabling users to create, retrieve, and manage summary records as Note engagements linked to a dedicated shared contact record.

how to use HubSpot MCP Server?

To use the HubSpot MCP Server, you can either install it via Smithery or manually by installing dependencies, creating a .env file with your HubSpot credentials, building the project, and starting the server.

key features of HubSpot MCP Server?

  • Create summary records as Note engagements in HubSpot
  • Fetch all summary records (Notes) from HubSpot
  • Filter summary records by date
  • Update existing summary records
  • Delete summary records
  • Send summary records via command box
  • Integration with HubSpot contact pipeline

use cases of HubSpot MCP Server?

  1. Automating the creation of Note engagements in HubSpot.
  2. Managing and retrieving summary records for reporting purposes.
  3. Integrating HubSpot CRM with other applications for enhanced data management.

FAQ from HubSpot MCP Server?

  • How do I install the HubSpot MCP Server?

You can install it via Smithery or manually by following the installation instructions provided in the documentation.

  • What programming language is used for this project?

The HubSpot MCP Server is built using JavaScript.

  • Is there a license for this project?

Yes, this project is licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
KaranThink41
Star
0
Language
JavaScript
License
MIT 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
Crevio

2 days ago