MTD Chase — chase clients for MTD records

Qué puedes hacer con él

Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.

• Conexión: Se ejecuta en la nube
• Transporte: Streamable HTTP
• Categoría: Contabilidad, finanzas e impuestos

Instalación

Elige la app de IA que usas y copia la configuración.

Necesitas

• Se ejecuta en la nubeNo hay nada que instalar; se conecta por internet

¿Qué app usas?

https://mtd-chase.smallwright.com/mcp

claude mcp add --transport http mtd-chase https://mtd-chase.smallwright.com/mcp

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

{
  "servers": {
    "mtd-chase": {
      "type": "http",
      "url": "https://mtd-chase.smallwright.com/mcp"
    }
  }
}

https://mtd-chase.smallwright.com/mcp

Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.

Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.

Qué puede hacer

Nombres y descripciones de las herramientas tal como los informó el servidor el 6 nov 2026. Los escribió el creador, no nosotros; los mostramos como texto sin formato.

• get_mtd_deadlines

  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 du

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

  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), h

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

  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 Ch

• 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 (req

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

  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.

• update_client

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

• archive_client

  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.

• list_clients

  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.

• start_chase

  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 chec

• get_chase_links

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

• mark_chase

  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 ar

• list_records

  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

• set_nudge_plan

  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 se

• send_nudges_now

  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: cha

• pause_nudges

  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

• whos_outstanding

  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, o

• get_client_history

  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 t

Revisiones básicasi

Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026

• ! Precaución

  El creador coincide con el repo

  El registro no indica ningún repo de código fuente, así que no podemos relacionar a quien lo publicó (smallwright.com) con el código

• … Aún sin revisar

  Sigue en mantenimiento

  Todavía no hemos leído este repo en GitHub

• … Aún sin revisar

  Tiene licencia

  Todavía no hemos leído este repo en GitHub

• ✓ Superada

  El endpoint responde

  Respondió en 237 ms (HTTP 200)

• – No aplica

  Inicio de sesión con OAuth

  No hace falta iniciar sesión

• ✓ Superada

  Sin instrucciones ocultas en las descripciones de herramientas

  Leímos 20 descripciones de herramientas y no encontramos instrucciones ocultas para la IA

Comparado con otros en Contabilidad, finanzas e impuestosi

• Más estrellas que el 0% de los otros 1720 servidores de esta categoría
• Publicado en el registro más recientemente que el 94% de los otros 1720 servidores de esta categoría
• Revisiones básicas iguales o mejores que el 43% de los otros 1720 servidores de esta categoría

Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.

Alternativas

Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.

Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi

README del creador

No se encontró un README en el repo