Debt Payoff Planner MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBT_CONFIG | No | Path to the YAML configuration file (e.g. data_dir, timezone, currency, default_budget). Overridden by the --config CLI flag. Relative YAML paths resolve beside the config. | |
| DEBT_DATA_DIR | No | Data directory for the ledger storage (debts.db). Data directory precedence is CLI --data-dir → DEBT_DATA_DIR → YAML config → ./data. Relative paths resolve from the working directory. |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_debtsB | Read current principal, assessed charges, retained fees and contract assumptions. Amounts are integer cents. |
| simulate_planB | Read a bounded monthly payoff projection. Budget is major currency units; strategies: snowball, avalanche, custom, baseline. Does not write or pay money. |
| compare_strategiesC | Compare four strategies without writing. Incomplete baselines produce null interest savings, never fabricated savings. |
| record_paymentA | Write an actual payment journal entry and reduce local principal. No external money transfer. Optional interest replaces estimated newly assessed finance charges; reuse an idempotency key on retries. |
| upcoming_paymentsB | Read estimated upcoming minimums within 0–366 days, accounting for actual payments already recorded in the month. |
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 5 tools
Most tools have clearly distinct purposes: list_debts reads state, record_payment writes, and upcoming_payments projects minimums. simulate_plan and compare_strategies both produce non-writing projections, so their boundaries are close but descriptions clarify single-plan vs four-strategy comparison.
Four tools follow a clear verb_noun pattern: list_debts, simulate_plan, compare_strategies, and record_payment. upcoming_payments breaks the pattern as an adjective_noun phrase, but overall the naming remains predictable.
Five tools is well-scoped for a debt payoff planner: read debts, simulate, compare strategies, record payments, and view upcoming payments. Each tool earns its place without excessive surface area.
The server covers reading debts, planning, comparison, payment recording, and upcoming minimums. However, there is no tool to create or update a debt or its contract assumptions, which is a notable gap for initializing and maintaining the debt list.