HubSpot MCP Troubleshooting

Error: “No server info found”

This error typically occurs when:

  1. The MCP server configuration format is incorrect
  2. The OAuth flow hasn’t been initiated yet
  3. Cursor needs to be restarted after configuration changes

Configuration Fix Applied

Changed "type": "http" to "transport": "http" to match HubSpot MCP documentation format.

Current Configuration

{
  "hubspot": {
    "url": "https://mcp.hubspot.com/",
    "transport": "http",
    "auth": {
      "type": "oauth",
      "clientId": "e151e63f-399c-4c64-b1b2-7616966f79f9",
      "clientSecret": "7dd6e6e2-7e91-4ba2-8123-7ca4e655bf06",
      "redirectUri": "https://www.brainforge.ai"
    }
  }
}

Steps to Resolve

1. Verify Configuration

Check that ~/.cursor/mcp.json has the correct format:

  • Uses "transport": "http" (not "type")
  • OAuth credentials are correct
  • Redirect URI matches HubSpot app settings

2. Restart Cursor

Critical: Fully quit and restart Cursor after configuration changes:

  1. Quit Cursor completely (Cmd+Q)
  2. Wait a few seconds
  3. Reopen Cursor

3. Initiate OAuth Flow

After restart, Cursor should automatically initiate the OAuth flow:

  1. Look for authorization prompts
  2. Click “Authorize” when prompted
  3. Complete the HubSpot OAuth flow
  4. Grant permissions

4. Check MCP Status

In Cursor:

  • Check MCP server status in settings
  • Look for HubSpot MCP in the MCP servers list
  • Verify it shows as “connected” or “ready”

Alternative Configuration Formats

If the above doesn’t work, try these variations:

Option 1: With explicit transport type

"hubspot": {
  "url": "https://mcp.hubspot.com/",
  "transport": "http",
  "auth": {
    "type": "oauth",
    "clientId": "e151e63f-399c-4c64-b1b2-7616966f79f9",
    "clientSecret": "7dd6e6e2-7e91-4ba2-8123-7ca4e655bf06",
    "redirectUri": "https://www.brainforge.ai"
  }
}

Option 2: Using command format (like Linear)

"hubspot": {
  "command": "npx",
  "args": [
    "-y",
    "mcp-remote",
    "https://mcp.hubspot.com/"
  ],
  "env": {
    "HUBSPOT_MCP_CLIENT_ID": "e151e63f-399c-4c64-b1b2-7616966f79f9",
    "HUBSPOT_MCP_CLIENT_SECRET": "7dd6e6e2-7e91-4ba2-8123-7ca4e655bf06"
  }
}

Note: Option 2 may not support OAuth flow automatically - Option 1 is preferred.

Verification

Check Server Response

curl -I https://mcp.hubspot.com/

Expected: 401 Unauthorized (this is normal - means server is reachable)

Check Configuration File

cat ~/.cursor/mcp.json | python3 -m json.tool

Verify JSON is valid and HubSpot entry exists.

Common Issues

Issue: “No server info found”

  • Cause: Server not initialized or OAuth not completed
  • Fix: Restart Cursor, complete OAuth flow

Issue: “Authentication failed”

  • Cause: Invalid credentials or redirect URI mismatch
  • Fix: Verify credentials in 1Password, check redirect URI matches exactly

Issue: “Connection timeout”

  • Cause: Network issue or incorrect URL
  • Fix: Verify https://mcp.hubspot.com/ is accessible

Logs Location

Check Cursor MCP logs:

~/Library/Application Support/Cursor/logs/*/window*/exthost/anysphere.cursor-mcp

Look for:

  • Connection attempts
  • OAuth flow progress
  • Error messages

Next Steps

  1. ✅ Configuration updated to use "transport": "http"
  2. ⏳ Restart Cursor completely
  3. ⏳ Complete OAuth authorization when prompted
  4. ⏳ Test with: “Show me all deals for Inteleos”

References