MCP
AI operations through a persistent MCP connection.
MCP is a long-lived operating surface for catalogs, campaign drafts, verification, request logs, and sandbox activity. It is not a one-time setup shortcut.
Connected AI assistants can keep managing product catalogs, campaign drafts, verification, request logs, and sandbox activity through MCP.
Two different credentials
A long-lived KNOBASE_API_KEY lets an AI service call POST /v1/offers/decide. A user or workspace MCP authorization lets a connected assistant return later and continue catalog and campaign work. Do not treat them as the same secret.
What connected AI can manage
Typical work includes product imports, catalog cleanup, campaign drafts, sandbox analytics, request logs, and verification runs. This page does not claim named provider integrations unless they are actually available in the product.
Scopes and audit
Keep MCP access scoped. Review request logs and verification runs in the workspace. Security-sensitive implementation details are not published here.
Questions
- Is MCP just a faster setup?
- No. MCP is a persistent operating surface so connected AI can keep working on the same workspace.