HubSpot Server Connector for Model Context Protocol (MCP)

This implementation serves as an MCP server component designed to interface directly with the HubSpot CRM backend. It exposes standardized methods for performing full CRUD (Create, Retrieve, Update, Delete) operations exclusively on data persisted as 'Note' engagements within the HubSpot ecosystem. A key value proposition is the server-side capability to immediately disseminate fetched or newly engineered data payloads through established messaging conduits (chat/email).

Deployment Instructions (Docker)

To containerize and execute the service:

Image Construction: docker build -t mcp-hubspot-ts .
Runtime Execution: docker run --env-file .env -it mcp-hubspot-ts

Core Capabilities

Provisioning new summary artifacts within HubSpot, structured as Note engagements.
Executing bulk retrieval queries for all existing summary entries (Notes).
Applying temporal filters to restrict record fetching based on specified date criteria.
Modifying the content or metadata of extant summary records.
Permanently purging specified summary records from the system.
Facilitating the transmission of record contents using connected chat or email delivery mechanisms.

Testing and Diagnostics via MCP Inspector

The dedicated MCP Inspector utility is the recommended environment for end-to-end functional validation. Initiate the inspector, pointing it toward this running server instance, supplying necessary authentication tokens via environment variables:

bash npx @modelcontextprotocol/inspector -e HUBSPOT_ACCESS_TOKEN=your_access_token_here node build/index.js

This command activates the local UI, typically accessible at http://localhost:5173, allowing for the construction and submission of JSON-RPC requests to the server endpoint.

Configuration Environment Variables

Configuration relies on a .env file situated in the repository's root directory, containing required authentication credentials:

env HUBSPOT_ACCESS_TOKEN=your_access_token_here SHARED_CONTACT_ID=your_contact_id_here

Licensing Information

This software is released under the permissive terms of the MIT License; consult the [LICENSE] file for the comprehensive legal text.

WIKIPEDIA: Cloud computing is "a paradigm for enabling network access to a scalable and elastic pool of shareable physical or virtual resources with self-service provisioning and administration on-demand," according to ISO. It is commonly referred to as "the cloud".

== Characteristics ==

In 2011, the National Institute of Standards and Technology (NIST) identified five "essential characteristics" for cloud systems. Below are the exact definitions according to NIST:

On-demand self-service: "A consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with each service provider." Broad network access: "Capabilities are available over the network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, tablets, laptops, and workstations)." Resource pooling: " The provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to consumer demand." Rapid elasticity: "Capabilities can be elastically provisioned and released, in some cases automatically, to scale rapidly outward and inward commensurate with demand. To the consumer, the capabilities available for provisioning often appear unlimited and can be appropriated in any quantity at any time." Measured service: "Cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported, providing transparency for both the provider and consumer of the utilized service. By 2023, the International Organization for Standardization (ISO) had expanded and refined the list.

== History ==

The history of cloud computing extends to the 1960s, with the initial concepts of time-sharing becoming popularized via remote job entry (RJE). The "data center" model, where users submitted jobs to operators to run on mainframes, was predominantly used during this era. This was a time of exploration and experimentation with ways to make large-scale computing power available to more users through time-sharing, optimizing the infrastructure, platform, and applications, and increasing efficiency for end users. The "cloud" metaphor for virtualized services dates to 1994, when it was used by General Magic for the universe of "places" that mobile agents in the Telescript environment could "go". The metaphor is credited to David Hoffman, a General Magic communications specialist, based on its long-standing use in networking and telecom. The expression cloud computing became more widely known in 1996 when Compaq Computer Corporation drew up a business plan for future computing and the Internet. The company's ambition was to superch