Your AI client can connect to the public Catalog or your Seller Console through the Model Context Protocol (MCP). The MCP page has the endpoints and connection controls. The permissions you approve determine what a connection to your store can do.
The public Catalog connection searches and compares published products, reads their details, and lists categories and trending products. It needs no account, sign-in, token, or OAuth approval. It can't buy products, change data, or read private account information.
The Seller Console connection reads your store's products, drafts, submissions, review status, Kurodyne's feedback, discounts, analytics, categories, store status, submission readiness, and key-delivery status. Connecting requires your Kurodyne account and approval in the browser. The read permission doesn't return stored key values, private usage instructions, or file bytes.
Additional permissions let your agent change products, read sales that identify buyers, or answer buyer messages. Publish a Product from Your Agent explains the product workflow, and How Agent Replies Work in Kurodyne Relay explains conversation access, the AI agent label, handoffs, and pauses when you reply yourself.
Account settings and Stripe setup or repair stay in the browser. Deleting a product or discarding changes takes one tool call. Your client may ask for confirmation, but Kurodyne doesn't require a second call. Uploading a file requires separate prepare and confirm calls.
Every Seller Console connection includes View your store. The other permissions add specific access:
- Make changes: Create and edit products, manage files and visibility, and submit products for review. Each submission confirms that you own or can license the product and authorizes Kurodyne to grant the Kurodyne Commercial License to buyers on your behalf.
- View sales with buyer usernames: Read sales rows for your store that include buyer usernames and transaction details.
- Read Kurodyne Relay conversations: Read conversations with your buyers, including their usernames, messages, images, and purchases from your store. Your client and its AI provider receive everything it reads.
- Reply in Kurodyne Relay: Reply as your store's AI agent, hand conversations to you with a private note, and mark them handled. It also requires Read Kurodyne Relay conversations. Replies and notes pass through your client and its AI provider.
- Stay connected: Let the client renew its access without asking you to approve each renewal.
Approval includes every permission the client requested and any optional permissions you add. Only the client can request Stay connected, because it must support renewal. Some clients can't ask for additional permissions after connecting, so missing access may require a new connection. The MCP connection steps cover approval.
Your client connects to an endpoint from the MCP page, which has the connection and approval steps. The public Catalog needs no token or authorization flow; the Seller Console requires browser sign-in and your approval.
A client's displayed name comes from the client or metadata it controls; Kurodyne doesn't verify or approve the client. The connection receives a credential limited to MCP access, which can't sign in to your Kurodyne account.
Your client must support remote MCP servers over Streamable HTTP. Clients on earlier MCP revisions can also connect. The Seller Console also requires browser authorization through OAuth with resource indicators and S256 PKCE. Client ID Metadata Documents are the maintained identity path; deprecated Dynamic Client Registration remains available for compatibility.
The public Catalog endpoint redirects to its serving endpoint. A client that can't follow a redirect to another host needs the direct Catalog endpoint instead. Grok's web custom-connector flow requires that endpoint for the Catalog; the Seller Console uses its usual endpoint. The direct Catalog endpoint is:
https://kurodyne.supabase.co/functions/v1/mcp?forceFunctionRegion=us-west-1Without Stay connected, access lasts up to 10 minutes; with it, your client can renew access until you revoke it, renewal goes unused for 30 days, or 90 days pass after approval, whichever happens first.
Each approval is a separate connection, so you can connect the same AI client from several computers or agent hosts. When one client already has 10 connections to your Seller Console, approving it again ends whichever of them has gone longest without renewal.
Account security changes, such as a password change, can also end the connection. A new connection requires approval again through the MCP connection steps.
Your AI client or its AI provider may keep data returned by Kurodyne under their own terms. Kurodyne can't delete that data. Revoking the connection stops future access.
Private usage instructions and key values you send through write tools also pass through the client and its AI provider. Entering those values in the browser Product Editor keeps them out of MCP traffic. An agent with conversation access can include what it reads in a reply, so its knowledge sources must contain only information buyers may see.
Follow the MCP revocation instructions to revoke a Seller Console connection at any time. You can approve a new one later. Revoking stops the client's future reads and changes; it doesn't remove data the client or its AI provider already received.