Connect Claude, ChatGPT and desktop assistants

The Kognit connector lets a workspace owner give an assistant access to conversations, synced orders, enabled knowledge articles and recorded support metrics. Each connection has its own permissions, expiry and revoke control. Customer messages and documents remain untrusted content; they cannot grant an assistant additional permissions.

Connect a hosted assistant

1. Open Integrations → Claude, Cursor & ChatGPT (MCP) in Kognit.
2. Copy the hosted server URL and add it as a custom MCP connector in your assistant.
3. If prompted for OAuth client registration, choose automatic registration.
4. Sign in to Kognit as the workspace owner. Check the client name, return destination and requested permissions before choosing Allow connection.
5. Ask a question such as “List unresolved conversations” or “Find order #1042.”

Your assistant receives the workspace data it requests. Conversation transcripts and order details may include personal information, so connect only assistants you trust. Assistant availability and workspace policy can affect which connection options appear.

What the tools do

Read tools list conversations, read recent messages, look up synced orders, keyword-search enabled knowledge and report recorded metrics. Order results are cached store records, not a fresh carrier lookup. Ticket lists are paginated in document order. Metrics show scan coverage and return unknown values when a measurement cannot be established.

With actions:request access, an assistant can also create a reply proposal, refund review request, knowledge-document proposal or storefront AI-setting proposal. These requests appear in the connector's review queue for up to 24 hours.

• Replies and refunds: open the inbox, review the context, and use the normal send or refund workflow. Copying a proposal or marking it reviewed does not send or pay anything.
• Knowledge documents: review the full proposed text, then choose Publish this document.
• AI settings: review the proposed enable/disable state and reply threshold before choosing Apply these AI settings. Existing per-topic escalation rules are retained.

The connector never sends customer messages or executes refunds. A failed request is reported as a failure. It does not substitute demonstration data.

Desktop clients and Custom GPT Actions

Create a named desktop access token in the connector dialog. Copy it immediately: it is shown once, expires after 30 days, and cannot be retrieved later. Give each client a separate token. Enable proposals only if that client needs them.

The local bridge requires Node 22 or newer. From a verified source checkout, install its locked dependencies with npm ci --prefix mcp, set KOGNIT_API_KEY privately in your MCP client's environment, and run node mcp/bin/kognit-mcp.js.

For Custom GPT Actions, the OpenAPI schema is https://kognithq.com/openapi.json. Use a desktop connector token as Bearer authentication. The Actions endpoints enforce the same permissions, workspace boundary and owner-review rules as native MCP.

Revoke and retention

In the connector dialog, choose Revoke beside the connection. Revocation affects its access and refresh tokens immediately. Disabling the owner's account or removing workspace ownership also blocks access. A client's refresh-token reuse revokes that connection.

OAuth access tokens last up to one hour; connections and refresh tokens expire after 30 days. Pending authorization requests last 10 minutes and codes last one minute. Proposals expire after 24 hours. Audit records contain operation metadata, not message bodies or tokens, and expire after 90 days. Expired artifacts are cleaned periodically; access checks always enforce expiry even if cleanup is delayed.

The first release supports workspace owners. Teammate delegation and automatic payment or message execution are outside this connector's permissions.