MCP

MCP is a standard way for compatible AI clients to discover and call external tools. Your client and its model decide whether and when to call the tools available from a connected server.

Your client must support remote MCP servers over Streamable HTTP. To connect to seller tools, it must also support Kurodyne's OAuth flow, including Client ID Metadata Documents or Dynamic Client Registration, resource indicators, and S256 PKCE.

An AI client requests a set of permissions, all shown before you approve or deny the connection. Every request to connect seller tools includes “View your store”. A client can also request “Make changes”, “Identified sales”, and “Stay connected”; “Stay connected” only lets it renew access.

Yes, when you approve “Make changes”. Ordinary edits can run directly; destructive actions use separate prepare and confirm tool calls, while account settings and Stripe Connect onboarding or repair remain unavailable through MCP.

Kurodyne checks OAuth registration data, but it does not verify the company or application behind a client. Kurodyne does not verify client-provided names. Approve only connections you initiated, and check the requested permissions, return address, host, and port.