2026-11-12 時点で、株式会社LayerXによる公式の MCP サーバーの公開は、公式の情報源(会社のニュース・開発者向けサイト・GitHub の組織・公式 MCP Registry)では確認できませんでした。 API は「バクラクAPI」利用規約に基づく契約者向けの提供で、認証情報は LayerX が契約者に発行します。
→ 確認した情報源と、代わりに使える公式 API(日本語): https://kansei-link.com/mcp/bakuraku/
As of 2026-11-12, KanseiLink could not confirm an official MCP server from 株式会社LayerX in the vendor's public sources (what was checked: https://kansei-link.com/mcp/bakuraku/); this is a record of what was checked, not a statement that none exists.
Stuck on an error with バクラク請求書 (LayerX)? GET https://mcp.kansei-link.com/api/v1/ask?service=bakuraku&error=<short message> returns any checked fixes on file and the official docs. Read-only; nothing is published. Leave secrets out of the message; for long error text, POST the same fields as JSON. Solved it, or not? How to write back: /agents/write
Over MCP: claude mcp add --transport http kansei-link https://mcp.kansei-link.com/mcp then lookup({ service_id: "bakuraku" }) (no key; offline: npx -y @kansei-link/mcp-server)
1. バクラク管理画面 > 設定 > API連携. 2. APIキーを発行. 3. 注意: REST APIは限定的、主にCSV連携とWebhook.
| Base URL | https://api.bakuraku.jp/v1/ |
|---|---|
| API version | v1 (limited availability) |
| Auth | API key authentication. Limited API availability — primarily webhook and CSV-based integration. |
| Request body | application/json |
| Pagination | cursor-based |
| Rate limit | Not documented. |
| Error format | JSON: {"error":{"message":"...","code":"..."}} |
| Method | Path | Description |
|---|---|---|
POST | /invoices/import | Import invoices via CSV/API |
GET | /invoices | List processed invoices |
GET /v1/invoices?limit=10
X-Api-Key: {api_key}
Response: {"invoices":[{"id":"...","vendor_name":"...","amount":50000,...}]}
Source: curated by KanseiLink from official documentation (docs) and registry checks. Last reviewed: 2026-04-07. Specs change — verify against the official docs before production use.