What each system does
The Edge is a point-of-sale and store-management system for independent jewelers, from Abbott Jewelry Systems. It runs on a machine in the store and holds the store’s inventory, customers, sales history, repairs and custom orders, and appraisals. It is where the store’s day actually happens.
Claude is the AI assistant from Anthropic. On its own it knows nothing about a particular store. It can be given connectors — over MCP, the Model Context Protocol — that let it look things up in a business’s systems while a person is asking questions.
What connects natively
Nothing, as far as we can find. As of August 2026 The Edge publishes no MCP connector and no public API intended for outside programs; its integrations are vendor-arranged. If that changes, the vendor’s own path would be worth evaluating first, and we will update this page.
What The Edge does have is an export. That is the hinge the whole connection turns on.
What a connection looks like in practice
This is the shape of the deployment that is in production today, since go-live.
-
The export. Once a night, a little after seven in the morning Eastern, The Edge’s read-only export runs on the store’s machine and lands, outbound over a private link, in a copy we host. The export has run every night since go-live. The POS is never exposed to the AI or to the app; both only ever see the copy.
-
The gateway. On the AI side there is one MCP gateway. Behind it, at this deployment, are seventeen tools. All seventeen are reads — past-due repairs, customer history, what sold, what’s aging in the case. One of them is a free-form query for the questions nobody anticipated, and it is forced read-only at the server, with a timeout and a row cap, so a clever question cannot become a slow one or a destructive one.
-
The people. The store runs three permission tiers — owner, manager, associate. Each person adds one connector to their own Claude and carries their own key. What they can ask is decided by the key, not by the phrasing: an associate’s list of tools is shorter, and topics the owner designates are filtered out before a question is even matched, so there is nothing to argue with and nothing to leak in a refusal.
-
The questions. “Which repairs are past their promised date?” “Who bought bridal last year and hasn’t been in since?” “What did this customer buy the last three times?” All reads. Nobody’s first question is “please change something.”
Limitations and honest caveats
- It is as current as last night. Anything that happened today is not there until tomorrow morning. If the question is about right now, this connection is the wrong tool.
- It cannot write. That is the design, and it is still the design. A store that wants writes would need a different path, and a decision to build one. Read-only first: why we sequence access this way →
- The export is what the export is. The Edge decides what its export contains. Fields it leaves out are not available to Claude, and we don’t reach around it.
- Someone runs the copy. The export job, the hosted copy, and the gateway are running services. At this deployment that someone is us.
- We don’t publish a speed figure. We haven’t measured how fast it answers.
Bigger picture
This page is the worked example for two broader questions that any owner-operated business runs into, not just jewelers: What is an MCP connector? → and How do I connect AI to on-premise software? →
Setup guide: Can my AI work with The Edge jewelry POS? →
Who this is for
An independent jeweler on The Edge who already pays for Claude (or is about to), wants to ask plain-language questions about their own store without building reports, and is comfortable with answers as of last night. If that is you, tell us about the store. Read-only first. Writing only when you say so.