Skip to main content
Question

Integration with Amazon Quick via MCP Connector

  • August 6, 2026
  • 0 replies
  • 18 views

We're connecting Bob MCP to Amazon Quick. The connection fails during the OAuth handshake before a Bob sign-in is reached. We'd like to confirm how the Bob MCP server expects clients to register/authenticate.

Environment

  • Client: Amazon Quick (enterprise) MCP connector
  • Server (streamable-HTTP): https://mcp.hibob.com/mcp/public

What was observed

  • The client's automatic OAuth mode (no credentials entered) fails before any Bob sign-in redirect appears.
  • The client's alternative mode requires a Client ID / Authorization URL / Token URL, which the  documented URL-only setup doesn't provide — so we cannot populate them.

Anyone any ideas here? It looks like an incompatibility between the parameters Quick is passing or expecting and those available/passed in HiBob.