Zaim API MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZAIM_ACCESS_TOKEN | Yes | Zaim API Access Token | |
| ZAIM_CONSUMER_KEY | Yes | Zaim API Consumer Key | |
| ZAIM_CONSUMER_SECRET | Yes | Zaim API Consumer Secret | |
| ZAIM_ACCESS_TOKEN_SECRET | Yes | Zaim API Access Token Secret |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| zaim_check_auth_statusB | Zaim APIの認証状態をチェックし、アクセストークンの有効性を確認します |
| zaim_get_user_infoB | Zaimユーザーの詳細情報（プロフィール、統計情報等）を取得します |
| zaim_get_money_recordsB | Zaim家計簿の支出・収入・振替記録を取得します。日付範囲、カテゴリ、モードでフィルタリング可能です。 |
| zaim_create_paymentC | Zaimに支出記録を作成します |
| zaim_create_incomeC | Zaimに収入記録を作成します |
| zaim_create_transferB | Zaimに振替記録を作成します（口座間の資金移動） |
| zaim_update_money_recordC | Zaimの既存の家計簿記録を更新します |
| zaim_delete_money_recordA | Zaimの家計簿記録を削除します。削除は永続的で復元できません。 |
| zaim_get_user_categoriesB | Zaimユーザーのカスタムカテゴリ一覧を取得します |
| zaim_get_user_genresB | Zaimユーザーのカスタムジャンル一覧を取得します |
| zaim_get_user_accountsB | Zaimユーザーの口座一覧を取得します |
| zaim_get_default_categoriesB | Zaimのデフォルトカテゴリ一覧を取得します（支出または収入） |
| zaim_get_default_genresB | Zaimのデフォルトジャンル一覧を取得します（支出または収入） |
| zaim_get_currenciesB | Zaimで利用可能な通貨一覧を取得します |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Every tool has a clearly distinct purpose with no ambiguity. Tools are well-separated by resource (e.g., money records, categories, user info) and action (e.g., create, get, update, delete). For example, zaim_create_income, zaim_create_payment, and zaim_create_transfer handle different types of money records, while get tools target specific data sets like currencies or accounts.
All tool names follow a consistent verb_noun pattern with the prefix 'zaim_', such as zaim_create_income, zaim_get_currencies, and zaim_update_money_record. This uniformity makes the tool set predictable and easy to navigate, with no deviations in naming style or structure.
With 14 tools, the count is well-scoped for a personal finance API server. Each tool earns its place by covering essential operations like CRUD for money records, retrieval of metadata (currencies, categories), and user management, without being excessive or too sparse for the domain.
The tool surface provides complete CRUD/lifecycle coverage for the Zaim API domain. It includes creation, retrieval, update, and deletion for money records, along with supporting operations for authentication, user info, accounts, and metadata (currencies, categories, genres). No obvious gaps exist; agents can perform full workflows without dead ends.