HubSpot's MCP Auth Apps: Bridging the Gap for Custom Objects and Secure Integrations
HubSpot's ecosystem thrives on integrations, allowing users to connect various tools and services to streamline their workflows. Recently, a community member sparked a valuable discussion about the new MCP (Managed Component Platform) Auth Apps beta and its potential for connecting applications like Claude Desktop to HubSpot. The conversation highlighted both the progress made and the remaining hurdles in achieving seamless integration, particularly concerning custom object support and OAuth 2.1 implementation.
The Challenge: Connecting Apps Securely and Comprehensively
The original poster aimed to connect Claude to their HubSpot account using the Remote MCP Server, leveraging OAuth for secure authentication without managing static private app tokens. While the OAuth flow showed promise, several limitations surfaced:
- Lack of Custom Object Support: The remote MCP server currently only supports standard CRM objects, which limits its usefulness for teams heavily reliant on custom objects.
- OAuth 2.1 Incompletion: The OAuth flow failed to complete successfully when connecting via Claude Desktop's Connectors UI.
- Documentation Clarity: The absence of clear documentation regarding supported objects and limitations led to unnecessary troubleshooting.
In the meantime, the user found a workaround: using a private app token with a third-party MCP server that has full API access.
HubSpot's Response and Current Status
A HubSpot representative acknowledged the feedback and provided valuable context. As of the discussion, the Remote MCP Server offered read-only access to standard objects like contacts, companies, deals, tickets, carts, products, orders, line items, invoices, quotes, and subscriptions. Custom object support was not yet available. The representative also confirmed that MCP Auth Apps use OAuth 2.1 with PKCE (Proof Key for Code Exchange), a security extension that helps prevent certain attacks.
For those encountering issues with OAuth completion, the suggestion was to ensure proper PKCE handling, potentially using tools like the MCP Inspector. The HubSpot team encouraged users to submit feature requests for custom object support and OAuth completion issues through the official Developer Feedback form.
Practical Implications and Workarounds
For HubSpot users eager to leverage the MCP Auth Apps but facing limitations, here are a few takeaways:
- Assess Your Needs: Determine if your integration relies heavily on custom objects. If so, the current MCP Auth Apps might not be suitable.
- Explore Workarounds: As the original poster demonstrated, using a private app token with a third-party MCP server can provide a temporary solution.
- Provide Feedback: Actively submit feature requests and bug reports through the Developer Feedback form. This helps HubSpot prioritize development efforts based on user needs.
- Monitor Updates: Stay informed about updates to the MCP Auth Apps and its capabilities. HubSpot is continuously evolving its platform, and custom object support may be added in the future.
ESHOPMAN Team Comment
This discussion highlights a common challenge in platform development: balancing new features with comprehensive support for existing functionalities. While HubSpot's MCP Auth Apps show promise, the lack of custom object support is a significant limitation for many users, especially those with complex data structures. ESHOPMAN believes that prioritizing custom object support and improving documentation will be crucial for widespread adoption. For now, exploring alternative integration methods might be necessary to achieve full functionality.
The conversation underscores the importance of community feedback in shaping HubSpot's development roadmap. By actively engaging with the HubSpot Community and providing constructive criticism, users can play a vital role in improving the platform and its integrations. As HubSpot continues to enhance its MCP Auth Apps, the hope is that custom object support and streamlined OAuth flows will become a reality, unlocking even greater potential for seamless integration and automation. While we wait for those updates, keep exploring creative workarounds and sharing your experiences with the community – your insights can help others navigate the current limitations and contribute to a better future for HubSpot integrations.