HubSpot MCP Server
Deploy and configure the HubSpot MCP server with authentication, use cases, security notes, and India-ready hosting guidance.
Quick Answer / TL;DR
The HubSpot MCP server exposes HubSpot capabilities to AI clients through scoped tools, resources, and JSON-RPC calls, using HubSpot Private App Access Token for authentication.
Key Takeaways
- Authentication: HubSpot Private App Access Token.
- Category: Productivity.
- Best first use case: List active sales opportunities.
- Use environment variables and least-privilege scopes for production.
Integration overview
Expose HubSpot contacts, pipelines, deals, and engagement history to let models act as personalized sales assistants.
Use this connector when an AI assistant such as Claude, Cursor, or a custom agent needs a governed path into HubSpot. Keep the server focused on the approved workflows instead of exposing a whole account or admin surface.
For Indian teams, deploy the connector near the users and the data source, then add request IDs, redaction, and audit logs before connecting production data.
| Field | Value |
|---|---|
| Connector | HubSpot MCP Server |
| Category | Productivity |
| Authentication | HubSpot Private App Access Token |
| Production route | /servers/hubspot-mcp-server/ |
Features and use cases
HubSpot is most useful when the agent has a narrow job to complete and the server can validate every argument before execution.
Start with read-only or low-risk tools. Add write operations only after approval prompts, scoped credentials, and logging are working.
| Capability | Recommended guardrail |
|---|---|
| Contact indexing | Allow with scoped read access |
| Deal status triggers | Allow with scoped read access |
| Activity logs writing | Allow with scoped read access |
| Company lookups | Allow with scoped read access |
Local and hosted configuration
Configure HubSpot with credentials stored in environment variables. Do not hardcode tokens in prompts, repositories, screenshots, or browser-visible code.
The local configuration pattern works for a single developer. Hosted deployments should add TLS, bearer-token authentication, health checks, and monitoring.
{
"mcpServers": {
"hubspot": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-hubspot"],
"env": {
"HUBSPOT_TOKEN": "${HUBSPOT_TOKEN}"
}
}
}
}Security and permissions
Protect HubSpot Private App Access Token credentials with least privilege, rotation, and separate environments for development, staging, and production.
Review every tool output for sensitive data before letting it enter model context. For regulated Indian workflows, add DPDP-aware redaction and retention controls.
{
"server": "hubspot-mcp-server",
"auth": "HubSpot Private App Access Token",
"policy": {
"leastPrivilege": true,
"redactSecrets": true,
"requireApprovalForWrites": true,
"auditToolCalls": true
}
}HubSpot MCP Server FAQs
Direct answers for developers, operators, and Indian teams evaluating MCP.