MTD Chase — chase clients for MTD records

UK bookkeepers: chase clients for Making Tax Digital quarterly records, upload links, reminders.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
78%
Naming quality
95%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~4,625Tokens (tool definitions)
~1.2 KBTypical response size
Significant attention impact (3.61% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "mtd-chase": {
      "url": "https://mtd-chase.smallwright.com/mcp"
    }
  }
}

Remote endpoints

https://mtd-chase.smallwright.com/mcpstreamable-http

What it can do

Tool inventory

Tools (20)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢get_mtd_deadlines(tax_year)

Returns the four MTD for Income Tax quarterly update periods for a tax year (standard and calendar period ends), each deadline, the final declaration date, and days until the next deadline. Works without signing in. Use this when: someone asks when the next quarterly update is due or what a Quarter covers. Not for: whether a particular Client has sent records (whos_outstanding).

Input Schema

{
  "type": "object",
  "properties": {
    "tax_year": {
      "description": "e.g. \"2026-27\". Default: the current tax year.",
      "type": "string"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢get_started

Returns the practice's setup and current position: plan and active Clients vs limit, Clients, open Chases per Quarter, settings still unset, and the next few things the practitioner can say. Use this when: the practitioner asks where they're up to or what to do next.

Input Schema

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟡update_practice(name, reply_to_email, sign_off, phone, ask_by_days, ...)

Changes what Clients see and how MTD Chase behaves for this practice: name shown to Clients, reply-to email, sign-off, phone shown on the Client's page, how many days before the HMRC deadline Clients are asked to send by (0–30, default 10; applies to Chases started afterwards), how many days after a deadline files are kept (30–365), daily summary email on/off, and the default checklist new Chases ask Clients for (1–8 items; running Chases keep theirs). Returns before → after. Use this when: the practitioner changes their details, the date clients are asked to send by, their default checklist, or retention.

Input Schema

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string"
    },
    "reply_to_email": {
      "type": "string"
    },
    "sign_off": {
      "type": "string"
    },
    "phone": {
      "description": "UK phone number shown to Clients; empty clears it",
      "type": "string"
    },
    "ask_by_days": {
      "description": "0–30: days before the HMRC deadline that clients are asked to send by",
      "type": "number"
    },
    "retention_days": {
      "description": "30–365: days after the HMRC deadline that files are kept",
      "type": "number"
    },
    "daily_summary": {
      "type": "boolean"
    },
    "default_checklist": {
      "description": "1–8 items, each up to 120 characters",
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "idempotency_key": {
      "description": "Optional; reuse when retrying so the change happens once.",
      "type": "string",
      "maxLength": 100
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢export_practice_data

Exports everything the practice holds in MTD Chase (Clients, Chases with history, Nudges sent, Records list, requests) as one JSON file; returns a download link for the signed-in practitioner. Use this when: they want a copy of their data or are leaving.

Input Schema

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
⚪request_feature(what_the_user_wanted, what_they_were_trying_to_achieve, closest_existing_tool, urgency, idempotency_key)

Files a request with MTD Chase when the user asks for something none of the other tools can do, or adds a vote to a matching open request; returns its ID, status and any workaround with existing tools. No date is promised. Use this when: the practitioner wants a capability MTD Chase doesn't have. Not for: reporting a single Client's problem.

Input Schema

{
  "type": "object",
  "properties": {
    "what_the_user_wanted": {
      "type": "string",
      "description": "their own words"
    },
    "what_they_were_trying_to_achieve": {
      "type": "string",
      "description": "the job behind it"
    },
    "closest_existing_tool": {
      "type": "string"
    },
    "urgency": {
      "type": "string",
      "enum": [
        "blocking",
        "nice_to_have"
      ],
      "description": "blocking = they can't do the job today; nice_to_have = a workaround exists"
    },
    "idempotency_key": {
      "description": "Optional; reuse when retrying so the change happens once.",
      "type": "string",
      "maxLength": 100
    }
  },
  "required": [
    "what_the_user_wanted",
    "what_they_were_trying_to_achieve",
    "urgency"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢list_my_requests

Lists the practice's feature requests with status (open, planned, live, declined), how many times each was asked for, the workaround meanwhile, and for declined ones the reason. Use this when: asked what happened to something they asked for. Not for: asking for something new (request_feature) or what's recently live for everyone (whats_new).

Input Schema

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢whats_new

Lists changes that went live recently in MTD Chase, and which of this practice's requests are now live, with the date each went live and what to say to try it. Use this when: the practitioner asks what's new, or whether something they asked for is live yet.

Input Schema

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟡add_clients(clients, confirm, idempotency_key)

Adds Clients (people the practice does MTD quarterly updates for) from a pasted list; matches existing Clients by email, else exact name. confirm:false (default) shows what would be added, skipped as duplicates, or rejected, and the plan-limit effect; confirm:true saves. Max 500. Use this when: setting up or adding MTD clients from a spreadsheet or accounting-software export, or a typed list. Not for: changing one Client (update_client).

Input Schema

{
  "type": "object",
  "properties": {
    "clients": {
      "maxItems": 500,
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "name": {
            "type": "string"
          },
          "email": {
            "type": "string"
          },
          "mobile": {
            "type": "string"
          },
          "period_type": {
            "description": "standard = periods end on the 5th; calendar = month-end",
            "type": "string",
            "enum": [
              "standard",
              "calendar"
            ]
          },
          "tags": {
            "type": "array",
            "items": {
              "type": "string"
            }
          },
          "ref": {
            "description": "your own client reference",
            "type": "string"
          }
        },
        "required": [
          "name"
        ]
      }
    },
    "confirm": {
      "default": false,
      "description": "false (default) = dry run: shows what would happen, changes nothing. true = do it.",
      "type": "boolean"
    },
    "idempotency_key": {
      "description": "Optional; reuse when retrying so the change happens once.",
      "type": "string",
      "maxLength": 100
    }
  },
  "required": [
    "clients"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟡update_client(client, name, email, mobile, period_type, ...)

Changes one Client's name, email, mobile, period type (standard/calendar), tags or reference. Returns before → after. Use this when: a Client's details change. Not for: stopping chasing someone (archive_client) or pausing nudges (pause_nudges).

Input Schema

{
  "type": "object",
  "properties": {
    "client": {
      "type": "string",
      "description": "Client name, email or your own reference"
    },
    "name": {
      "type": "string"
    },
    "email": {
      "type": "string"
    },
    "mobile": {
      "type": "string"
    },
    "period_type": {
      "type": "string",
      "enum": [
        "standard",
        "calendar"
      ]
    },
    "tags": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "ref": {
      "type": "string"
    },
    "idempotency_key": {
      "description": "Optional; reuse when retrying so the change happens once.",
      "type": "string",
      "maxLength": 100
    }
  },
  "required": [
    "client"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🔴archive_client(client, unarchive, confirm, idempotency_key)

Archives a Client who has left: their open Chases become skipped and their links stop working; they stop counting towards the plan limit. confirm:false (default) shows what would change. unarchive:true brings them back. Use this when: a Client leaves the practice or comes back.

Input Schema

{
  "type": "object",
  "properties": {
    "client": {
      "type": "string",
      "description": "Client name, email or your own reference"
    },
    "unarchive": {
      "default": false,
      "type": "boolean"
    },
    "confirm": {
      "default": false,
      "description": "false (default) = dry run: shows what would happen, changes nothing. true = do it.",
      "type": "boolean"
    },
    "idempotency_key": {
      "description": "Optional; reuse when retrying so the change happens once.",
      "type": "string",
      "maxLength": 100
    }
  },
  "required": [
    "client"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢list_clients(text, tag, period_type, include_archived)

Lists Clients with contact details, period type, tags and the status of their Chase for the current Quarter. Use this when: looking up who the practice has, finding a Client's details, or seeing a tagged group (e.g. landlords) with this Quarter's status.

Input Schema

{
  "type": "object",
  "properties": {
    "text": {
      "description": "part of a name or email",
      "type": "string"
    },
    "tag": {
      "type": "string"
    },
    "period_type": {
      "type": "string",
      "enum": [
        "standard",
        "calendar"
      ]
    },
    "include_archived": {
      "type": "boolean"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟡start_chase(quarter, clients, checklist, confirm, idempotency_key)

Starts chasing Clients for their records for a Quarter: each gets a personal link (no login, works on a phone) and a first email; then Nudges go out on the practice's plan until they send their records. confirm:false (default) shows who would be chased, who has no email, the checklist and the dates (the date Clients are asked to send by, and the HMRC deadline); confirm:true starts it. Safe to repeat: Clients already being chased are left alone. Use this when: asking Clients to send their records for a Quarter — everyone, a group by tag, or one Client — including particular items such as bank statements or receipts (checklist). Not for: reminding Clients already being chased (send_nudges_now); documents unrelated to the quarterly update.

Input Schema

{
  "type": "object",
  "properties": {
    "quarter": {
      "description": "Quarter like \"2026-27 Q3\". Default: the Quarter whose HMRC deadline is next.",
      "type": "string"
    },
    "clients": {
      "anyOf": [
        {
          "type": "string",
          "const": "all"
        },
        {
          "type": "array",
          "items": {
            "type": "string"
          }
        }
      ],
      "description": "\"all\", or Client names/emails/tags"
    },
    "checklist": {
      "description": "what to send, 1–8 items; default: the practice's checklist (sales and income, receipts and invoices for expenses, bank statements for accounts the practice can't already see)",
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "confirm": {
      "default": false,
      "description": "false (default) = dry run: shows what would happen, changes nothing. true = do it.",
      "type": "boolean"
    },
    "idempotency_key": {
      "description": "Optional; reuse when retrying so the change happens once.",
      "type": "string",
      "maxLength": 100
    }
  },
  "required": [
    "clients"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢get_chase_links(quarter, clients)

Returns each Client's personal records link for a Quarter and a ready-to-paste message for a messaging app or text. Use this when: the practitioner wants to send a link themselves (no email on file, or they prefer a messaging app or text).

Input Schema

{
  "type": "object",
  "properties": {
    "quarter": {
      "description": "Quarter like \"2026-27 Q3\". Default: the Quarter whose HMRC deadline is next.",
      "type": "string"
    },
    "clients": {
      "description": "names/emails; default all being chased",
      "type": "array",
      "items": {
        "type": "string"
      }
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟡mark_chase(client, quarter, status, note, recount, ...)

Sets one Client's Chase for a Quarter to ready, partial, nothing_to_report, skipped or back to waiting, with an optional note; Nudges stop for ready/nothing_to_report/skipped and resume for waiting/partial. The change is recorded in the Client's history. Use this when: records arrived another way (office, post, email) or a Client should be skipped this Quarter.

Input Schema

{
  "type": "object",
  "properties": {
    "client": {
      "type": "string",
      "description": "Client name, email or your own reference"
    },
    "quarter": {
      "description": "Quarter like \"2026-27 Q3\". Default: the Quarter whose HMRC deadline is next.",
      "type": "string"
    },
    "status": {
      "type": "string",
      "enum": [
        "waiting",
        "partial",
        "ready",
        "nothing_to_report",
        "skipped"
      ]
    },
    "note": {
      "type": "string",
      "maxLength": 300
    },
    "recount": {
      "description": "true = recount lateness from now",
      "type": "boolean"
    },
    "idempotency_key": {
      "description": "Optional; reuse when retrying so the change happens once.",
      "type": "string",
      "maxLength": 100
    }
  },
  "required": [
    "client",
    "status"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢list_records(quarter, client)

Lists the files (name, size, received) a Client sent through their link for a Quarter — or for every Client in a Quarter — with download links valid 24 hours for the signed-in practitioner, and the Client's note marked as written by the Client. Use this when: asked what a Client sent or to download it.

Input Schema

{
  "type": "object",
  "properties": {
    "quarter": {
      "description": "Quarter like \"2026-27 Q3\". Default: the Quarter whose HMRC deadline is next.",
      "type": "string"
    },
    "client": {
      "description": "Client name, email or your own reference",
      "type": "string"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟡set_nudge_plan(days_before, on_the_day, days_after, idempotency_key)

Sets when Nudges (reminder emails) go out for every Chase, including ones already running, counted from the date Clients are asked to send by (the ask-by date): days before it, on the day, and days after it, sent at 09:00 UK time on weekdays. A value left out keeps its current setting. Returns the plan in words and this Quarter's remaining nudge dates. Use this when: the practitioner wants reminders on different days. Not for: one extra reminder now (send_nudges_now), one Client (pause_nudges), or the ask-by date itself (update_practice).

Input Schema

{
  "type": "object",
  "properties": {
    "days_before": {
      "description": "1–60, up to 6 values: days before the date clients are asked to send by",
      "type": "array",
      "items": {
        "type": "number"
      }
    },
    "on_the_day": {
      "description": "also nudge on the ask-by date itself",
      "type": "boolean"
    },
    "days_after": {
      "description": "1–60, up to 6 values: days after it",
      "type": "array",
      "items": {
        "type": "number"
      }
    },
    "idempotency_key": {
      "description": "Optional; reuse when retrying so the change happens once.",
      "type": "string",
      "maxLength": 100
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟡send_nudges_now(quarter, clients, only_status, confirm, idempotency_key)

Sends a Nudge email now to Clients who haven't finished sending records for a Quarter (waiting or partial), at most one per Client per day. confirm:false (default) lists who would get one and who is excluded (no email, nudged today, paused); confirm:true sends. Use this when: chasing up everyone outstanding, or named Clients, now — an extra reminder outside the plan.

Input Schema

{
  "type": "object",
  "properties": {
    "quarter": {
      "description": "Quarter like \"2026-27 Q3\". Default: the Quarter whose HMRC deadline is next.",
      "type": "string"
    },
    "clients": {
      "description": "Client names, emails or references; default: everyone outstanding",
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "only_status": {
      "description": "e.g. waiting = only those who've sent nothing",
      "type": "string",
      "enum": [
        "waiting",
        "partial"
      ]
    },
    "confirm": {
      "default": false,
      "description": "false (default) = dry run: shows what would happen, changes nothing. true = do it.",
      "type": "boolean"
    },
    "idempotency_key": {
      "description": "Optional; reuse when retrying so the change happens once.",
      "type": "string",
      "maxLength": 100
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
⚪pause_nudges(client, until, resume, idempotency_key)

Stops all Nudges to one Client until a date (YYYY-MM-DD) or until resumed; resume:true restarts them. The result warns if the pause runs past a deadline. Use this when: a Client is ill, away or has asked for no reminders for now. Not for: a Client who has left (archive_client) or has sent their records (mark_chase).

Input Schema

{
  "type": "object",
  "properties": {
    "client": {
      "type": "string",
      "description": "Client name, email or your own reference"
    },
    "until": {
      "description": "YYYY-MM-DD",
      "type": "string"
    },
    "resume": {
      "default": false,
      "type": "boolean"
    },
    "idempotency_key": {
      "description": "Optional; reuse when retrying so the change happens once.",
      "type": "string",
      "maxLength": 100
    }
  },
  "required": [
    "client"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢whos_outstanding(quarter, late_last_quarter)

Returns the Clients who haven't finished sending records for a Quarter (waiting or partial), with days to/after the date they were asked to send by, last Nudge, whether they opened their link, and counts per status. Use this when: asked who's still outstanding, who's sent what, or how the Quarter is going. Not for: one tagged group (list_clients with tag).

Input Schema

{
  "type": "object",
  "properties": {
    "quarter": {
      "description": "Quarter like \"2026-27 Q3\". Default: the Quarter whose HMRC deadline is next.",
      "type": "string"
    },
    "late_last_quarter": {
      "description": "only those who were late last Quarter",
      "type": "boolean"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢get_client_history(client)

Returns a Client's Chases across Quarters — when they finished and how many days early or late against the date they were asked to send by (and whether before or after the HMRC deadline) — with a one-line summary. Without a client, returns every active Client ranked by how late they usually are. Use this when: asked whether a Client is usually late, how they did last time, or who's always late. Not for: who hasn't sent records this Quarter (whos_outstanding).

Input Schema

{
  "type": "object",
  "properties": {
    "client": {
      "description": "Client name, email or your own reference",
      "type": "string"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded20 tools