17 modules · 200+ tools for AI assistants · 18 walkthrough videos
The all-in-one, AI-first
operations platform.
Two ways in, one company underneath. Your team works in the screens. Anyone on the team can also open Claude or ChatGPT and work in the same company through 200+ tools, as themselves.
tracking_project_summaryUsed list_tasks · status=in_progress,blockedBurn is at 61 % of the month's plan with 9 days left. Two tasks are blocked on the checkout API, both Mark's. The Aurora phase-two proposal is due Friday and has no next step yet.
update_deal · Aurora Retail · Phase twoDone. It is on the account timeline and on your Friday.
comment_task · STORE-118, STORE-121Commented on both and mentioned Nina; she gets the DM from the Opelli Bot.
Watch it work
Every module, in about two minutes.
1:38
2:15
2:16
1:37Sessions
The same week, from both sides.
Each session is one of the walkthroughs, told twice: on the screens the team uses, and in the chat client somebody opened beside them. Every tool name is real.
From the sync note to the board.
generate_report · last 3 days · STOREEleven tasks moved, two shipped. Nina published the checkout copy page. 14 hours tracked. Nothing from Aurora yet.
get_wiki_page · Weekly sync 2026-09-04Used create_task × 4Four tasks: STORE-131 to STORE-134, linked to the note. Two are Mira's, one Nina's, one yours, all in sprint 12.
update_task · STORE-133 · priority P0, blocked_by STORE-118Done. Mira got the P0 message; the board shows the blocked chip.
A reply from Aurora Retail.
list_mail_queueOne message, forwarded this morning: "Re: Phase two scope", from Charles at Aurora Retail, with a reply from their CFO quoted underneath.
file_mail · Aurora RetailUsed read_entry_with_agentSummary: they accept the phase-two scope and want the loyalty page live before their October campaign. Next step proposed: send the revised proposal by Friday, which replaces the step you set yesterday. People: Charles (known), and a new name, Lucy Marsh, "our marketing lead".
update_deal · stage Proposal, next step acceptedUsed lookup_person · Lucy Marsh, Aurora RetailDeal moved. Lucy Marsh: one strong match on Aurora's own team page, marketing lead since 2024, with the source linked. Shall I add her as a contact with the buying role "champion"?
create_contactAdded, with where each field came from recorded on the contact.
The launch page, before October.
get_wiki_page · Aurora Loyalty · BriefUsed create_siteUsed write_site_files · index.html, styles.cssStaged as version 1, unpublished. Preview link attached. The copy comes from the brief's "What members get" section.
create_form · Aurora Loyalty sign-up · lead formUsed open_formUsed write_site_files · index.html · editVersion 2 staged. Submissions file a Lead-stage deal on Aurora Retail, matched by the sender's domain.
publish_site · version 2Live. The domain needs one DNS record on their side; the built-in address works now. I'll be able to tell you visits and sign-ups from tomorrow.
Approved hours become the invoice.
list_approvals · August · pendingTwo: Nina on Storefront Revamp (68 h) and Adam on Mobile Companion App (41 h). Everything else is approved.
list_time_entries · Nina Roth · August · STOREThree: 7.5 h on 12 Aug (checkout API), 6.5 h on 19 Aug, 8 h on 27 Aug (release). All billable, all on tasks.
api_request · POST /api/tracking/approvals/… · approve × 2Used api_request · POST /api/finance/invoices · from approved hoursBoth months are locked. Draft invoice created: 4 lines at the August rates, Czech document, QR payment code, due in 14 days. It is a draft; issuing it allocates the number, and I will only do that when you say so.
api_request · issue, sendIssued as 2026-091 and emailed to Aurora's billing address with the PDF and ISDOC inside. The send history shows it accepted.
What it will not do.
list_time_off · Octoberapi_request · GET /api/people/…/rates · refusedLucie is out 13 to 17 October and Adam on the 31st. Pay is outside what this key can read: this connection was made from a guest account, and cost rates are a separate grant that guests never hold.
update_initiative · Storefront Revamp · Launch · +7 daysMoved to 24 October. It is on the roadmap and in the activity log under your name.
One permission model for people and their assistants. Every action, a person's or an assistant's, lands in the audit log. Every model call is on the record.
Connect
One connector. Two chapters. Five minutes.
Add Opelli as a custom connector in Claude or ChatGPT, sign in, choose which modules the connection may touch. Any other MCP client takes the config Opelli prints for you.
Claude
Desktop and claude.ai, one connector that follows the account. Settings → Connectors → Add custom connector, then the consent screen lists the tools.
The Claude chapter →ChatGPT
Developer mode, Create, paste the address, choose OAuth, sign in. Actions that change something confirm each time.
The ChatGPT chapter →Any MCP client
A copy-paste config with a personal key, scoped to the modules you choose. It runs on your own computer, so it works against a private Opelli too.
The config file →The whole platform
17 modules, one page.
Every module with its screens, its walkthrough and a session beside it, from Projects to Signing, plus the permission model, the security posture and the AI layer under all of them.
See it on your own operations.
A short call on your projects and your month, with the assistant you already use connected to a copy of your company.
Thanks — we'll be in touch to find a time.






