MTD Chase — chase clients for MTD records is an MCP server published by com.smallwright, hosted at mtd-chase.smallwright.com. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 20 tools, including get_mtd_deadlines, get_started, update_practice, export_practice_data, request_feature.
UK bookkeepers: chase clients for Making Tax Digital quarterly records, upload links, reminders.
201 connections through 5 shared values. Tap any node.
Inferred from the host name and headers: what a server runs on, not who runs it.
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).
| Parameter | Type | Description |
|---|---|---|
| tax_year | string | e.g. "2026-27". Default: the current tax year. |
{
"name": "get_mtd_deadlines",
"title": "MTD deadlines",
"description": "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.\nUse this when: someone asks when the next quarterly update is due or what a Quarter covers.\nNot for: whether a particular Client has sent records (whos_outstanding).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"tax_year": {
"type": "string",
"description": "e.g. \"2026-27\". Default: the current tax year."
}
}
},
"annotations": {
"title": "MTD deadlines",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
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.
No parameters.
{
"name": "get_started",
"title": "Where am I up to",
"description": "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.\nUse this when: the practitioner asks where they're up to or what to do next.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
},
"annotations": {
"title": "Where am I up to",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| name | string | |
| phone | string | UK phone number shown to Clients; empty clears it |
| sign_off | string | |
| ask_by_days | number | 0–30: days before the HMRC deadline that clients are asked to send by |
| daily_summary | boolean | |
| reply_to_email | string | |
| retention_days | number | 30–365: days after the HMRC deadline that files are kept |
| idempotency_key | string | Optional; reuse when retrying so the change happens once. |
| default_checklist | array | 1–8 items, each up to 120 characters |
{
"name": "update_practice",
"title": "Update practice settings",
"description": "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.\nUse this when: the practitioner changes their details, the date clients are asked to send by, their default checklist, or retention.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"name": {
"type": "string"
},
"phone": {
"type": "string",
"description": "UK phone number shown to Clients; empty clears it"
},
"sign_off": {
"type": "string"
},
"ask_by_days": {
"type": "number",
"description": "0–30: days before the HMRC deadline that clients are asked to send by"
},
"daily_summary": {
"type": "boolean"
},
"reply_to_email": {
"type": "string"
},
"retention_days": {
"type": "number",
"description": "30–365: days after the HMRC deadline that files are kept"
},
"idempotency_key": {
"type": "string",
"maxLength": 100,
"description": "Optional; reuse when retrying so the change happens once."
},
"default_checklist": {
"type": "array",
"items": {
"type": "string"
},
"description": "1–8 items, each up to 120 characters"
}
}
},
"annotations": {
"title": "Update practice settings",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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.
No parameters.
{
"name": "export_practice_data",
"title": "Export practice data",
"description": "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.\nUse this when: they want a copy of their data or are leaving.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
},
"annotations": {
"title": "Export practice data",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| urgency * | string | blocking = they can't do the job today; nice_to_have = a workaround exists |
| idempotency_key | string | Optional; reuse when retrying so the change happens once. |
| what_the_user_wanted * | string | their own words |
| closest_existing_tool | string | |
| what_they_were_trying_to_achieve * | string | the job behind it |
{
"name": "request_feature",
"title": "Request a feature",
"description": "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.\nUse this when: the practitioner wants a capability MTD Chase doesn't have.\nNot for: reporting a single Client's problem.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"what_the_user_wanted",
"what_they_were_trying_to_achieve",
"urgency"
],
"properties": {
"urgency": {
"enum": [
"blocking",
"nice_to_have"
],
"type": "string",
"description": "blocking = they can't do the job today; nice_to_have = a workaround exists"
},
"idempotency_key": {
"type": "string",
"maxLength": 100,
"description": "Optional; reuse when retrying so the change happens once."
},
"what_the_user_wanted": {
"type": "string",
"description": "their own words"
},
"closest_existing_tool": {
"type": "string"
},
"what_they_were_trying_to_achieve": {
"type": "string",
"description": "the job behind it"
}
}
},
"annotations": {
"title": "Request a feature",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": false
}
}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).
No parameters.
{
"name": "list_my_requests",
"title": "List my feature requests",
"description": "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.\nUse this when: asked what happened to something they asked for.\nNot for: asking for something new (request_feature) or what's recently live for everyone (whats_new).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
},
"annotations": {
"title": "List my feature requests",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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.
No parameters.
{
"name": "whats_new",
"title": "What's new",
"description": "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.\nUse this when: the practitioner asks what's new, or whether something they asked for is live yet.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
},
"annotations": {
"title": "What's new",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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).
| Parameter | Type | Description |
|---|---|---|
| clients * | array | |
| confirm | boolean | false (default) = dry run: shows what would happen, changes nothing. true = do it. |
| idempotency_key | string | Optional; reuse when retrying so the change happens once. |
{
"name": "add_clients",
"title": "Add Clients",
"description": "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.\nUse this when: setting up or adding MTD clients from a spreadsheet or accounting-software export, or a typed list.\nNot for: changing one Client (update_client).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"clients"
],
"properties": {
"clients": {
"type": "array",
"items": {
"type": "object",
"required": [
"name"
],
"properties": {
"ref": {
"type": "string",
"description": "your own client reference"
},
"name": {
"type": "string"
},
"tags": {
"type": "array",
"items": {
"type": "string"
}
},
"email": {
"type": "string"
},
"mobile": {
"type": "string"
},
"period_type": {
"enum": [
"standard",
"calendar"
],
"type": "string",
"description": "standard = periods end on the 5th; calendar = month-end"
}
}
},
"maxItems": 500
},
"confirm": {
"type": "boolean",
"default": false,
"description": "false (default) = dry run: shows what would happen, changes nothing. true = do it."
},
"idempotency_key": {
"type": "string",
"maxLength": 100,
"description": "Optional; reuse when retrying so the change happens once."
}
}
},
"annotations": {
"title": "Add Clients",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": false
}
}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).
| Parameter | Type | Description |
|---|---|---|
| ref | string | |
| name | string | |
| tags | array | |
| string | ||
| client * | string | Client name, email or your own reference |
| mobile | string | |
| period_type | string | one of ["standard","calendar"] |
| idempotency_key | string | Optional; reuse when retrying so the change happens once. |
{
"name": "update_client",
"title": "Update a Client",
"description": "Changes one Client's name, email, mobile, period type (standard/calendar), tags or reference. Returns before → after.\nUse this when: a Client's details change.\nNot for: stopping chasing someone (archive_client) or pausing nudges (pause_nudges).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"client"
],
"properties": {
"ref": {
"type": "string"
},
"name": {
"type": "string"
},
"tags": {
"type": "array",
"items": {
"type": "string"
}
},
"email": {
"type": "string"
},
"client": {
"type": "string",
"description": "Client name, email or your own reference"
},
"mobile": {
"type": "string"
},
"period_type": {
"enum": [
"standard",
"calendar"
],
"type": "string"
},
"idempotency_key": {
"type": "string",
"maxLength": 100,
"description": "Optional; reuse when retrying so the change happens once."
}
}
},
"annotations": {
"title": "Update a Client",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| client * | string | Client name, email or your own reference |
| confirm | boolean | false (default) = dry run: shows what would happen, changes nothing. true = do it. |
| unarchive | boolean | |
| idempotency_key | string | Optional; reuse when retrying so the change happens once. |
{
"name": "archive_client",
"title": "Archive or unarchive a Client",
"description": "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.\nUse this when: a Client leaves the practice or comes back.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"client"
],
"properties": {
"client": {
"type": "string",
"description": "Client name, email or your own reference"
},
"confirm": {
"type": "boolean",
"default": false,
"description": "false (default) = dry run: shows what would happen, changes nothing. true = do it."
},
"unarchive": {
"type": "boolean",
"default": false
},
"idempotency_key": {
"type": "string",
"maxLength": 100,
"description": "Optional; reuse when retrying so the change happens once."
}
}
},
"annotations": {
"title": "Archive or unarchive a Client",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": true
}
}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.
| Parameter | Type | Description |
|---|---|---|
| tag | string | |
| text | string | part of a name or email |
| period_type | string | one of ["standard","calendar"] |
| include_archived | boolean |
{
"name": "list_clients",
"title": "List Clients",
"description": "Lists Clients with contact details, period type, tags and the status of their Chase for the current Quarter.\nUse 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.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"tag": {
"type": "string"
},
"text": {
"type": "string",
"description": "part of a name or email"
},
"period_type": {
"enum": [
"standard",
"calendar"
],
"type": "string"
},
"include_archived": {
"type": "boolean"
}
}
},
"annotations": {
"title": "List Clients",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| clients * | any | "all", or Client names/emails/tags |
| confirm | boolean | false (default) = dry run: shows what would happen, changes nothing. true = do it. |
| quarter | string | Quarter like "2026-27 Q3". Default: the Quarter whose HMRC deadline is next. |
| checklist | array | 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) |
| idempotency_key | string | Optional; reuse when retrying so the change happens once. |
{
"name": "start_chase",
"title": "Chase a Quarter",
"description": "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.\nUse 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).\nNot for: reminding Clients already being chased (send_nudges_now); documents unrelated to the quarterly update.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"clients"
],
"properties": {
"clients": {
"anyOf": [
{
"type": "string",
"const": "all"
},
{
"type": "array",
"items": {
"type": "string"
}
}
],
"description": "\"all\", or Client names/emails/tags"
},
"confirm": {
"type": "boolean",
"default": false,
"description": "false (default) = dry run: shows what would happen, changes nothing. true = do it."
},
"quarter": {
"type": "string",
"description": "Quarter like \"2026-27 Q3\". Default: the Quarter whose HMRC deadline is next."
},
"checklist": {
"type": "array",
"items": {
"type": "string"
},
"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)"
},
"idempotency_key": {
"type": "string",
"maxLength": 100,
"description": "Optional; reuse when retrying so the change happens once."
}
}
},
"annotations": {
"title": "Chase a Quarter",
"readOnlyHint": false,
"openWorldHint": true,
"idempotentHint": false,
"destructiveHint": false
}
}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).
| Parameter | Type | Description |
|---|---|---|
| clients | array | names/emails; default all being chased |
| quarter | string | Quarter like "2026-27 Q3". Default: the Quarter whose HMRC deadline is next. |
{
"name": "get_chase_links",
"title": "Get Chase links",
"description": "Returns each Client's personal records link for a Quarter and a ready-to-paste message for a messaging app or text.\nUse this when: the practitioner wants to send a link themselves (no email on file, or they prefer a messaging app or text).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"clients": {
"type": "array",
"items": {
"type": "string"
},
"description": "names/emails; default all being chased"
},
"quarter": {
"type": "string",
"description": "Quarter like \"2026-27 Q3\". Default: the Quarter whose HMRC deadline is next."
}
}
},
"annotations": {
"title": "Get Chase links",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| note | string | |
| client * | string | Client name, email or your own reference |
| status * | string | one of ["waiting","partial","ready","nothing_to_report","skipped"] |
| quarter | string | Quarter like "2026-27 Q3". Default: the Quarter whose HMRC deadline is next. |
| recount | boolean | true = recount lateness from now |
| idempotency_key | string | Optional; reuse when retrying so the change happens once. |
{
"name": "mark_chase",
"title": "Set a Chase status",
"description": "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.\nUse this when: records arrived another way (office, post, email) or a Client should be skipped this Quarter.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"client",
"status"
],
"properties": {
"note": {
"type": "string",
"maxLength": 300
},
"client": {
"type": "string",
"description": "Client name, email or your own reference"
},
"status": {
"enum": [
"waiting",
"partial",
"ready",
"nothing_to_report",
"skipped"
],
"type": "string"
},
"quarter": {
"type": "string",
"description": "Quarter like \"2026-27 Q3\". Default: the Quarter whose HMRC deadline is next."
},
"recount": {
"type": "boolean",
"description": "true = recount lateness from now"
},
"idempotency_key": {
"type": "string",
"maxLength": 100,
"description": "Optional; reuse when retrying so the change happens once."
}
}
},
"annotations": {
"title": "Set a Chase status",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| client | string | Client name, email or your own reference |
| quarter | string | Quarter like "2026-27 Q3". Default: the Quarter whose HMRC deadline is next. |
{
"name": "list_records",
"title": "List Records",
"description": "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.\nUse this when: asked what a Client sent or to download it.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"client": {
"type": "string",
"description": "Client name, email or your own reference"
},
"quarter": {
"type": "string",
"description": "Quarter like \"2026-27 Q3\". Default: the Quarter whose HMRC deadline is next."
}
}
},
"annotations": {
"title": "List Records",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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).
| Parameter | Type | Description |
|---|---|---|
| days_after | array | 1–60, up to 6 values: days after it |
| on_the_day | boolean | also nudge on the ask-by date itself |
| days_before | array | 1–60, up to 6 values: days before the date clients are asked to send by |
| idempotency_key | string | Optional; reuse when retrying so the change happens once. |
{
"name": "set_nudge_plan",
"title": "Set the nudge plan",
"description": "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.\nUse this when: the practitioner wants reminders on different days.\nNot for: one extra reminder now (send_nudges_now), one Client (pause_nudges), or the ask-by date itself (update_practice).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"days_after": {
"type": "array",
"items": {
"type": "number"
},
"description": "1–60, up to 6 values: days after it"
},
"on_the_day": {
"type": "boolean",
"description": "also nudge on the ask-by date itself"
},
"days_before": {
"type": "array",
"items": {
"type": "number"
},
"description": "1–60, up to 6 values: days before the date clients are asked to send by"
},
"idempotency_key": {
"type": "string",
"maxLength": 100,
"description": "Optional; reuse when retrying so the change happens once."
}
}
},
"annotations": {
"title": "Set the nudge plan",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| clients | array | Client names, emails or references; default: everyone outstanding |
| confirm | boolean | false (default) = dry run: shows what would happen, changes nothing. true = do it. |
| quarter | string | Quarter like "2026-27 Q3". Default: the Quarter whose HMRC deadline is next. |
| only_status | string | e.g. waiting = only those who've sent nothing |
| idempotency_key | string | Optional; reuse when retrying so the change happens once. |
{
"name": "send_nudges_now",
"title": "Nudge now",
"description": "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.\nUse this when: chasing up everyone outstanding, or named Clients, now — an extra reminder outside the plan.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"clients": {
"type": "array",
"items": {
"type": "string"
},
"description": "Client names, emails or references; default: everyone outstanding"
},
"confirm": {
"type": "boolean",
"default": false,
"description": "false (default) = dry run: shows what would happen, changes nothing. true = do it."
},
"quarter": {
"type": "string",
"description": "Quarter like \"2026-27 Q3\". Default: the Quarter whose HMRC deadline is next."
},
"only_status": {
"enum": [
"waiting",
"partial"
],
"type": "string",
"description": "e.g. waiting = only those who've sent nothing"
},
"idempotency_key": {
"type": "string",
"maxLength": 100,
"description": "Optional; reuse when retrying so the change happens once."
}
}
},
"annotations": {
"title": "Nudge now",
"readOnlyHint": false,
"openWorldHint": true,
"idempotentHint": false,
"destructiveHint": false
}
}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).
| Parameter | Type | Description |
|---|---|---|
| until | string | YYYY-MM-DD |
| client * | string | Client name, email or your own reference |
| resume | boolean | |
| idempotency_key | string | Optional; reuse when retrying so the change happens once. |
{
"name": "pause_nudges",
"title": "Pause or resume Nudges",
"description": "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.\nUse this when: a Client is ill, away or has asked for no reminders for now.\nNot for: a Client who has left (archive_client) or has sent their records (mark_chase).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"client"
],
"properties": {
"until": {
"type": "string",
"description": "YYYY-MM-DD"
},
"client": {
"type": "string",
"description": "Client name, email or your own reference"
},
"resume": {
"type": "boolean",
"default": false
},
"idempotency_key": {
"type": "string",
"maxLength": 100,
"description": "Optional; reuse when retrying so the change happens once."
}
}
},
"annotations": {
"title": "Pause or resume Nudges",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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).
| Parameter | Type | Description |
|---|---|---|
| quarter | string | Quarter like "2026-27 Q3". Default: the Quarter whose HMRC deadline is next. |
| late_last_quarter | boolean | only those who were late last Quarter |
{
"name": "whos_outstanding",
"title": "Who's outstanding",
"description": "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.\nUse this when: asked who's still outstanding, who's sent what, or how the Quarter is going.\nNot for: one tagged group (list_clients with tag).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"quarter": {
"type": "string",
"description": "Quarter like \"2026-27 Q3\". Default: the Quarter whose HMRC deadline is next."
},
"late_last_quarter": {
"type": "boolean",
"description": "only those who were late last Quarter"
}
}
},
"annotations": {
"title": "Who's outstanding",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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).
| Parameter | Type | Description |
|---|---|---|
| client | string | Client name, email or your own reference |
{
"name": "get_client_history",
"title": "Client history",
"description": "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.\nUse this when: asked whether a Client is usually late, how they did last time, or who's always late.\nNot for: who hasn't sent records this Quarter (whos_outstanding).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"client": {
"type": "string",
"description": "Client name, email or your own reference"
}
}
},
"annotations": {
"title": "Client history",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}MTD Chase keeps a UK practice's MTD Income Tax records chase: Clients, Quarters, Chases (one per Client per Quarter, with a personal no-login link), Records the Client sends, and Nudges (reminder emails). Concepts and tool replies use those words.
Names, descriptions and schemas were written by the server and are shown as data.
Shared addresses on big platforms (Cloudflare, Vercel and the like) put unrelated servers together; those are marked shared_infrastructure. A match is a pivot, not a link between operators.