GuidesAgent setup

Connect Bionic by LM Studio

Hosted Sell MCP setup and verification status for Bionic by LM Studio.

Bionic release notes describe MCP OAuth support, but its custom remote-server setup format has not been verified. If your version offers a custom remote MCP connection, enter the hosted URL and complete browser consent. Do not apply the classic LM Studio configuration file instructions to Bionic.

Hosted URL: https://sell.app/mcp.

Status: not_tested. Configuration supplied: UI guidance or limitation only. Local artifact validation checks examples; it does not establish a successful connection in the actual client. No actual-client pass is claimed.

Official setup source.

Complete browser consent for admin access across current and future accessible stores. Current membership and role still apply. With zero stores, read sellapp_get_workflow with {"id":"connect-store"} to create your first store. Call sellapp_list_stores, then sellapp_search_operations with {"query":"listProducts","limit":1} and sellapp_get_operation with {"operation":"listProducts"}. Use a returned store slug in this bounded sellapp_read call:

{
  "operation": "listProducts",
  "arguments": {
    "store": "launch-lab",
    "query": {
      "limit": 1,
      "page": 1
    }
  }
}

Inspect the returned API page. For a consequential action, discover its contract and call sellapp_write with a stable idempotency key. Present the prepared preview to the user; only after approval, repeat the identical arguments with the returned confirmation token. Ordinary writes execute immediately. An unknown outcome needs inspection before any retry.

Disconnect your own connection through MCP access, separately from CLI access. It remains available after leaving all stores.

For integration questions, call sellapp_search_docs with a query, then sellapp_get_doc with a returned path. Cite its URL. Continue long pages with next_offset and revision. These public documentation reads need no store and work through the CLI bridge too.

Troubleshoot

Registration or invalid-client errors need a compatible callback and DCR/CIMD implementation. Invalid scope is a client configuration error. Declined consent grants no access. Let the client refresh expired tokens; reconnect for a revoked grant. Permission failures require checking current membership and role. Transport failures require checking the HTTP URL and feature availability; a 404 means MCP is unavailable. API keys cannot authenticate to this endpoint.

See Use Sell MCP for pagination, retrieval coverage, errors, and confirmation rules. Full mode is available at https://sell.app/mcp?tool_mode=full. Refresh the client's cached tool list when switching or upgrading to runtime 3.1.0; modes share the same OAuth resource.

On this page