Give your AI assistant permission-aware commerce context
Connect an MCP-compatible assistant to live Colab Commerce data through one secure, read-only endpoint. Users see exactly what their existing account permissions allow.
TRANSPORT
Streamable HTTP
ACCESS
Read-only tools
AUTHORIZATION
User policy scopes
AUTHENTICATION
X-Api-Key
Built for controlled access
Useful context without handing over control
The MCP server turns Colab Commerce resources into tools an assistant can understand, while keeping authentication and authorization at the boundary of every request.
Commerce context on demand
Let assistants retrieve leads, activities, products, retailers, locations, territories, invoices, and other operational records.
Existing permissions apply
Every request uses the same policy scopes and record-level authorization as the Colab Commerce application.
Read-only by design
The MCP exposes list and get tools only. Connected assistants cannot create, update, or delete Colab Commerce data.
Structured, auditable retrieval
Tools return the same structured resource data as the API, making answers easier to verify against source records.
Work with live data
Ask operational questions in natural language
Once connected, your assistant can choose the appropriate Colab Commerce tools and retrieve records on your behalf.
- Summarize a lead and its recorded activity before a sales call.
- Find products and nearby retailer locations while helping a customer.
- Review pipeline records without exporting data into another system.
- Give internal assistants current business context within existing access rules.
Add Colab Commerce to your assistant
Follow the setup guide to configure the endpoint, API key, and required HTTP headers in an MCP-compatible client.