Setup with your AI assistant

Set up Gem Logic in a conversation

Skip the setup forms. Connect the AI assistant you already use, tell it about your store in plain language, and it walks you through the whole setup: your company details, your first product, your first customer, your first sale. You approve every change before it is saved.

เริ่มทดลองใช้ฟรี 14 วัน จองการสาธิต

Works with the assistant you already use Your key, your limits You approve every change

Your AI assistant

Connected to your Gem Logic

Let's set up my store. We're called Aurora Fine Jewelry, on Fifth Avenue in New York.

Welcome! I saved your store name and address. Next: which TAX number should appear on your invoices?

Setup checklist1 OF 5 DONE

Company detailsSaved

First productNext

First customerTo do

First saleTo do

First invoiceTo do

Each answer is saved after you confirm it

One question at a time, in plain conversation.

Continue setup

How it works

Three steps, no forms

No import files to map, no settings screens to hunt through. The questions come to you, one at a time, and everything you answer lands in the right place.

STEP 1

Create your agent key

In Gem Logic, open Settings > AI agents and pick what your agent is allowed to do. A read-only assistant cannot change anything, and you decide exactly how far its reach goes. Gem Logic hands you the exact command to connect it.

STEP 2

Connect your assistant

Paste that one command into Claude Code, Cursor, Copilot or any assistant that speaks the Model Context Protocol. No code to write, no connector to build, no consultant on a plane.

STEP 3

Have the conversation

Your assistant checks what is still missing and asks you one question at a time. Each answer is saved as you confirm it, and the checklist fills up until your setup is done.

Works with

The assistant you already use

Gem Logic speaks the Model Context Protocol (MCP), the standard way modern AI assistants connect to the tools they work with. If yours supports MCP, it can set up Gem Logic for you.

Claude CodeClaude DesktopCursorGitHub Copilotand any other MCP-capable assistant

ความปลอดภัยและการควบคุม

คุณยังคงควบคุมทุกอย่าง

An assistant that works on your live system has to be one you can trust. Three rules keep it accountable.

Your key, your limits

An agent key only reaches what you allow. A read-only key never even sees a write operation: Gem Logic hides them from the assistant entirely. Narrow a key down or revoke it at any time, and its access ends on the spot.

You approve every change

Your assistant is told to read before it writes, to prefer searching over creating, and to confirm with you before saving anything. Setup is an interview, not a surprise.

Same rules as your team

Everything the agent does goes through the same API, permissions and logging as a click in the app. Nothing bypasses your roles, and every action is recorded.

For the technically curious

One command, the whole API

The agent key authenticates a hosted MCP endpoint on your own Gem Logic instance. Your assistant receives a live catalog of everything the key may do, the exact request and response shape of each operation, and curated guidance per module, so it never has to guess.

# shown in Settings > AI agents with your key filled in
claude mcp add --transport http \
  --header "X-API-Key: <your key>" \
  gemlogic https://your-instance.gem-logic.eu/mcp

Cursor, Copilot and Claude Desktop take the same endpoint and header in their MCP settings. And it is not just for setup: the same connection exposes the full REST API, so your assistant can keep helping long after your store is running.

Explore API & integrations →

สำรวจเพิ่มเติม