Hubspot Mcp Server

Created By
DidelotKa year ago
MCP server for integrating HubSpot with Claude Desktop and other MCP clients. Provides access to HubSpot contacts, companies, and deals through conversational tools.
Overview

What is HubSpot MCP Server?

HubSpot MCP Server is a Model Context Protocol server designed to integrate HubSpot with Claude Desktop and other MCP clients, allowing users to access HubSpot contacts, companies, and deals through conversational tools.

How to use HubSpot MCP Server?

To use the HubSpot MCP Server, clone the repository, configure your HubSpot API key, and run the server using the provided command. You can then interact with the server using natural language commands.

Key features of HubSpot MCP Server?

  • Integration with HubSpot for managing contacts, companies, and deals.
  • Conversational interface for easy access to HubSpot data.
  • Multiple tools available for various HubSpot functionalities.

Use cases of HubSpot MCP Server?

  1. Listing and filtering HubSpot contacts.
  2. Creating new deals in HubSpot.
  3. Searching for specific deals or companies.

FAQ from HubSpot MCP Server?

  • What programming language is used?

The server is built using Python.

  • Do I need a HubSpot account?

Yes, a HubSpot account with API access is required to use this server.

  • Is there documentation available?

Yes, comprehensive documentation is provided in the repository.

Server Config

{
  "mcpServers": {
    "hubspot": {
      "command": "uv",
      "args": [
        "run",
        "python",
        "/path/to/your/project/main.py",
        "--mode",
        "stdio"
      ],
      "env": {
        "HUBSPOT_API_KEY": "your_hubspot_api_key"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
DidelotK
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
Crevio

2 days ago