Mekari Jurnal MCP by usefulapi

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

• 连接方式: 在云端运行
• 传输方式: Streamable HTTP
• 分类: 会计、财务与税务

安装

选择你使用的 AI 应用，然后复制设置。

你需要

• 在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

https://jurnal.usefulapi.io/mcp

claude mcp add --transport http jurnal https://jurnal.usefulapi.io/mcp

{
  "mcpServers": {
    "jurnal": {
      "url": "https://jurnal.usefulapi.io/mcp"
    }
  }
}

{
  "servers": {
    "jurnal": {
      "type": "http",
      "url": "https://jurnal.usefulapi.io/mcp"
    }
  }
}

https://jurnal.usefulapi.io/mcp

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月6日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

• jurnal_get_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

  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

  Customers with display name, addresses, email, phone, tax number and receivable balance. Paged. GET /customers.

• jurnal_get_customer

  One customer by id (from jurnal_list_customers). GET /customers/{id}.

• jurnal_list_vendors

  Vendors (suppliers) with display name, addresses, email, phone, tax number and payable balance. Paged. GET /vendors.

• jurnal_get_vendor

  One vendor by id (from jurnal_list_vendors). GET /vendors/{id}.

• jurnal_list_products

  Products and services: code, name, buy and sell prices, stock quantity, category, units, active flag. Paged. GET /products.

• jurnal_get_product

  One product by id (from jurnal_list_products). GET /products/{id}.

• jurnal_list_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

  One chart-of-accounts entry by id. GET /accounts/{id}.

• jurnal_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

  One sales invoice with its lines, taxes and payments. GET /sales_invoices/{id}.

• jurnal_list_sales_orders

  Sales orders with customer, dates, status and totals. Paged. GET /sales_orders.

• jurnal_list_sales_quotes

  Sales quotes (offers) with customer, dates, status and totals. Paged. GET /sales_quotes.

• jurnal_list_receive_payments

  Customer payments received against sales invoices. Paged. GET /receive_payments.

• jurnal_list_purchase_invoices

  Purchase invoices (bills from vendors): number, vendor, dates, status, total and balance due. Paged. GET /purchase_invoices.

• jurnal_get_purchase_invoice

  One purchase invoice with its lines, taxes and payments. GET /purchase_invoices/{id}.

• jurnal_list_purchase_orders

  Purchase orders with vendor, dates, status and totals. Paged. GET /purchase_orders.

• jurnal_list_purchase_payments

  Payments made to vendors against purchase invoices. Paged. GET /purchase_payments.

• jurnal_list_expenses

  Expenses: number, date, beneficiary, status, total and balance due. Paged. GET /expenses.

• jurnal_get_expense

  One expense with its lines. GET /expenses/{id}.

• jurnal_list_journal_entries

  Manual journal entries (general journal). Paged. GET /journal_entries.

• jurnal_get_journal_entry

  One journal entry with its debit and credit lines. GET /journal_entries/{id}.

• jurnal_list_taxes

  The company's tax rates (PPN, PPh and so on). Paged. GET /taxes.

• jurnal_list_tags

  Transaction tags. Not paged. GET /tags.

• jurnal_list_payment_methods

  Payment methods (cash, transfer and so on). Not paged. GET /payment_methods.

• jurnal_list_warehouses

  Warehouses (needs a Jurnal plan with inventory). Paged. GET /warehouses.

• jurnal_list_product_categories

  Product categories. Not paged. GET /product_categories.

• jurnal_get_profit_and_loss

  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

  Balance sheet as of end_date (yyyy-mm-dd, default today): assets, liabilities and equity by account. GET /balance_sheet.

• jurnal_get_trial_balance

  Trial balance for a period: opening, movement and closing balance of every account. GET /trial_balance.

• jurnal_get_cash_flow

  Cash flow statement for a period (operating, investing, financing). GET /cash_flow.

• jurnal_get_general_ledger

  General ledger for a period, optionally limited to some accounts (ids from jurnal_list_accounts). GET /general_ledger.

• jurnal_get_aged_receivables

  Aged receivables: what customers owe, bucketed by how overdue it is. GET /aged_receivables.

• jurnal_get_aged_payables

  Aged payables: what is owed to vendors, bucketed by how overdue it is. GET /aged_payables.

• jurnal_get_executive_summary

  Executive summary: key figures (cash, revenue, profit, receivables, payables) for the company. GET /executive_summary.

• jurnal_create_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

  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.

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

• ✓ 通过

  作者与仓库一致

  注册名称已通过域名 usefulapi.io 验证（注册中心会核实域名所有权）

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 16 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 38 个工具描述，未发现针对 AI 的隐藏指令

与“会计、财务与税务”中的其他服务器比较i

• 星标数多于此分类中其他 1720 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 1720 个服务器的 97% 更新
• 基础检查结果等于或优于此分类中其他 1720 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

作者的 README

{