Discover HubSpot objects
Inspect the connected account’s available tables and columns before selecting contacts, companies, deals or another supported object.
Your connection path
Your assistant works through your Stacksync workspace and its available connections.
“Plan a contact and company replica”
Stacksync MCP · CRM
Bring HubSpot connection discovery, connector actions and sync planning into an AI conversation. Use Stacksync MCP to prepare contact and company mappings, review deal automation, or understand why a HubSpot sync has failed records.
01 / The connection
Bring HubSpot connection discovery, connector actions and sync planning into an AI conversation. Use Stacksync MCP to prepare contact and company mappings, review deal automation, or understand why a HubSpot sync has failed records. Choose an AI client below to get started with the Stacksync MCP server.
The server belongs to Stacksync. The available HubSpot operations depend on your connection, permissions, and connector modules.
Explore the HubSpot connector →02 / Capabilities
Choose the connection path that fits the job. Your assistant inspects the available tools before configuring or running an action.
Inspect the connected account’s available tables and columns before selecting contacts, companies, deals or another supported object.
Inspect available HubSpot action modules and their input forms before proposing an individual lookup or update.
Read existing mappings, select table direction and propose edits without creating a second sync for the same records.
03 / Setup
Connect the MCP server first. Then connect HubSpot using the requirements below.
Connect Claude on the web or desktop to Stacksync through a custom connector and browser sign-in.
Open Customize → Connectors, select + Add, then Add custom connector. Name it Stacksync and use the server URL below.
https://mcp.stacksync.com/mcp Select Connect, complete the Stacksync sign-in in your browser and choose the default workspace. Clear Make changes on the consent screen if you only want read access.
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available HubSpot connection and capabilities.
Add the remote Stacksync server to Claude Code and authenticate from its MCP menu.
Run the command below. Add --scope user if you want the connection available across your projects.
claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp Open Claude Code, run /mcp, select stacksync and complete the Stacksync sign-in. Choose the workspace you want requests to use by default.
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available HubSpot connection and capabilities.
Add Stacksync as a custom MCP app in ChatGPT and sign in with OAuth.
Open Settings → Apps → Advanced settings and turn on Developer mode. If the option is unavailable, check the account or workspace policy with your administrator.
Select Create app, name it Stacksync, enter the server URL below and choose OAuth. Complete the Stacksync sign-in and select your default workspace.
https://mcp.stacksync.com/mcp Select Stacksync from the chat tools menu so the conversation can use its tools. Signing in to ChatGPT itself does not sign you in to Stacksync.
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available HubSpot connection and capabilities.
Configure Stacksync in Codex with a remote MCP URL and an explicit OAuth login.
Add the Stacksync endpoint to your Codex MCP configuration.
codex mcp add stacksync --url https://mcp.stacksync.com/mcp Run the login command and complete the Stacksync browser sign-in. Select a default workspace; restart your Codex session if the tools are not yet listed.
codex mcp login stacksync Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available HubSpot connection and capabilities.
Use Stacksync from Cursor by adding a remote server to its MCP configuration.
Merge this stacksync entry into the mcpServers object in ~/.cursor/mcp.json. Preserve any servers you already use.
{
"mcpServers": {
"stacksync": {
"url": "https://mcp.stacksync.com/mcp"
}
}
} Open Cursor’s MCP settings, select Connect beside stacksync and finish the Stacksync sign-in in your browser.
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available HubSpot connection and capabilities.
Connect Stacksync to GitHub Copilot Chat in VS Code using an HTTP MCP server.
Run the command below. Alternatively, add a stacksync entry with type http and this URL under servers in your project’s .vscode/mcp.json.
code --add-mcp '{"name":"stacksync","type":"http","url":"https://mcp.stacksync.com/mcp"}' Open Copilot Chat in Agent mode. Start stacksync from the tools picker and complete the Stacksync browser sign-in.
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available HubSpot connection and capabilities.
Add Stacksync to Cascade with Windsurf’s serverUrl configuration and OAuth sign-in.
In the Cascade panel, open the … menu and select Open MCP config file. Merge this entry into mcp_config.json without removing other servers.
{
"mcpServers": {
"stacksync": {
"serverUrl": "https://mcp.stacksync.com/mcp"
}
}
} Save the configuration. Cascade opens the Stacksync sign-in flow the first time it uses the server. Choose your default workspace.
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available HubSpot connection and capabilities.
Connect the Gemini command-line client to Stacksync through remote HTTP MCP and browser authorization.
Run the following command in your terminal to add the HTTP server.
gemini mcp add --transport http stacksync https://mcp.stacksync.com/mcp Start Gemini CLI, run the command below and finish the Stacksync sign-in in your browser.
/mcp auth stacksync Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available HubSpot connection and capabilities.
04 / Put it to work
Example prompts for HubSpot. The outcomes describe what to expect, not results from your account. Review the proposed configuration before running it.
Inspect my HubSpot and PostgreSQL connections, available contacts and companies fields, and existing syncs. Propose a one-way reporting replica with stable HubSpot record IDs and the fields needed to join contacts to companies. Separate any association configuration that I must complete in the web app. Wait for my review before creating or starting the sync.
A contact and company reporting design with explicit relationship and setup requirements.
Inspect the HubSpot and Slack connector modules, connections and existing workflows. Propose a workflow that identifies the closed-won deal condition and prepares a message for the Slack channel I choose. Verify the trigger path and every action from the available forms; flag any step that needs the web app. Show the payload and duplicate-message handling before saving or running it.
A proposed deal alert with a verified trigger path and channel-specific message payload.
Inspect my HubSpot sync issues and current field mappings. Identify failures caused by property formats, permissions or missing required values. Propose a correction for each group with example affected record IDs. Ask me to choose any retry, revert or ignore operation before executing it.
An actionable breakdown of HubSpot property errors without silently discarding updates.
05 / Before you run
OAuth access follows your Stacksync role. Choose read-only access during sign-in when appropriate. Workspace owners can enable “Ask before every change”; it is a configurable setting. Direct connector actions also follow gateway policies.
Read about permissions and approvals ↗06 / Common questions
The sync documentation includes contacts, companies, deals, tickets and many other objects. That list describes sync support; the available direct MCP actions must be discovered separately in the connector catalog.
The sync connector documents custom-object support, but the HubSpot account must have the required Enterprise entitlement and the connection must expose the object.
It can inspect the sync and prepare the mapping plan. The current sync skill directs association settings and per-field direction to the Stacksync web app.
Keep building