Connect Claude and ChatGPT
Connect Claude, ChatGPT or another AI assistant to your Eleo store. Ask about stock, sales and orders in plain language, and make changes that always wait for your confirmation.
What you can do
Eleo has a connector for AI assistants. Once it is connected, you can ask Claude or ChatGPT about your store in plain language. The assistant gets its answers from your live Eleo data:
- "Which products will run out of stock this week?"
- "How did sales this month compare with last month?"
- "List the orders still waiting to be fulfilled."
- "Which supplier have I spent the most with this quarter?"
- "Raise the price of Jollof Rice (large) to 4,500." (a change, so the assistant asks you to confirm first)
The connector uses the Model Context Protocol (MCP), the open standard Claude, ChatGPT and most other AI assistants use to connect to other apps. Any assistant that supports remote MCP servers with OAuth sign-in can use it.
Before you start
- Plan. The connector is included in the Professional plan. When you connect, you can only choose stores that are on Professional.
- Your role. The assistant acts as you. It can only see and change what your own role allows in that store, and never more.
- Several stores in one connection. You can connect any of your stores, across organisations, in one go. The assistant asks which store you mean when it isn't clear.
- Who can connect. Any member of a store can connect an assistant to it, and the assistant never gets more than that member's role allows. That includes an accountant you invite with the Accountant role: see Your accountant.
- An AI assistant that supports custom connectors. Claude and ChatGPT both support them. See each section below for the plans they need.
The connector URL is the same for everyone:
https://api.eleo.app/mcp/
You can also copy it in Eleo from Settings → Integrations → Connect AI assistant.
Connect Claude
You can add Eleo as a custom connector on every Claude plan. On the Free plan you can add one custom connector. Once connected, Eleo works in Claude on the web, in Claude Desktop and in the Claude mobile apps.
- 1
Open Connectors in Claude
On Free, Pro or Max, go to Customize → Connectors and click Add custom connector. On Team or Enterprise, an owner first adds Eleo under Organization settings → Connectors → Add → Custom → Web. Members then find Eleo, marked Custom, under Customize → Connectors and skip to step 3.
- 2
Paste the Eleo connector URL
Name it Eleo and paste
https://api.eleo.app/mcp/as the URL. Leave the advanced OAuth settings as they are. Eleo registers Claude automatically. Then click Add. - 3
Sign in to Eleo and approve
Click Connect. A window opens at eleo.app. Sign in if you need to, then choose the stores and permissions on the consent screen (see The consent screen) and click Allow.
- 4
Turn it on in a chat
In a new chat, open the tools menu and make sure Eleo is switched on. Then ask a question about your store.
Connect ChatGPT
ChatGPT runs custom connectors as plugins. Adding one works on the web only, and what ChatGPT allows depends on your plan:
- Business, Enterprise and Edu can read and make changes. On these plans, a workspace admin or owner may need to turn on developer mode, or add Eleo for the workspace, first.
- Pro can read data, but cannot make changes.
OpenAI changes these plans often. If you cannot find the option, check OpenAI's help article on MCP connectors.
- 1
Add a custom MCP server
Go to chatgpt.com/plugins, click + and choose Add custom MCP server. Name it Eleo, paste
https://api.eleo.app/mcp/as the URL and choose OAuth for authentication. Accept the warning about custom servers, then click Create as a plugin. - 2
Sign in to Eleo and approve
ChatGPT sends you to eleo.app. Sign in, choose the stores and permissions, and click Allow.
- 3
Use it in a chat
Install Eleo from your plugins, start a chat, and type
@Eleoto bring it in. Then ask a question about your store.
ChatGPT marks every tool call that changes data and asks you to approve it. Eleo then asks you to confirm the change again, so a change needs two clear yeses. Reading data does not need any approval.
The consent screen
Whichever assistant you use, connecting brings you to the same Eleo page at eleo.app. It asks you to make three choices:
- Where it can work. Your stores are listed under their organisation. Tick the stores you want, or tick an organisation to choose all of its stores. Once every store in an organisation is ticked, you can also switch on Include stores added later, so a store you open there later is covered without reconnecting. Stores that are not on Professional are folded away and cannot be picked.
- What it can do. Pick one of three options:
- View only (recommended, and the default). The assistant can read your data and can't change anything.
- View and change. The assistant can also make changes. Every change still needs your confirmation in the chat. Money areas, such as expenses and budgets, are listed so you can see they are included.
- Custom. Set each area, such as stock, orders or expenses, to Off, View or Change. Each section has a Set all shortcut.
- Allow or Deny. Click Allow to finish connecting. Click Deny to go back to the assistant without connecting.
The assistant never gets more than your own role allows in each store, whatever you pick here.
Your accountant
An accountant or bookkeeper who keeps the books for several businesses can connect their own assistant once and read every client's books from it.
As the store owner, invite them from Team → Add member with the Accountant role. The role reads the books and nothing else: the ledger, budgets and cash flow, expenses, payments, suppliers' invoices, the cash drawer, reports and your plan. It cannot see sales, orders, stock, customers or your team. It sees that payroll runs exist and how many people are on them, never what anyone is paid, and it never sees bank account numbers. It cannot change anything.
Inviting them is your consent. When they connect an assistant to your store, you get a notification naming the assistant and what it can view, and the connection shows under Active connections with their name and the Accountant role.
As the accountant, connect the assistant as above. The consent screen offers:
- All my clients. Ticks every client store you can connect. A client whose plan is not Professional is listed greyed out with "Ask the store to upgrade" and can't be ticked.
- Books (read-only). The books areas, view only. View and change is not offered when every store you picked is a client's.
Then ask, for example, "Give me a books overview for all my clients this month". The assistant reports each store on its own: whether the trial balance balances, the last journal posted, open or unreconciled cash shifts, approvals waiting and cash not yet reconciled. A client the connection can't reach is listed as refused, with the reason, rather than left out.
How changes are confirmed
The assistant never changes your store in a single step. When you ask for a change:
- The assistant asks Eleo for the change. Eleo changes nothing yet. It replies with a summary of exactly what will happen, for example "Set the price of Jollof Rice (large) from 4,000 to 4,500", and a one-time confirmation code.
- The assistant shows you that summary and asks whether to go ahead.
- Only when you say yes does the assistant send the same request again with the code. Eleo then makes the change.
The code is valid for 5 minutes, works once, and only for that exact change. If you wait longer, change your mind, or the assistant alters the request, nothing happens. Ask again when you are ready.
Some actions are never available through the connector, whatever permissions you grant. Do these in Eleo:
- Anything that moves money: payouts, transfers, wallet payments, shipping labels and refunds.
- Recording payments or payroll: marking expenses, bills or payroll as paid, payment plans, and drafting or approving payroll.
- Accounting entries: journal entries and changes to the chart of accounts.
- Till cash: opening or closing shifts, safe drops, bank deposits and cash movements.
- Messaging people: win-back campaigns to customers and notifications to staff.
- Running an automation on demand, changing anyone's role or access, permanent deletes, KYC, and your plan and billing.
Packaged workflows (Claude)
Eleo ships five everyday routines as ready-made prompts. In Claude you pick one instead of describing it; Claude then reads the right things in the right order, ends with a fixed summary, and offers at most a few tasks or one draft that you confirm. Nothing in a workflow moves money, closes a till or changes stock or prices on its own.
Where to find them:
- claude.ai and Claude Desktop. In a chat, click +, choose Connectors, then Eleo. The workflows are listed by name, and the same menu lets you attach a store's Daily brief, its Needs your attention list or its Chart of accounts as context for the conversation.
- Claude Code. Type
/mcp__eleo__morning_check_in(the slash menu also lists it as/eleo:morning_check_in). Arguments follow in order, separated by spaces, store first:/mcp__eleo__month_end_books Ikeja last_month. Attach the brief with@eleo:eleo://store/<store id>/brief. - ChatGPT shows neither prompts nor resources. Ask in your own words instead, for example "Run my morning check-in: sales so far, open orders, low stock and what needs me today." The assistant uses the same tools.
| Workflow | What it reads | What it offers |
| ----------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| Morning check-in (morning_check_in) | Yesterday's sales, what is waiting on you, open orders, low stock, who is on duty, today's tasks | Up to three tasks for what needs a person today |
| End-of-day close (end_of_day_close) | Today's sales, shift totals, takings by payment method, open orders, stock expiring tomorrow | One handoff task for whoever closes, naming the expected deposit. Shifts are closed and deposits recorded in Eleo, never by the assistant |
| Weekly stock review (weekly_stock_review) | Low, expiring and slow-moving stock, the demand forecast, counts in progress, the reorder plan | One draft purchase order per supplier you confirm. Submitting and approving stay in Eleo |
| Month-end books (month_end_books) | Profit and loss, balance sheet, bills due, payables, receivables, unapproved expenses, unmatched invoices, cash outlook | One task per unreconciled group for your bookkeeper. No entry is posted and nothing is paid |
| Supplier check (supplier_check) | Unpaid and overdue invoices, late deliveries, price changes, payables and spend per supplier | A task for each supplier to chase. No invoice is paid |
Each workflow takes an optional store and period. If your connection covers one store, it is used; if it covers several, Claude asks which one before reading anything.
A daily brief without opening Eleo
Eleo never pushes to an assistant; the assistant pulls. So a brief that arrives every morning is a scheduled task you set up in Claude or ChatGPT, running under your own connection. Each one uses the same prompt:
Call get_daily_brief for <store> and send me the summary; flag anything in the attention list.
- Claude Code routine. Run
/schedulein Claude Code and describe the task with the prompt above and the time you want it, or create the routine from the Claude Code web app. Routines run in the cloud at least an hour apart and need no permission prompts, so the brief arrives whether or not your computer is on. - Claude Desktop or Cowork scheduled task. Create a scheduled task, pick the time, paste the prompt and make sure the Eleo connector is enabled for it. A Cowork task can also attach the Daily brief resource instead of calling the tool.
- ChatGPT Scheduled Task. Start a chat with
@Eleo, ask ChatGPT to schedule the prompt above at a time of your choosing (at most one run per hour, and ChatGPT caps how many tasks you can keep active), and confirm. The brief arrives as a notification from that chat.
What arrives is the brief's summary: yesterday's sales, the headline metrics, the risks that need action and anything waiting on you. The schedule runs in your own timezone, while the brief's "today" and "yesterday" are the store's local days, so pick a time after the store's day has started. The task uses your own grant, so it sees only the store and permissions you approved, and it stops the moment you revoke the connection in Eleo.
Manage and revoke connections
Go to Settings → Integrations → Connect AI assistant in Eleo. Under Active connections you see every assistant connected to the store, who connected it and their role here, which stores it works in, the permissions it holds and when it was last used.
Click Disconnect from this store to remove one. It takes effect immediately for this store, and the assistant's next request here is refused. A connection that also covers other stores keeps working there, so disconnecting your accountant's assistant does not affect their other clients. To reconnect, go through the steps above again.
Removing someone from your team also removes your store from every connection they made, at once.
You can also remove the connector inside Claude or ChatGPT, but that only removes it from the assistant. To be sure the assistant has lost access, disconnect it in Eleo too.
Claude Code, Cursor and other local tools
Developer tools that support remote MCP servers with OAuth can use the same URL. In Claude Code, for example:
claude mcp add --transport http eleo https://api.eleo.app/mcp/
Then run /mcp in Claude Code and choose eleo to sign in.
Some tools cannot sign in with OAuth and ask for a token instead. For these, create an API key in Settings → Integrations → Connect AI assistant → Local clients (API keys) and send it as a bearer token. For example, in Cursor's mcp.json:
{
"mcpServers": {
"eleo": {
"url": "https://api.eleo.app/mcp/",
"headers": { "Authorization": "Bearer emk_your_key_here" }
}
}
}
An API key has your own permissions in that store, and it does not expire until you revoke it. Treat it like a password: never paste it into a chat or commit it to a code repository.
Troubleshooting
"None of your stores is on a plan that includes AI assistant connections." The connector is part of the Professional plan. Upgrade the store, or ask its owner to, then connect again.
The assistant says it does not have permission. The permission wasn't granted on the consent screen, or your role in the store doesn't allow the action. To grant more, disconnect it in Eleo and connect again. If the problem is your role, ask the store owner.
"Confirmation expired." More than 5 minutes passed between the preview and your yes. Ask the assistant to make the change again.
The sign-in window closes without connecting. Check that pop-ups are allowed for claude.ai or chatgpt.com, sign in to eleo.app in the same browser, and try again.
The assistant shows data from the wrong store. Tell it which store you mean. If that store isn't covered, disconnect it in Eleo and connect again, ticking the stores you need.
Your data
The assistant receives only what you ask it to look up, and only from the stores and permissions you approved. Once data reaches Claude, ChatGPT or another assistant, that provider's terms and privacy policy apply to it. Eleo never receives your chat history.
Every request an assistant makes in Eleo is recorded with your account and kept for 12 months. You can revoke access at any time. See AI assistants and connected apps in our privacy policy for what we keep and for how long.