logo
Free, unlimited AI code reviews that run on commit
git-lrc git-lrc GitHub Install Now We'd appreciate a star git-lrc - Free, unlimited AI code reviews that run on commit | Product Hunt git-lrc - Free, unlimited AI code reviews that run on commit | Product Hunt

cdata-hubspot-mcp-gateway

Establishes a read-only Model Context Protocol (MCP) endpoint for interrogating live HubSpot datasets using natural language, abstracting away the necessity for direct SQL interaction. Leverages the robust CData JDBC Driver for HubSpot to facilitate real-time data retrieval by Large Language Models (LLMs).

Author

cdata-hubspot-mcp-gateway logo

CDataSoftware

MIT License

Quick Info

GitHub GitHub Stars 0
NPM Weekly Downloads 0
Tools 1
Last Updated 2026-02-19

Tags

cdatasoftwarehubspotjdbccdatasoftware hubspothubspot datahubspot information

CData Model Context Protocol (MCP) Server Implementation for HubSpot Access

:warning: Important Distinction: This repository provides a restricted, read-only MCP server component. For a comprehensive data access solution encompassing full CRUD (Create, Read, Update, Delete) operations plus action invocation, explore the enhanced, simplified CData MCP Server for HubSpot (beta) available here: CData Download Link.

Core Objective

This read-only MCP gateway was engineered specifically to empower sophisticated LLMs (such as Claude Desktop) to execute queries against current, live data residing within HubSpot instances. This capability is underpinned by the powerful CData JDBC Driver for HubSpot.

The CData JDBC Driver excels at transforming HubSpot's operational data structures into a familiar, relational SQL-like model. Our server component encapsulates this driver, exposing HubSpot entities via a streamlined MCP interface. Consequently, generative AI clients can derive insights and retrieve up-to-the-minute information simply by posing questions in plain, conversational language—no database querying syntax (SQL) is required from the user.

Deployment Instructions

  1. Source Code Acquisition: bash git clone https://github.com/cdatasoftware/hubspot-mcp-server-by-cdata.git cd hubspot-mcp-server-by-cdata

  2. Compilation & Packaging: bash mvn clean install

    This process generates the executable artifact: CDataMCP-jar-with-dependencies.jar 3. JDBC Driver Acquisition: Download and install the prerequisite CData JDBC Driver for HubSpot: Driver Download Portal 4. Driver Licensing Procedure: * Locate the driver installation directory (typical paths): * Windows: C:\Program Files\CData\CData JDBC Driver for HubSpot\ * Mac/Linux: /Applications/CData JDBC Driver for HubSpot/ * Execute the licensing utility: bash java -jar cdata.jdbc.hubspot.jar --license

    • Input your credentials and use "TRIAL" or your actual entitlement key when prompted.
    • Data Source Connection Configuration:
    • Initiate the connection string utility: bash java -jar cdata.jdbc.hubspot.jar

    • Within the utility, precisely define and validate your HubSpot connection parameters (OAuth authentication may require browser interaction).

    • Upon successful validation, save the resultant JDBC Connection String for subsequent steps.
    • Property File Creation (.prp): Construct a configuration file (e.g., hubspot.prp) detailing server metadata and connection parameters:
    • Prefix: Namespace identifier for exposed tools.
    • ServerName: Designated name for the MCP service instance.
    • ServerVersion: Version identifier.
    • DriverPath: Absolute file system path to the downloaded JDBC driver JAR.
    • DriverClass: Fully qualified name of the JDBC driver implementation (e.g., cdata.jdbc.hubspot.HubSpotDriver).
    • JdbcUrl: The connection string obtained in the previous step.
    • Tables: Specify table names for restricted access; leave empty (Tables=) for full schema exposure. env Prefix=hubspot ServerName=CDataHubSpot ServerVersion=1.0 DriverPath=PATH\TO\cdata.jdbc.hubspot.jar DriverClass=cdata.jdbc.hubspot.HubSpotDriver JdbcUrl=jdbc:hubspot:InitiateOAuth=GETANDREFRESH; Tables=

Integrating with LLM Clients (e.g., Claude Desktop)

  1. Client Configuration File Update: Create or modify the client's configuration file (claude_desktop_config.json) to incorporate the new MCP server definition within the mcpServers block.

    Windows Configuration Snippet:

    { "mcpServers": { "{classname_dash}": { "command": "PATH\TO\java.exe", "args": [ "-jar", "PATH\TO\CDataMCP-jar-with-dependencies.jar", "PATH\TO\hubspot.prp" ] }, ... } }

    Linux/Mac Configuration Snippet:

    { "mcpServers": { "{classname_dash}": { "command": "/PATH/TO/java", "args": [ "-jar", "/PATH/TO/CDataMCP-jar-with-dependencies.jar", "/PATH/TO/hubspot.prp" ] }, ... } }

    If necessary, relocate the configuration file to the client's designated application support directory: Windows Relocation: bash cp C:\PATH\TO\claude_desktop_config.json %APPDATA%\Claude\claude_desktop_config.json

    Linux/Mac Relocation: bash cp /PATH/TO/claude_desktop_config.json /Users/{user}/Library/Application\ Support/Claude/claude_desktop_config.json'

  2. Client Restart: Fully terminate and relaunch your consuming client application (e.g., Claude Desktop). Server registration is typically completed during client initialization.

Tip: If the server does not appear, ensure the client process is completely shut down (check Task Manager/Activity Monitor).

Standalone Server Execution

To launch the MCP endpoint independently (useful for direct testing over stdio): bash java -jar /PATH/TO/CDataMCP-jar-with-dependencies.jar /PATH/TO/Salesforce.prp

Constraint: This mode communicates via standard input/output (stdio) and mandates that the client application executing the queries reside on the same host machine.

Operational Usage Guidelines

Once the MCP server is correctly integrated into the client's configuration, the LLM gains access to the underlying HubSpot data schema via its toolset. Explicit tool invocation is generally unnecessary; the AI agent will self-select the appropriate mechanism based on the user's request. Examples of natural language inquiries: * "Determine the correlation coefficient between closed/won opportunities and the associated account's defined industry sector." * "Quantify the total volume of pending support tickets logged within the primary SUPPORT project." * "List all scheduled calendar entries assigned to me for the current day."

The available procedural interfaces exposed by this server are detailed below, where {servername} corresponds to the identifier used in the configuration file (e.g., hubspot_get_tables).

Function Signatures & Descriptions

  • {servername}_get_tables: Fetches an enumerated list of all accessible relational structures within the connected HubSpot environment. Follow up with {servername}_get_columns for schema details. Output is delivered in CSV format, starting with header row definitions.
  • {servername}_get_columns: Retrieves the attribute list (columns) pertaining to a specified data table. Requires the table identifier as an argument. Output is delivered in CSV format, starting with header row definitions.
  • {servername}_run_query: Executes an arbitrary SQL SELECT statement against the HubSpot data model.

JSON-RPC Request Schemas (For Scripted Interaction)

For developers integrating directly via JSON-RPC 2.0 protocols rather than relying on the AI client's abstraction layer, use these payload examples:

Invocation: hubspot_get_tables

{ "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "hubspot_get_tables", "arguments": {} } }

Invocation: hubspot_get_columns

{ "jsonrpc": "2.0", "id": 2, "method": "tools/call", "params": { "name": "hubspot_get_columns", "arguments": { "table": "Account" } } }

Invocation: hubspot_run_query

{ "jsonrpc": "2.0", "id": 3, "method": "tools/call", "params": { "name": "hubspot_run_query", "arguments": { "sql": "SELECT * FROM [Account] WHERE [IsDeleted] = true" } } }

Troubleshooting Common Issues

  1. Server Invisible in Client: Verify that the client application (e.g., Claude Desktop) was completely shut down before restarting it, allowing for proper registration of the new MCP endpoint.
  2. Data Retrieval Failures: Cross-reference the connection settings. Confirm that the JDBC URL copied into the .prp file was accurately sourced from the connection string utility test.
  3. Connectivity Problems: For issues directly related to linking with the HubSpot API, please engage CData Technical Support.
  4. MCP Server Operational Feedback: General feedback or issues with the server's function should be directed to the CData User Community.

Licensing

This specific read-only MCP server software is distributed under the permissive MIT License terms. Full rights to use, modify, and redistribute are granted, contingent upon adherence to the MIT License stipulations detailed in the repository's LICENSE file.

Comprehensive Data Source Compatibility List

This driver stack supports integration with an extensive array of data systems, including (but not limited to):

AccessAct CRMAct-OnActive Directory
ActiveCampaignAcumaticaAdobe AnalyticsAdobe Commerce
ADPAirtableAlloyDBAmazon Athena
Amazon DynamoDBAmazon MarketplaceAmazon S3Asana
Authorize.NetAvalara AvaTaxAvroAzure Active Directory
Azure Analysis ServicesAzure Data CatalogAzure Data Lake StorageAzure DevOps
Azure SynapseAzure TableBasecampBigCommerce
BigQueryBing AdsBing SearchBitbucket
Blackbaud FE NXTBoxBullhorn CRMCassandra
CertiniaCloudantCockroachDBConfluence
Cosmos DBCouchbaseCouchDBCSV
CventDatabricksDB2DocuSign
DropboxDynamics 365Dynamics 365 Business CentralDynamics CRM
Dynamics GPDynamics NAVeBayeBay Analytics
ElasticsearchEmailEnterpriseDBEpicor Kinetic
Exact OnlineExcelExcel OnlineFacebook
Facebook AdsFHIRFreshdeskFTP
GitHubGmailGoogle Ad ManagerGoogle Ads
Google AnalyticsGoogle CalendarGoogle Campaign Manager 360Google Cloud Storage
Google ContactsGoogle Data CatalogGoogle DirectoryGoogle Drive
Google SearchGoogle SheetsGoogle SpannerGraphQL
GreenhouseGreenplumHarperDBHBase
HCL DominoHDFSHighriseHive
HubDBHubSpotIBM Cloud Data EngineIBM Cloud Object Storage
IBM InformixImpalaInstagramJDBC-ODBC Bridge
JiraJira AssetsJira Service ManagementJSON
KafkaKintoneLDAPLinkedIn
LinkedIn AdsMailChimpMariaDBMarketo
MarkLogicMicrosoft DataverseMicrosoft Entra IDMicrosoft Exchange
Microsoft OneDriveMicrosoft PlannerMicrosoft ProjectMicrosoft Teams
Monday.comMongoDBMYOB AccountRightMySQL
nCinoNeo4JNetSuiteOData
OdooOffice 365OktaOneNote
OracleOracle EloquaOracle Financials CloudOracle HCM Cloud
Oracle SalesOracle SCMOracle Service CloudOutreach.io
ParquetPaylocityPayPalPhoenix
PingOnePinterestPipedrivePostgreSQL
Power BI XMLAPrestoQuickbaseQuickBooks
QuickBooks OnlineQuickBooks TimeRaisers Edge NXTReckon
Reckon Accounts HostedRedisRedshiftREST
RSSSage 200Sage 300Sage 50 UK
Sage Cloud AccountingSage IntacctSalesforceSalesforce Data Cloud
Salesforce Financial Service CloudSalesforce MarketingSalesforce Marketing Cloud Account EngagementSalesforce Pardot
SalesloftSAPSAP Ariba ProcurementSAP Ariba Source
SAP Business OneSAP BusinessObjects BISAP ByDesignSAP Concur
SAP FieldglassSAP HANASAP HANA XS AdvancedSAP Hybris C4C
SAP Netweaver GatewaySAP SuccessFactorsSAS Data SetsSAS xpt
SendGridServiceNowSFTPSharePoint
SharePoint Excel ServicesShipStationShopifySingleStore
SlackSmartsheetSnapchat AdsSnowflake
SparkSplunkSQL Analysis ServicesSQL Server
SquareStripeSugar CRMSuiteCRM
SurveyMonkeySybaseSybase IQTableau CRM Analytics
TallyTaxJarTeradataTier1
TigerGraphTrelloTrinoTwilio
TwitterTwitter AdsVeeva CRMVeeva Vault
Wave FinancialWooCommerceWordPressWorkday
xBaseXeroXMLYouTube Analytics
ZendeskZoho BooksZoho CreatorZoho CRM
Zoho InventoryZoho ProjectsZuora... Over 300 Connectors

== Contextual Background: Business Management Systems ==

WIKIPEDIA Overview: Business management tools encompass the spectrum of systems, applications, procedural controls, computational solutions, and methodologies employed by organizations to navigate fluctuating market dynamics, secure a sustained competitive advantage, and systematically enhance overall enterprise performance.

== Functional Classification == Management tools can be segmented based on their operational focus. A functional classification highlights:

  • Systems dedicated to data ingestion and integrity validation across all departments.
  • Instrumentation for monitoring and optimizing operational workflows.
  • Platforms for aggregating information and supporting executive decision-making.

Modern management tools have undergone rapid, technology-driven transformation, presenting managers with a complex landscape for selection. The perpetual drive for cost optimization, sales augmentation, deep customer insight acquisition, and precise product fulfillment necessitates a strategic, rather than reactive, approach to tool adoption. Tools must be meticulously chosen and subsequently tailored to the specific operational requirements of the organization, avoiding the pitfalls of unmodified, off-the-shelf integration.

== Prominent Tools (Circa 2013 Survey Insights) == Research by Bain & Company indicated key global tool utilization patterns reflecting regional economic needs and market conditions. The leading ten categories included:

  • Strategic Planning Frameworks
  • Client Relationship Management (CRM)
  • Personnel Sentiment Measurement (Engagement Surveys)
  • Competitive Analysis (Benchmarking)
  • Performance Measurement (Balanced Scorecard)
  • Core Competency Identification
  • Operational Strategy (Outsourcing)
  • Organizational Transition Programs (Change Management)
  • Logistics and Procurement Coordination (Supply Chain)
  • Mission and Vision Articulation
  • Target Audience Definition (Market Segmentation)
  • Comprehensive Quality Assurance Methodologies (TQM)

== Business Software Applications == Software applications, defined as collections of programs designed for enterprise users, aim to increase productivity, accurately measure output, and streamline various corporate functions. This evolution began with Management Information Systems (MIS), expanded through Enterprise Resource Planning (ERP), integrated CRM functionality, and has now largely migrated toward cloud-based management solutions. While a clear link exists between IT investment and organizational results, maximizing value depends critically on effective deployment strategies and the judicious selection and customization of the supporting tools.

See Also

`