Integration

KnoCommerce integration

KnoCommerce (Kno) post-purchase survey platform for Shopify stores: list surveys with their questions, read survey responses (answers, customer, lifetime spend and orders) with cursor pagination and date filters, list benchmark questions, and subscribe a URL to new-response webhooks. API access depends on the Kno plan (a plan without it answers HTTP 422). The deprecated attribution and response-count routes are not exposed, and neither the order object attached to a response nor webhook URLs and signing secrets are returned. Authentication is OAuth 2.0 client credentials: create an API client in the Kno dashboard (Settings, API Access) and enter its client ID and secret; LiveContext requests a token for the SURVEYS, RESPONSES, QUESTIONS and WEBHOOKS scopes.

Connect KnoCommerce How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in KnoCommerce.Built from the 6 KnoCommerce tools below, on the connection you add once.

What you can do with KnoCommerce

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Webhook, 3 operations

create_webhookCreate webhookPOSTSubscribes an HTTPS URL to Kno events for real: Kno then sends response/create events (new survey responses) to it; 409 if that URL and topic exist. The signing secret is withheld, so deliveries cannot be verified.
delete_webhookDelete webhookDELETEPermanently deletes one webhook subscription (id from list_webhooks).
list_webhooksList webhooksGETLists the account's webhook subscriptions (id, topic, creation date). Use an id with delete_webhook.

Benchmark, 1 operation

list_benchmark_questionsList benchmark questionsGETLists the benchmark survey questions available to the account (id, label, title).

Response, 1 operation

list_responsesList responsesGETLists survey responses, newest first: answers, status dates, customer email, phone, lifetime spend and orders. Filter by surveyId (from list_surveys), questionId, status or dates; page with maxPageSize and nextPageToken.

Survey, 1 operation

list_surveysList surveysGETLists the account's surveys with title, status (live or draft), dates and their questions (id, label, type, values). Filter by creation dates, status or title search; paginate with page and pageSize (max 50).

Use KnoCommerce from Claude Code, Cursor or Codex

Connect KnoCommerce in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its KnoCommerce operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect KnoCommerce

Create your workspace
Sign up free. Nothing to install.
Connect KnoCommerce once
Add your KnoCommerce connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.