MCP server for Mekari Jurnal — company accounting, sales, purchases and customer/vendor creation. For finance teams with company-scoped Mekari Jurnal API credentials. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"jurnal": {
"url": "https://jurnal.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"jurnal": {
"type": "http",
"url": "https://jurnal.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
List sales invoices, inspect a selected invoice and review aged receivables before following up.
jurnal_list_sales_invoices jurnal_get_sales_invoice jurnal_get_aged_receivables
Read the balance sheet, profit and loss report and cash flow for the selected reporting period.
jurnal_get_balance_sheet jurnal_get_profit_and_loss jurnal_get_cash_flow
List purchase invoices and inspect a bill alongside aged payables.
jurnal_list_purchase_invoices jurnal_get_purchase_invoice jurnal_get_aged_payables
Review existing records, then create a customer or vendor when requested. This does not post an invoice or payment.
Changes data · jurnal_list_customers jurnal_list_vendors jurnal_create_customer jurnal_create_vendor
The login page asks for your Client ID and Client Secret.
Create the credentials in the Mekari Developer dashboard (developers.mekari.com): Create Application, pick your company and the Jurnal scopes you want to allow, then copy the Client ID and Client Secret. If your dashboard is empty, ask Jurnal support to enable Mekari Developer access. Credentials belong to one company. Include the Get Current Active Company permission for login and only the other scopes you need. Requested customer, vendor, invoice, expense and financial-report data passes to your chosen AI client and its LLM provider. Two write tools create customer or vendor records; no accounting transaction, payment or refund is posted. Revoke or delete this application in Mekari Developer to stop vendor access. Billing follows the verified active company ID and stays stable when a company-scoped credential is rotated. Your Jurnal plan, monthly API quota and rate limit still apply.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Client ID and Client Secret. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Mekari Jurnal connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
jurnal_get_current_user | read | Get the current user The Jurnal user the credential acts as: id, name, email, status, owner flag and roles. GET /public/jurnal/api/v1/users/me. |
jurnal_list_companies | read | List companies The Jurnal company (or companies) the credential belongs to: id, name, industry, address, tax number, currency settings and feature flags. GET /companies. |
jurnal_list_customers | read | List customers Customers with display name, addresses, email, phone, tax number and receivable balance. Paged. GET /customers. |
jurnal_get_customer | read | Get a customer One customer by id (from jurnal_list_customers). GET /customers/{id}. |
jurnal_list_vendors | read | List vendors Vendors (suppliers) with display name, addresses, email, phone, tax number and payable balance. Paged. GET /vendors. |
jurnal_get_vendor | read | Get a vendor One vendor by id (from jurnal_list_vendors). GET /vendors/{id}. |
jurnal_list_products | read | List products Products and services: code, name, buy and sell prices, stock quantity, category, units, active flag. Paged. GET /products. |
jurnal_get_product | read | Get a product One product by id (from jurnal_list_products). GET /products/{id}. |
jurnal_list_accounts | read | List chart of accounts The chart of accounts: id, number, name, category, currency and balance. Not paged. Use the ids as account_id in jurnal_get_general_ledger. GET /accounts. |
jurnal_get_account | read | Get an account One chart-of-accounts entry by id. GET /accounts/{id}. |
jurnal_list_sales_invoices | read | List sales invoices Sales invoices: number, customer, dates, status, total (original_amount) and balance due (remaining). Sort by transaction_date or remaining to find recent or unpaid ones. Paged. GET /sales_invoices. |
jurnal_get_sales_invoice | read | Get a sales invoice One sales invoice with its lines, taxes and payments. GET /sales_invoices/{id}. |
jurnal_list_sales_orders | read | List sales orders Sales orders with customer, dates, status and totals. Paged. GET /sales_orders. |
jurnal_list_sales_quotes | read | List sales quotes Sales quotes (offers) with customer, dates, status and totals. Paged. GET /sales_quotes. |
jurnal_list_receive_payments | read | List received payments Customer payments received against sales invoices. Paged. GET /receive_payments. |
jurnal_list_purchase_invoices | read | List purchase invoices Purchase invoices (bills from vendors): number, vendor, dates, status, total and balance due. Paged. GET /purchase_invoices. |
jurnal_get_purchase_invoice | read | Get a purchase invoice One purchase invoice with its lines, taxes and payments. GET /purchase_invoices/{id}. |
jurnal_list_purchase_orders | read | List purchase orders Purchase orders with vendor, dates, status and totals. Paged. GET /purchase_orders. |
jurnal_list_purchase_payments | read | List purchase payments Payments made to vendors against purchase invoices. Paged. GET /purchase_payments. |
jurnal_list_expenses | read | List expenses Expenses: number, date, beneficiary, status, total and balance due. Paged. GET /expenses. |
jurnal_get_expense | read | Get an expense One expense with its lines. GET /expenses/{id}. |
jurnal_list_journal_entries | read | List journal entries Manual journal entries (general journal). Paged. GET /journal_entries. |
jurnal_get_journal_entry | read | Get a journal entry One journal entry with its debit and credit lines. GET /journal_entries/{id}. |
jurnal_list_taxes | read | List taxes The company's tax rates (PPN, PPh and so on). Paged. GET /taxes. |
jurnal_list_tags | read | List transaction tags Transaction tags. Not paged. GET /tags. |
jurnal_list_payment_methods | read | List payment methods Payment methods (cash, transfer and so on). Not paged. GET /payment_methods. |
jurnal_list_warehouses | read | List warehouses Warehouses (needs a Jurnal plan with inventory). Paged. GET /warehouses. |
jurnal_list_product_categories | read | List product categories Product categories. Not paged. GET /product_categories. |
jurnal_get_profit_and_loss | read | Get the profit and loss report Profit and loss (income statement) for a period: revenue, cost of sales, expenses and net profit by account. Dates are yyyy-mm-dd. GET /profit_and_loss. |
jurnal_get_balance_sheet | read | Get the balance sheet Balance sheet as of end_date (yyyy-mm-dd, default today): assets, liabilities and equity by account. GET /balance_sheet. |
jurnal_get_trial_balance | read | Get the trial balance Trial balance for a period: opening, movement and closing balance of every account. GET /trial_balance. |
jurnal_get_cash_flow | read | Get the cash flow report Cash flow statement for a period (operating, investing, financing). GET /cash_flow. |
jurnal_get_general_ledger | read | Get the general ledger General ledger for a period, optionally limited to some accounts (ids from jurnal_list_accounts). GET /general_ledger. |
jurnal_get_aged_receivables | read | Get aged receivables Aged receivables: what customers owe, bucketed by how overdue it is. GET /aged_receivables. |
jurnal_get_aged_payables | read | Get aged payables Aged payables: what is owed to vendors, bucketed by how overdue it is. GET /aged_payables. |
jurnal_get_executive_summary | read | Get the executive summary Executive summary: key figures (cash, revenue, profit, receivables, payables) for the company. GET /executive_summary. |
jurnal_create_customer | write | Create a customer Create a new customer contact in Jurnal. This writes to the user's books (a customer can be archived or deleted later in Jurnal). Only display_name is required. POST /customers. |
jurnal_create_vendor | write | Create a vendor Create a new vendor (supplier) contact in Jurnal. This writes to the user's books (a vendor can be archived or deleted later in Jurnal). Only display_name is required. POST /vendors. |
jurnal_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
jurnal_request_feature | Request a missing feature Tell usefulapi that the user needs something the Jurnal tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
jurnal_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Jurnal (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $39/month or $390/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
jurnal_cancel_subscription | Cancel the Pro subscription Cancel the caller's Jurnal Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run jurnal_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper active company | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this Mekari Jurnal server only. Subscribe with jurnal_upgrade (it returns a Stripe Checkout link). Cancel any time with jurnal_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running jurnal_upgrade before then undoes the cancel. Or write to [email protected].
Review receivables and customer invoices. Check financial reports. Review supplier bills. Create a customer or vendor. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by Mekari Jurnal. The server calls the Mekari Jurnal API with your own Mekari Jurnal access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Client ID and Client Secret. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Client ID and Client Secret. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Mekari Jurnal API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Mekari Jurnal.
Yes, if you approve it. 2 of the 38 Mekari Jurnal tools can create or change data. The other 36 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this Mekari Jurnal server only. Cancel any time: Pro then runs to the end of the paid period. Run jurnal_usage_status to see how many calls you used.
Ask the AI to run jurnal_upgrade: it returns a Stripe Checkout link. To cancel, run jurnal_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with jurnal_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.