For owners and their AI assistants · Beta
Connect your
AI assistant.
Connect an assistant to your company, explain how you work, and let it prepare your setup. Review the proposed changes in Oklyst before they are applied.
01 Start with your company
One browser sign-in. One company.
- 01
Sign up and create your company. You must be an active owner to authorize setup access.
- 02
Add the Oklyst connection in your AI app, or use the downloadable CLI below.
- 03
Sign in through the browser, choose your company and review the access request. Approve only the company you want the assistant to help.
- 04
Ask for a setup proposal. Open its review link, inspect each change and choose whether to apply it.
A connection belongs to one company and the owner who approved it. To work on another company, authorize a separate connection.
02 Choose your assistant
Choose how to connect.
MCP lets your AI app discover Oklyst’s tools after you authorize access. Use this remote server address:
https://oklyst.com/mcpCodex
Add the remote server from Codex MCP settings, or run:
codex mcp add oklyst --url https://oklyst.com/mcp --oauth-client-registration dcrComplete the browser authorization. If you are not prompted, start it explicitly:
codex mcp login oklyst --scopes mcp:setup --oauth-client-registration dcrClaude Code
claude mcp add --transport http oklyst https://oklyst.com/mcpStart a new Claude Code session, because a running session does not load servers added after it started. Run /mcp, select Oklyst and follow the browser sign-in. See Claude Code’s MCP instructions for client settings and troubleshooting.
Claude in the browser
In Claude’s connector settings, add a custom connector with the same server address and connect your account. Availability depends on your Claude plan and administrator settings. Follow Claude’s custom connector guide.
ChatGPT
Add Oklyst as a custom MCP app using the server address above, then complete browser authorization. Your plan and workspace administrator must allow custom MCP apps with the required tools. An interactive app connection is separate from an automatic workspace agent.
Your AI client must support remote HTTP MCP with browser OAuth and dynamic client registration. The connection requests mcp:setup; no database password or provider secret is needed.
03 Give it the context
Describe the work, then review the plan.
“Help me set up our company. We have Operations and Finance teams. Read the current setup, ask what you need to know, then propose the departments, purchasing forms, company guidance and my team with their WhatsApp numbers. Give me the review link before applying anything.”
| Tool | What it does |
|---|---|
get_setup_status | Reads your live setup checklist, the same one you see on Getting started, so the assistant knows what is done and what comes next. |
get_setup_context | Reads company configuration, people, roles, forms and guidance so the plan starts from what is already there. |
get_setup_schema | Explains the exact structure needed for custom forms and setup definitions. |
propose_setup | Prepares profile, department, purchasing, form and guidance changes, people with their WhatsApp numbers, roles, form access, going live and the background agent’s schedule, and returns an owner review link. |
get_agent_setup | Returns the background routine’s status, its exact instructions, a schedule to confirm with you and the steps only you can take. |
get_setup_proposal | Checks whether the owner applied or rejected a proposal. |
get_connection_guide | Returns the next owner steps for WhatsApp, Zoho, Stocklyst, people or routines. |
The assistant cannot apply its own proposal: people, access and going live change only when you apply them. It cannot approve purchases, connect a provider, make payments or receive routine credentials through this setup connection. It does not receive your transaction documents or provider credentials.
04 Prefer a terminal?
Download the Oklyst CLI.
A single file for Node.js 24 or later. No npm package installation, database connection or API key is required. These commands are for macOS and Linux.
curl --fail --proto "=https" https://oklyst.com/downloads/oklyst.mjs --output oklyst.mjs
node oklyst.mjs login
node oklyst.mjs status
node oklyst.mjs tools
node oklyst.mjs call get_setup_context
node oklyst.mjs call get_agent_setup
node oklyst.mjs call get_connection_guide '{"service":"whatsapp"}'The login command opens your browser. On a computer without automatic browser opening, use login --no-browser and open its address on the same computer. The CLI saves a private credential in ~/.config/oklyst/connection.json; never share that file.
status shows the saved connection’s expiry without displaying its token. tools checks live access. Tokens expire after at most 90 days; sign in again after expiry or revocation. logout revokes the connection before removing the local credential. If revocation fails, it keeps the credential so you can retry. You can also revoke access in Oklyst Settings → Agent.
05 Connect the wider workflow
Owners stay in control of connections.
- You enter your Meta app’s details on your company’s WhatsApp screen and press Connect Meta for me; Oklyst points Meta at your company itself. The assistant proposes your team’s numbers and reads the setup checklist to see whether a test message arrived. Read the WhatsApp setup guide.
- Zoho
- Provider sign-in and company selection require the owner’s browser. Accounting sending is still in controlled testing; assistant authorization does not enable sending.
- Stocklyst
- You can authorize Stocklyst separately in the same AI client, using
https://stocklyst.com/api/v1/mcp/stream. Follow the official Stocklyst connection guide, approve the intended workspace, then ask your assistant to work with the tools available from each connection. Each app keeps its own permissions. This does not enable automatic inventory or accounting sync between the apps. - Routines
- Your AI app owns its schedules. Ask your setup assistant to set up the background agent: it prepares the routine and proposes its schedule for your review. ChatGPT workspace agents have no schedule and need an eligible workspace with Workspace Agents and the API channel enabled; a normal ChatGPT chat or scheduled task cannot receive their triggers.
Recurring operational work uses a separate company agent connection that you approve in the browser. A setup grant is for planning and owner review; it is not a replacement for that routine connection.
06 Background work
Let your assistant set up the agent.
- 01
Ask your setup assistant: “Set up the Oklyst background agent.” It reads the routine instructions, a suggested schedule and your company agent connector address.
- 02
In the AI app that will run the routine, add the company agent connector and approve it in your browser. This is a separate grant from the setup connection.
- 03
The assistant creates the routine with that connector and schedule where your AI app allows it, as Claude Code does for Claude routines. Otherwise it gives you the values to paste.
- 04
Review the schedule proposal in Oklyst and apply it. Settings → Background agent then shows the connection, schedule and last run.
The routine checks for work at its scheduled times. Instant wake after each message is optional: enter the routine’s trigger URL and token yourself under Advanced settings, never in a chat. A ChatGPT workspace agent has no schedule, so it always needs this step, with a ChatGPT Admin → Access tokens credential scoped to Workspace Agents rather than an OpenAI Platform API key.
Receipt reading has a separate connector and settings in Settings → Receipt reading. It can use either provider, but account verification and an operating window from an Oklyst operator are required. Only the assigned receipt is released; the reader saves private suggestions for an owner to review.
Setup access, operational work and receipt reading are separate permissions. A setup connection never grants the other two. Provider availability, usage limits and charges depend on your account; Oklyst’s daily start limit is not a subscription allowance.
07 Manage access
Review, revoke, reconnect.
Open Settings → Agent to review your company’s connections and revoke one you no longer use. Revocation ends its access even if a client still has a saved token. An expired or revoked connection needs fresh browser authorization.
If you are asked to paste a database password, a Zoho secret or a WhatsApp access token into a chat, stop that setup step. Provider credentials belong in the appropriate owner connection screen.
For AI clients reading this page: start with machine-readable connection instructions, discover tools after authorization, and read each tool’s current schema before proposing a change.