MTD Chase — chase clients for MTD records

● Active

com.smallwright/mtd-chase

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

Connect this server

One click to install, or copy the config below. Suits: Cursor · HTTP clients.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "mtd-chase": {
      "url": "https://mtd-chase.smallwright.com/mcp"
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add --transport http mtd-chase https://mtd-chase.smallwright.com/mcp
VS Code
code --add-mcp '{"name":"mtd-chase","type":"http","url":"https://mtd-chase.smallwright.com/mcp"}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in. Codex takes hosted servers in config.toml ([mcp_servers.<name>] url = …) rather than on the command line.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Finance
Version
0.1.1
Registry
active
Published
11/13/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 22, 2026

Mostly fine: MTD Chase — chase clients for MTD records is maintained, hosted endpoint answering without a key.

Maintained
Active
Last commit 8 days ago (Nov 13, 2026), 0 open issues.
Official registry
Active
Published as com.smallwright/mtd-chase in the official MCP registry, version 0.1.1.
Source
No licence found
Public repository, but GitHub reports no recognised licence (0 stars). Check the README before shipping it in a product.
Runs
Hosted by the publisher
Your client talks to mtd-chase.smallwright.com: prompts and tool arguments leave your machine for that host.
Credentials
None needed to connect
The hosted endpoint completed the Serverdex initialize + tools/list handshake with no key (checked Nov 22, 2026); individual tools may still ask for one.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself and see the status history.

Live check

checked Nov 22, 2026, 05:09 UTCStatus history & uptime →
● Working253 msprotocol 2025-06-18v0.1.0resourcestools

The endpoint answered the MCP handshake as "mtd-chase" and listed 20 tools. Answering since Nov 18, 2026.

Context cost ≈ 5.6k tokens of tool definitions a client loads per conversation (estimate: characters ÷ 4) across 20 tools.

Tools (20)

  • get_mtd_deadlines1 param

    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).

    Show parameters
    • tax_yearstringe.g. "2026-27". Default: the current tax year.
  • 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.

  • update_practice9 params

    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.

    Show parameters
    • namestring
    • reply_to_emailstring
    • sign_offstring
    • phonestringUK phone number shown to Clients; empty clears it
    • ask_by_daysnumber0–30: days before the HMRC deadline that clients are asked to send by
    • retention_daysnumber30–365: days after the HMRC deadline that files are kept
    • daily_summaryboolean
    • default_checklistarray1–8 items, each up to 120 characters
    • idempotency_keystringOptional; reuse when retrying so the change happens once.
  • 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.

  • request_feature5 params

    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.

    Show parameters
    • what_the_user_wantedstringrequiredtheir own words
    • what_they_were_trying_to_achievestringrequiredthe job behind it
    • closest_existing_toolstring
    • urgencystringrequiredblocking = they can't do the job today; nice_to_have = a workaround exists
    • idempotency_keystringOptional; reuse when retrying so the change happens once.
  • 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).

  • 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.

  • add_clients3 params

    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).

    Show parameters
    • clientsarrayrequired
    • confirmbooleanfalse (default) = dry run: shows what would happen, changes nothing. true = do it.
    • idempotency_keystringOptional; reuse when retrying so the change happens once.
  • update_client8 params

    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).

    Show parameters
    • clientstringrequiredClient name, email or your own reference
    • namestring
    • emailstring
    • mobilestring
    • period_typestring
    • tagsarray
    • refstring
    • idempotency_keystringOptional; reuse when retrying so the change happens once.
  • archive_client4 params

    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.

    Show parameters
    • clientstringrequiredClient name, email or your own reference
    • unarchiveboolean
    • confirmbooleanfalse (default) = dry run: shows what would happen, changes nothing. true = do it.
    • idempotency_keystringOptional; reuse when retrying so the change happens once.
  • list_clients4 params

    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.

    Show parameters
    • textstringpart of a name or email
    • tagstring
    • period_typestring
    • include_archivedboolean
  • start_chase5 params

    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.

    Show parameters
    • quarterstringQuarter like "2026-27 Q3". Default: the Quarter whose HMRC deadline is next.
    • clientsrequired"all", or Client names/emails/tags
    • checklistarraywhat 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'
    • confirmbooleanfalse (default) = dry run: shows what would happen, changes nothing. true = do it.
    • idempotency_keystringOptional; reuse when retrying so the change happens once.
  • get_chase_links2 params

    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).

    Show parameters
    • quarterstringQuarter like "2026-27 Q3". Default: the Quarter whose HMRC deadline is next.
    • clientsarraynames/emails; default all being chased
  • mark_chase6 params

    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.

    Show parameters
    • clientstringrequiredClient name, email or your own reference
    • quarterstringQuarter like "2026-27 Q3". Default: the Quarter whose HMRC deadline is next.
    • statusstringrequired
    • notestring
    • recountbooleantrue = recount lateness from now
    • idempotency_keystringOptional; reuse when retrying so the change happens once.
  • list_records2 params

    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.

    Show parameters
    • quarterstringQuarter like "2026-27 Q3". Default: the Quarter whose HMRC deadline is next.
    • clientstringClient name, email or your own reference
  • set_nudge_plan4 params

    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).

    Show parameters
    • days_beforearray1–60, up to 6 values: days before the date clients are asked to send by
    • on_the_daybooleanalso nudge on the ask-by date itself
    • days_afterarray1–60, up to 6 values: days after it
    • idempotency_keystringOptional; reuse when retrying so the change happens once.
  • send_nudges_now5 params

    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.

    Show parameters
    • quarterstringQuarter like "2026-27 Q3". Default: the Quarter whose HMRC deadline is next.
    • clientsarrayClient names, emails or references; default: everyone outstanding
    • only_statusstringe.g. waiting = only those who've sent nothing
    • confirmbooleanfalse (default) = dry run: shows what would happen, changes nothing. true = do it.
    • idempotency_keystringOptional; reuse when retrying so the change happens once.
  • pause_nudges4 params

    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).

    Show parameters
    • clientstringrequiredClient name, email or your own reference
    • untilstringYYYY-MM-DD
    • resumeboolean
    • idempotency_keystringOptional; reuse when retrying so the change happens once.
  • whos_outstanding2 params

    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).

    Show parameters
    • quarterstringQuarter like "2026-27 Q3". Default: the Quarter whose HMRC deadline is next.
    • late_last_quarterbooleanonly those who were late last Quarter
  • get_client_history1 param

    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).

    Show parameters
    • clientstringClient name, email or your own reference

Checked by Serverdex with a plain initialize + tools/list call to mtd-chase.smallwright.com/mcp, no credentials, about once a day. A failed check is never a removal.

On GitHub

read Nov 21, 2026
Stars
0
Forks
0
Last push
Nov 13, 2026
License
—

accountantsbookkeepingchatgptclaudedocument-collectionhmrcmaking-tax-digitalmcpmcp-servermodel-context-protocolmtduk-accounting

From the README

MTD Chase MTD Chase is a records chaser for UK bookkeepers and small accountancy practices, run from their AI assistant: each client gets a personal no-login link for their Making Tax Digital quarterly records, reminders go out on their own, and you can ask who is still outstanding. MTD Chase is a remote MCP server. You add one address to Claude, ChatGPT, Cursor or any assistant that supports remote MCP servers, sign in once with an emailed link, and then ask in plain English. There is nothing to install. • Website: • MCP server: https://mtd-chase.smallwright.com/mcp (streamable HTTP, OAuth sign-in) • Price: Free for up to 5 clients; £19 a month for up to 75 clients (as of November 2026). MTD Chase does not file anything with HMRC and is not HMRC-recognised software. • Made by Smallwright, a small software studio (VINNYROO LLC). Support: support@smallwright.com Connect it Claude (claude.ai, desktop, mobile): Settings → Connectors → Add custom connector → paste the address → Connect, then sign in with the emailed link. ChatGPT: Settings → Apps & Connectors → Advanced settings → turn on Developer mode → Create → paste the address, choose OAuth → sign in. Cursor / VS Code / other MCP clients: add a remote server, for example in mcp.json: Step by step: Things to ask • "These are my MTD clients: …" • "Chase everyone for Q3, records by the 28th." • "Who's still outstanding?" • "When's the next MTD deadline?" (works before you sign in) FAQ What is MTD Chase?…

Read the full README on GitHub →

Remotes

  • streamable-httphttps://mtd-chase.smallwright.com/mcp

Alternatives to MTD Chase — chase clients for MTD records

All MTD Chase — chase clients for MTD records alternatives →Best Finance servers →

The most-starred Finance servers in the index, with their live-check result.

ServerStarsLast pushLive check
CCXT44,949Nov 2026Local / not checked
QR Rápido7,477Nov 2026Needs sign-in
Finance Toolkit5,554Nov 2026Needs sign-in
AKQuant2,627Nov 2026Local / not checked
com.stripe MCP2,072Nov 2026Needs sign-in

MTD Chase — chase clients for MTD records: questions people ask

Is MTD Chase — chase clients for MTD records a remote or a local MCP server?
According to its entry in the official MCP registry, MTD Chase — chase clients for MTD records ships as a hosted endpoint (streamable-http) that your client connects to by URL.
Does MTD Chase — chase clients for MTD records need an API key?
Its hosted endpoint completed the Serverdex live check — an MCP initialize + tools/list call — with no credentials on Nov 22, 2026. Individual tools may still ask for a key when called.
Is MTD Chase — chase clients for MTD records safe to use?
Mostly fine: MTD Chase — chase clients for MTD records is maintained, hosted endpoint answering without a key. In detail — maintained: Active; official registry: Active; source: No licence found; runs: Hosted by the publisher; credentials: None needed to connect. Serverdex check of Nov 22, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is MTD Chase — chase clients for MTD records still maintained?
Active: the repository's last commit 8 days ago. Last push Nov 13, 2026, 0 GitHub stars. Read from GitHub on Nov 21, 2026.
What tools does MTD Chase — chase clients for MTD records expose?
20 tools as listed by the server itself during the live check, including get_mtd_deadlines, get_started, update_practice, export_practice_data, request_feature. The full list with parameters is in the Live check section above.
How do I add MTD Chase — chase clients for MTD records to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
  1. Grommetbook — sign shop softwareSign shop software your AI runs: Price Book, Quotes customers approve, Jobs, website price box.
Browse all Finance →

Add the badge to your site

Show visitors that MTD Chase — chase clients for MTD records is listed here — it’s also the link we check for a free listing.

MTD Chase — chase clients for MTD records — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/com-smallwright-mtd-chase?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="MTD Chase — chase clients for MTD records — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![MTD Chase — chase clients for MTD records — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/com-smallwright-mtd-chase?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Add to CursorAdd to VS CodeOpen in Claude Code

Install buttons — for your README

[![Add to Cursor](https://serverdex.io/brand/install-cursor.svg)](https://serverdex.io/install/cursor/com-smallwright-mtd-chase) [![Add to VS Code](https://serverdex.io/brand/install-vscode.svg)](https://serverdex.io/install/vscode/com-smallwright-mtd-chase) [![Open in Claude Code](https://serverdex.io/brand/install-claude-code.svg)](https://serverdex.io/install/claude-code/com-smallwright-mtd-chase)

One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.

Install buttons — HTML for your docs

<a href="https://serverdex.io/install/cursor/com-smallwright-mtd-chase"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/com-smallwright-mtd-chase"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/com-smallwright-mtd-chase"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>

Same buttons as plain links for a docs page or website.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).