HubSpot MCP Server

Created By
Meerkats-Aia year ago
hubspot-mcp-server typescript
Overview

what is HubSpot MCP Server?

HubSpot MCP Server is a powerful Model Context Protocol (MCP) server implementation designed for seamless integration with HubSpot CRM, enabling AI assistants to interact with HubSpot data effectively.

how to use HubSpot MCP Server?

To use the HubSpot MCP Server, clone the repository, install dependencies, and start the server with your HubSpot API access token. You can also integrate it with AI assistants that support the Model Context Protocol.

key features of HubSpot MCP Server?

  • Seamless AI integration with HubSpot CRM data
  • Simplified CRM operations through natural language commands
  • Real-time access to HubSpot data
  • Secure authentication using HubSpot's API token
  • Extensible design for adding more HubSpot API capabilities

use cases of HubSpot MCP Server?

  1. Creating and managing contacts and companies in HubSpot CRM.
  2. Retrieving detailed company activity history and engagement timelines.
  3. Accessing recent engagement data across the HubSpot instance.
  4. Performing CRM operations directly from AI assistants.

FAQ from HubSpot MCP Server?

  • What is the purpose of the HubSpot MCP Server?

It allows AI assistants to interact with HubSpot CRM data seamlessly.

  • How do I authenticate with HubSpot MCP Server?

You can authenticate using a HubSpot API access token, which can be provided as an environment variable or command-line argument.

  • Is the HubSpot MCP Server extensible?

Yes! The server is designed to be easily extensible for adding new HubSpot API capabilities.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Meerkats-Ai
Star
0
Language
TypeScript
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)

6 hours ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago