Taokeh
Contabilidad y nómina para pymes malasias. Tu IA lee los libros y archiva borradores que apruebas en la aplicación; nada se publica por sí solo.
Documentación
The Taokeh MCP server
Taokeh runs an official Model Context Protocol server. Connect Claude, ChatGPT or any MCP-capable client to a Taokeh company and it can read the live books — sales, cash, aging, stock, statements — and file drafts a human approves. Live since 16 July 2026, 95 tools. The design goal is stated plainly: the AI runs the books, and the human approves on one page — every write tool here files a draft that waits on /go for a tap.
Endpoint
https://taokeh.my/mcp
Transport
Streamable HTTP (MCP)
Tools
95 — 46 read, 49 write (drafts only). A personal access token can be scoped at mint to chosen tool groups; a scoped connection lists only those tools and is told its own count at initialize. OAuth connections always list the full set.
Auth
OAuth 2.1 with dynamic client registration and PKCE, or a personal access token as a bearer
Tested clients
claude.ai · ChatGPT custom connectors · Claude Desktop · Claude Code · Cursor
Price
RM29/month add-on, included in the 14-day free trial
The first Malaysian-built accounting AI connector we are aware of (as of July 2026).
Connecting
claude.ai and ChatGPT. Add https://taokeh.my/mcp as a custom connector. The client registers itself, you are bounced to Taokeh to log in, and a consent screen names the company and the scope before anything is granted. No key to copy, no config file to edit. On ChatGPT that means adding a custom MCP server under Plugins — the steps are at Connect ChatGPT to your accounting books.
One connector per company. Every company also answers at its own address, https://taokeh.my/mcp/<company-slug> (the exact URL is on Integrations → Ask Taokeh connector). Use it when you keep books for more than one company: claude.ai and ChatGPT allow a single connector per address, so a second company added on the shared URL is refused as a duplicate. The address is a distinct URL and nothing more — it carries no access, the shared endpoint keeps working, existing connections are untouched, and which set of books opens is still decided by the sign-in you approve at consent.
Claude Desktop, Claude Code, Cursor and other CLI clients. Generate a personal access token inside Taokeh (they look like tkm_…) and send it as Authorization: Bearer <token>. Tokens are stored only as a hash, are scoped to one company, and can be revoked at any time.
The config, ready to paste. Claude Code can add the server directly — claude mcp add --transport http taokeh https://taokeh.my/mcp — and walk the same OAuth consent as the web clients, no token to manage. For a client that wants a config file and a personal access token instead:
{
"mcpServers": {
"taokeh": {
"command": "npx",
"args": ["mcp-remote", "https://taokeh.my/mcp", "--header", "Authorization:${AUTH_HEADER}"],
"env": { "AUTH_HEADER": "Bearer tkm_your_token_here" }
}
}
}
Two things worth knowing, written down here rather than discovered: the header argument has no space after the colon (Authorization:${AUTH_HEADER}) — a space splits the argument and the server answers 401 — which is why the value is passed through env rather than inline; and the token is a personal access token you mint inside Taokeh, so it carries one company and can be revoked without touching this file.
Both routes need the Ask Taokeh connector add-on switched on for the company. The tenant-facing setup walkthrough lives on the Ask Taokeh connector page.
The safety contract
This is a design decision, not a limitation we are working around. An AI connected to a business’s books must not be able to change them.
Reads are free
Every read tool answers immediately. Ask for the aging, the cash position, last month’s P&L or a product’s stock and the answer comes straight from the ledger — no approval step, because a read changes nothing.
Writes are drafts
Every write tool files a pending draft. It appears in Taokeh for the owner to check against the original document, and only the human tap posts it. Drafts now cover the daily loop: sales documents, purchases, money in and out, journals, fixed assets, payroll runs and leave, corrections to records already posted, and staging a switch from another system. The full list is in the table below.
Nothing changes without your approval
No tool posts to the ledger, changes or voids a posted document, deletes anything, confirms a bank row or sends an email by itself. Your AI can propose a correction to a record already posted; it waits as a draft showing the current record against the proposed one until a person approves it. Bank statement rows import into a review queue; classification suggestions are proposals the owner sees, not decisions.
Your AI does the processing — ours never does
On MCP paths the Taokeh server never calls a language model. Your assistant reads the receipt, reads the statement, reads the name card, and sends structured fields; our server validates them, re-computes the arithmetic, and files a draft. That means the reasoning runs on your own AI subscription with your own choice of model, and your documents are not fanned out to a third model we picked for you. We do the books. Your AI does the reading.
The 95 tools
Names and behaviour as registered by the server. 46 read tools:
| Tool | What it returns |
|---|---|
| Overview & cash | |
business_snapshot | One-glance health check: today’s and this month’s sales and expenses so far. |
daily_brief | The morning brief in one call — sales, cash, top debtors, pending approvals (the count is of DECISIONS, not rows — a real approval queue contributes its item count, an operational to-do counts as 1 however long its backlog), tax, low stock. |
cash_position | Every bank account and cash pocket with its current GL balance, plus the liquid total. An owner advance, and anything owed on a credit card, are reported separately as liabilities — never as cash. |
cash_forecast | A forward 8-week cash-flow forecast built from open invoices, open bills, payroll, statutory remittances, loans and SST — with every assumption listed. |
profit_drivers | Why net profit moved: a revenue/COGS/opex bridge against the same day-span of the previous month, with one-offs pulled out. |
| Statements & tax | |
income_statement | Profit and loss for a period: revenue, COGS, gross profit, expenses, net income — optionally against a comparison period, with every variance computed on the server. |
balance_sheet | Balance sheet as of a date: assets, liabilities, equity, with the balanced check — optionally against a second date, with the movement computed on the server. |
financial_timeseries | A month-by-month series across a window you name (up to 36 months, one call): revenue, COGS, gross profit, opex, net income, closing cash, AR, AP and net cash movement. An unfinished month is flagged partial; months before the accounting start date are absent, not zero. |
tax_position | Current SST period payable (if registered) plus e-invoice consolidation status and the filing due date. |
trial_balance | Trial balance as of a date: every account with a posting, its debit or credit, and whether the two columns agree. |
general_ledger | General ledger for a date range, every account or one: opening balance, each posting with its running balance, and closing. Capped rows; the balances stay exact. |
asset_register | The Fixed Assets register: every asset with its cost, depreciation to date and book value, the purchases waiting to be registered, and the months depreciation has not been run for. |
loan_register | The Financing register: every loan with its outstanding and its instalments. |
| Who owes whom | |
ar_aging | Who owes you money and how overdue — accounts-receivable aging by customer. |
ap_aging | Whom you owe and how overdue — accounts-payable aging by supplier. |
open_invoices | The unpaid or part-paid invoices for one customer, oldest first. |
customer_statement | One customer’s or supplier’s statement of account, line for line as the statement PDF prints it, with the running balance and the total outstanding. |
working_capital | Working capital in DAYS, month by month, plus who is slow to pay: debtor days, creditor days, inventory days and the cash-conversion cycle, each stating the balance, the flow and the day count it was computed from — and the amount-weighted average days-to-pay per customer and per supplier. A ratio with no base comes back null, not zero; inventory days is withheld unless the company runs perpetual costing. Figures only, no verdicts. |
payer_history | How this company has categorised a given bank counterparty before — the tenant’s own precedent behind a suggestion. |
| Sales, stock & channels | |
sales_summary | How much you have sold — today and month-to-date, or a date range broken down by month, customer and product. |
expenses_summary | How much you have spent: paid expenses today and this month so far. |
channel_summary | Sales by channel (Shopee, TikTok Shop, Shopify, your storefront) with discounts, shipping, freight-out, marketplace fees, returns and net proceeds. |
stock_level | Units on hand right now for a product, by name or SKU. |
stock_movements | The stock movement ledger in bulk, across products — what moved, when, why, the signed quantity, the balance it left behind and the document behind it. Says which stock mode the company is in, because on periodic stock (older companies; new ones start perpetual) selling does not move stock at all. |
low_stock | The reorder list: products at or below their reorder point. |
counter_day | A Counter (Kaunter) till day: receipt and voided counts, cash and DuitNow QR totals, the 5-sen rounding, whether the day is still open or closed into the books, and the receipt-number range. Counter add-on only. |
| Documents & search | |
search_documents | Find invoices, credit notes, quotes, delivery orders, bills, debit notes and purchase orders by number, party, date, amount or type. Ask for docType “payment” — opt-in, never part of “all” — and it returns the money instead: one row per bank line, with the invoices or bills it settled, where the payment came from, and refunds as negative allocations against the credit note they walk back. A set-off (contra) moves no bank money — Taokeh books it as two internal clearing lines, excluded here on purpose; see the ledger or the contra note. |
search_document_lines | Read the LINE ITEMS of invoices, credit notes, sell-side debit notes, bills, buy-side debit notes, quotes and delivery orders in bulk: product, description, quantity, unit, price, cost basis, discount, line total and the document’s own currency, across many documents in one call instead of one PDF at a time. Sizes and grades live in the name and description text, so the AI does the grouping. |
search_expenses | Search paid expenses already posted to the ledger — the duplicate check before filing an expense draft. |
search_journal | Search the ledger’s journal entries — every posting, whatever door created it (manual journal, scan, invoice, bank, expense, payroll) — each returned WITH its balanced lines, so you can see exactly how something was booked. |
get_document_pdf | A short-lived signed link to the real PDF of an invoice, quote, credit note, payment voucher or customer or supplier statement. It emails nobody; it hands you the link. |
get_attachment | A short-lived signed link to the ORIGINAL document someone filed — the receipt behind a posted expense, the scan on an invoice, bill or quote, the file riding a pending draft, or a Shoebox photo nobody has read yet. Taokeh serves the bytes; your own AI reads them. |
shoebox_items | The photos waiting in the Shoebox — paper the people in the business snapped on their phones and sent in, which nobody has read yet. Look at one with get_attachment, then file it by passing shoeboxItemId to a draft tool; Taokeh attaches its own stored copy, so the image is never re-sent. No AI credits are drawn on this lane. |
| Banking review | |
bank_review_queue | The imported bank register, in any status — defaulting to the rows still awaiting review, each with Taokeh’s own suggested category, confidence score and reason, lowest confidence first. Ask for confirmed, posted, ignored or all rows, or a date window across every statement, and settled rows come back with what was actually decided (category, ledger account, contact, splits, the invoices or bills settled) instead of a fresh guess. Hand-recorded settlements are never here. |
bank_reconciliation_status | Where each bank account stands: GL balance against the latest statement close, row counts by status, and the unreviewed backlog. |
bank_reconciliation_report | The audit bank reconciliation for one account, as the report page shows it: statement balance, unpresented payments, deposits not yet credited, statement lines not in the books, the balance per books and any unexplained difference — plus the entries still to tick off, the statement lines they can pair with, and the page’s own hints (a pair that cancels, a cash sale with no deposit, a missing opening balance). |
| Your own queue | |
my_work | What your AI filed and what happened to it: everything still waiting on the owner’s approval (with how long it has waited and the exact next step), what the owner approved and what it became, what was rejected and — where Taokeh stores one — the reason, and the migration sets still at a commit door. |
| Payroll | |
payroll_summary | A month’s payroll gross to net, as it was actually run: gross, every employee deduction (EPF/SOCSO/EIS/SKBBK/PCB/zakat), every employer contribution (EPF/SOCSO/EIS/HRD Corp), net pay and the employer’s true total cost — optionally per employee — plus who is on approved leave in the next 14 days, and, if you ask for it, the staff roster — which is where the employeeId for update_employee_draft comes from. Summed from the stored payslips, never recalculated. Admin and Bookkeeper + payroll roles only. |
employer_cost_estimate | What a hypothetical hire really costs: monthly wage plus employer EPF/SOCSO/EIS/HRD Corp, and the employee’s take-home after their own deductions — PCB from Taokeh’s implementation of LHDN’s official computerised MTD method. Every assumption is stated, so a scenario can never be read as a quote. Admin and Bookkeeper + payroll roles only. |
leave_register | Leave for a year, per employee: what each leave type allows and has left, the applications still waiting for a decision, and the leave already approved, recorded or decided. No pay figures. Admin and Bookkeeper + payroll roles only. |
| Lookups & shaping | |
resolve_customer | Match a customer name against the real customer list — resolved, ambiguous or none, with current outstanding A/R. Never guesses. |
resolve_vendor | Match a supplier name against the real vendor list. Near-misses are flagged rather than guessed. |
resolve_product | Match a product by name or SKU and return its unit and default sell price. |
expense_accounts | The expense categories and paid-from accounts this company can actually post to. |
intake_contract | The exact shape a Taokeh draft needs — required fields, totals, measurement and SST rules, and a worked example grounded in this company. |
find_in_taokeh | Where in Taokeh to do something: the real deep-link page(s) for a plain-language question, from the live feature catalogue. Guides only; changes nothing. |
49 write tools — every one of them files a draft or a suggestion, never a posted entry:
| Tool | What it files |
|---|---|
create_expense_draft | File a paid-expense draft from a receipt, with the original image attached — or pass shoeboxItemId and Taokeh attaches the Shoebox photo it already holds. Does not post. |
create_bill_draft | File a supplier-bill draft (inventory lines), optionally from a Shoebox photo via shoeboxItemId. Does not post, receive stock or move cost. |
create_invoice_draft | File a sales-invoice draft, optionally from a Shoebox photo via shoeboxItemId. Does not post or move stock; the server re-computes every line and total. |
create_quote_draft | File a quotation draft — an estimate, never a ledger entry. |
create_credit_note_draft | File a credit-note draft — a sales return, short delivery, price correction or allowance. Against a specific invoice, or as a standalone allowance. Does not post, and whether stock comes back is the owner’s decision at approval. |
create_debit_note_draft | File a sell-side debit-note draft — an additional charge on an invoice you already issued (an undercharge, a price revised upward, a missed surcharge). The original invoice is required; it posts nothing, and it never moves stock. |
create_purchase_order_draft | File a purchase-order draft — an order you intend to place with a supplier. It posts nothing and moves no stock; convert the order to a bill when the goods arrive. |
create_journal_draft | File an adjusting-journal draft — an accrual, a prepayment, a correction, a year-end adjustment, or the reversing entry that fixes a wrong posted entry. It must balance to the sen; it posts nothing, and posted history is never edited or deleted. |
create_receipt_draft | File a customer-payment draft, allocated across open invoices. Nothing settles until approved. |
create_payment_draft | File a supplier-payment draft, allocated across open bills. Ringgit only, never on a credit card, and nothing is paid or posted until the owner approves — at which point payables and the bank move exactly as a Banking match would. |
create_contact_draft | File a contact draft read off a business card. The card image is required so the owner can check your fields against the picture. |
update_contact_draft | Propose changes to a customer or vendor already on the books — tax id, e-Invoice details, phone, flags, and the people filed under them. The owner approves a plain current-to-proposed diff; nothing changes until they do. |
update_invoice_draft | Propose a correction to an invoice already posted — a wrong line, a wrong date, the wrong payment method. An admin approves a plain current-to-proposed diff; nothing changes until they do, and the correction keeps the same invoice number and carries the original document across. It can never change the customer, the invoice number, or an invoice LHDN has already validated. |
update_bill_draft | Propose a correction to a supplier bill already posted: a wrong line, quantity or cost, or a wrong date, term or payment method. It can change, add or remove lines on a bill received against a purchase order. Lines it keeps stay matched to what was received, and a removed line's quantity goes back on the order. An admin approves a plain current-to-proposed diff, and nothing changes until they do. The bill keeps its number, its original document and its link to the purchase order. The supplier, bill number and currency can never change, and a bill with a payment or a debit note against it is refused. Admin-only. |
update_quote_draft | Propose a correction to a quote that is still open: a wrong price or quantity, a missing line, or the date, validity, term or notes. The owner or bookkeeper approves a plain current-to-proposed diff, and nothing changes until they do. The quote keeps its number, and lines that are already right stay exactly as they are. The customer, quote number and currency can never change. |
update_delivery_order_draft | Propose a correction to a delivery order not yet invoiced: a wrong quantity or price, a missing line, or the date or notes. The owner or bookkeeper approves a plain current-to-proposed diff, and nothing changes until they do. The delivery order keeps its number, moves no stock and posts nothing. The customer, number and currency can never change. |
update_purchase_order_draft | Propose a correction to a purchase order not yet converted into a bill: a wrong quantity or cost, a missing line, or the date, term or notes. The owner or bookkeeper approves a plain current-to-proposed diff, and nothing changes until they do. The order keeps its number and status and posts nothing. The supplier, number and currency can never change. |
update_credit_note_draft | Propose a correction to a credit note already posted: a wrong line, quantity, price, date or reason. An admin approves a plain current-to-proposed diff and says, line by line, whether the goods came back into stock. Nothing changes until they do. The note keeps its number, the invoice it credits and its attachments. It can never change the customer, move the note to another invoice, or touch a note already on MyInvois. Admin-only. |
update_supplier_debit_note_draft | Propose a correction to a debit note raised against a supplier’s bill (a purchase return): a wrong line, quantity, cost, date or reason. An admin approves a plain current-to-proposed diff and says, line by line, whether the goods went back to the supplier. Nothing changes until they do. The note keeps its number, its bill and its attachments, and the supplier and bill can never change. Admin-only. |
update_expense_draft | Propose a correction to a paid expense already posted: the date, amount, input SST, category, paid-from account, payee or reference. The owner or bookkeeper approves a plain current-to-proposed diff, and nothing changes until they do. Anything you leave out stays as it is, and the entry’s receipt carries across. |
update_employee_draft | Propose corrections to an employee already on payroll — IC, EPF/SOCSO/tax numbers, salary, the statutory flags. An admin or a Bookkeeper + payroll login approves a plain current-to-proposed diff; nothing changes until they do, and an approved change applies to future payroll runs only. Admin and Bookkeeper + payroll roles only. |
update_product_draft | Propose changes to a product already in the catalogue — name, unit, selling price, reorder point, barcode, category. The owner approves a plain current-to-proposed diff; nothing changes until they do. It can never move stock on hand or restate a cost. |
update_logo_draft | Propose a new company logo — the mark Taokeh prints on every invoice, quote and receipt it generates. Send a PNG or JPEG; oversized artwork is shrunk for you rather than refused. An admin approves it looking at the logo they have now beside the one proposed; nothing changes until they do. It is one value, so a second proposal replaces the first. Admin-only. |
create_recurring_invoice_draft | Propose a recurring invoice — a billing schedule that issues the same invoice to a customer every month, quarter or year. It creates nothing; the owner approves it, and the review page states the date the FIRST invoice would go out. A schedule filed this way always files a draft invoice each cycle for a person to approve — it can never be set to post by itself. |
update_recurring_invoice_draft | Propose changes to a recurring invoice already set up — a price rise across a subscription, a new end date, or pausing the billing. The owner approves a plain current-to-proposed diff, and the review page states the date the next invoice would go out and whether approving moves it. Invoices the schedule has already issued are never touched, and it can never end a schedule or switch it to posting unattended. |
revise_draft | Correct a draft you already filed — amend a PENDING draft of any kind in place instead of re-filing it (which the duplicate guard refuses). Revising never approves: the draft stays pending and the owner still taps. |
import_bank_statement | Import a bank or credit-card statement for reconciliation. Every row lands in Banking → Review; the server refuses a statement whose rows do not tie to the printed closing balance, and a card statement must declare which sign convention it was read in. |
create_bank_clearing_draft | Propose which book entries have cleared the bank — each paired with its statement line or given its cleared date — for the reconciliation’s tick-off step. Nothing is ticked until an admin or bookkeeper approves; approving ticks them exactly as the page’s Save does. |
create_payment_match_draft | Propose which open invoices or bills one posted customer or supplier payment settles. Only the documents Banking → Match offers that payment; nothing is allocated until an admin or bookkeeper approves, and approving applies it exactly as Match does. |
create_asset_draft | File a draft putting a purchase already in the books on the asset register, from the waiting list. It posts nothing, and nothing is saved until an admin or bookkeeper approves. |
create_asset_disposal_draft | File an asset disposal draft: depreciation brought up to date, the asset cleared and the gain or loss booked, exactly as Dispose does, once an admin or bookkeeper approves. |
create_depreciation_draft | File a depreciation run draft through a date: one entry for each month not yet posted, exactly as Run depreciation does, once an admin or bookkeeper approves. |
create_payroll_run_draft | File a payroll run draft for a month: a new run, or allowances, overtime, bonus, unpaid days and other deductions set on the month’s draft run, with every payslip figure shown before approval. An admin or a payroll login approves it; the run stays a draft, nobody is paid and nothing is filed. Admin and Bookkeeper + payroll roles only. |
create_leave_draft | File a draft recording leave on an employee’s behalf, with the days counted and the balance left. Once an admin or a payroll login approves, it is recorded exactly as Record leave does. Admin and Bookkeeper + payroll roles only. |
create_leave_void_draft | File a draft voiding leave an admin recorded, so it can be recorded again correctly. Once an admin or a payroll login approves, the days go back into the balance. Admin and Bookkeeper + payroll roles only. |
create_quote_conversion_draft | File a draft converting a whole open quote into an invoice or a delivery order, with the document it becomes shown before approval. Once an admin or bookkeeper approves, it converts exactly as the quote page does. |
create_delivery_order_invoice_draft | File a draft turning one customer’s open delivery orders into one invoice, with the invoice and its journal lines shown before approval. Once an admin or bookkeeper approves, it is invoiced exactly as the Delivery orders page does. |
create_customer_refund_draft | File a draft recording a refund already paid to a customer, on the money-out bank line it went out on, against a credit note or an overpaid invoice. It never pays anything; once an admin or bookkeeper approves, it is recorded exactly as the Refund page does. |
create_supplier_refund_draft | File a draft recording a refund a supplier already paid back, on the money-in bank line it came in on, against a debit note or an overpaid bill. Once an admin or bookkeeper approves, it is recorded exactly as the Refund page does. |
create_contra_draft | File a contra set-off draft between a customer and a supplier that are the same business, settling one side in full. An admin or bookkeeper checks the two side by side and approves it on its review page. |
create_bank_account_draft | File a draft adding a bank account or credit card to Banking, with no opening balance. A name or account number already in Banking is refused. Once an admin or bookkeeper approves, it is added exactly as the Banking form does. |
draft_bank_classification | Propose categories — and, where the owner picks the account by hand, the ledger account too — for up to 50 bank rows. Written as an “AI suggestion” badge the owner sees, pre-selecting their dropdowns; it never confirms and never posts. On a customer or supplier payment it can also propose WHICH invoices or bills the money settles: the amounts must add up to the whole line, and the proposal only pre-fills the owner’s Match pane for them to read and save. |
request_attachment_upload | A one-time upload link for a file too large to inline, returning a token any draft tool accepts. |
stage_document | Bring one already-issued historical invoice or supplier bill across from the system you are migrating from. Groups into monthly batches the owner approves together; idempotent on the old system’s own document id, so re-running your export never double-books. Attach the original (request_attachment_upload → PUT → attachmentToken) and it rides the staged row onto the posted document. |
stage_opening_balances | Bring a whole set of opening balances across when switching accounting system — the closing trial balance, the aged receivables or the aged payables. The owner reviews it on the Switch wizard’s own screens and posts it; re-staging replaces the set, because a balance set only means anything whole. |
stage_master_data | Bring the chart of accounts, the product catalogue, the customer/supplier book or the staff list across when switching accounting system. The owner confirms it on the screen that already shows that list and applies it; re-staging replaces the set, and unlike opening balances it may be sent again after an import — a catalogue is upserted, not posted. The chart lane renames freely, never deletes an account, and refuses to re-type one that already has postings. The staff lane is admin-only and CREATES people rather than updating them, so anyone already in Taokeh is left off the list. |
create_supplier_debit_note_draft | File a debit-note draft against one supplier bill — goods sent back, or a credit the supplier gave. One draft waits per bill. It is approved on its review page, where the approver decides line by line whether stock goes out; nothing posts before then. |
create_delivery_order_draft | File a delivery-order draft — the paper for goods leaving the business. It posts nothing and moves no stock; stock moves when the delivery order is invoiced. |
withdraw_draft | Take back a pending draft your own connection filed — a duplicate or a mistake. It closes as withdrawn and leaves the approval queue; a draft someone else filed, or one already decided, is refused. |
Questions developers and buyers actually ask
Can ChatGPT create an invoice in my accounting software?
With the Taokeh MCP server connected, yes — as a draft. ChatGPT calls create_invoice_draft, which files a pending sales invoice into Taokeh. It does not post to the ledger and does not move stock. You open Taokeh, check the lines against the source document, and tap approve. Only that tap posts it.
Can my AI categorise receipts and bank transactions?
Yes. Your AI reads the receipt itself and files it with create_expense_draft, original image attached. For bank statements it calls import_bank_statement, then draft_bank_classification to propose a category per row. Proposals appear as AI suggestions in Banking → Review. Confirming and posting each row stays a human click.
Can I ask who owes me money?
Yes — that is a plain read. Your AI calls ar_aging for the full receivables aging by customer and overdue bucket, or open_invoices for one customer’s unpaid invoices oldest first. payer_history explains how a given counterparty has been treated before. No approval needed: reads change nothing.
Can my AI generate my monthly profit and loss?
Yes. income_statement returns revenue, cost of goods sold, gross profit, expenses and net income for any period, straight from the double-entry ledger — not estimated by a model. balance_sheet does the same as of a date, and profit_drivers explains why the number moved against last month.
Can it prepare a monthly management report?
Not as a packaged report — as a composition your AI assembles. It calls income_statement twice (this month and last), profit_drivers for the bridge, ar_aging, cash_position, cash_forecast and expenses_summary, then writes the narrative itself on your own AI subscription. The figures come from the ledger; the document is your AI’s. Worked prompt and full recipe: /guides/talk-to-your-books.
Can it flag anomalies before month-end?
When you ask it to. No tool returns an “anomaly” field — your AI reads daily_brief, search_expenses (the doubled-bill check), ar_aging, bank_reconciliation_status and low_stock, and judges what looks off. MCP is pull-only: Taokeh runs no watcher and pushes no alert, so a standing scan is a scheduled prompt in your AI client. Full recipe: /guides/talk-to-your-books.
Is there an API? How is MCP different from a REST API?
MCP is the API, described so an AI can use it without you writing code. Each of the 95 tools carries a typed schema and a description your assistant reads at connect time, so it knows what exists and what each field means. A REST API needs an integration built first; MCP needs a connection.
Can one AI connection cover all my companies?
One connection per company — by design. A company-scoped token or OAuth grant binds to the one company you consented to, so an AI connected to one company cannot reach another’s books. claude.ai and ChatGPT both hold several named connectors side by side, so an accountant connects each company separately. The one exception is an owner with two or more companies under one sign-in: a separate, owner-only group connection reads figures across them, read-only, and never appears on a normal connection. Name each connector after the company it opens — “Taokeh — Lim Hardware”, not twelve connectors all called “Taokeh”; the name is what your AI sees in its tool list, and it is how it knows whose books it is reading. Every tool response also carries the company name, so the AI is told on every call.
Are there API rate limits for AI agents?
Yes, and they are published: 1,000 MCP calls per company per day, plus 300 requests per 15 minutes per IP address and a platform-wide daily backstop. They exist for fair use and cost control, not to meter you — even a busy working day sits well below that. A limit returns a JSON-RPC error your client can read.
Are the AI’s actions fully auditable and reversible?
Yes. Every AI-filed draft records the connecting client’s name, the user whose grant it acted under, and the time. Approving or rejecting stamps the deciding user and timestamp. Nothing posts to the ledger without that tap, and a rejected draft posts nothing at all. Correcting a posted GL document is a void and repost that keeps its number.
What does the Taokeh MCP server cost?
RM29 per month as an à-la-carte add-on on top of a Taokeh base plan, and it is included in the 14-day free trial — so you can connect your AI and try every tool before paying for anything.
Point your AI at your books
RM29/month, included in the 14-day free trial. Connect it, ask it anything, and see how a draft feels before you pay for a thing.
Tool names and behaviour on this page mirror the live server. Setup walkthrough: Ask Taokeh connector. Security and data ownership: Trust & security.