KitScout

Categories › Business & Finance › Legal & compliance documents

SwiftProbate

MCP serverVerified domain · swiftprobate.comRemote● LiveFree to try

Probate help for US executors: county courts, court forms, bank guides, and your estate checklist.

Install

Remote server: your requests and data go to www.swiftprobate.com. Claude Code: claude mcp add --transport http swiftprobate https://www.swiftprobate.com/api/mcp/estate · Claude app: Settings → Connectors → Add custom connector.

What it can do

The tools this server listed when we connected to it, in its own words.

  • list_my_estates — List the estates the signed-in SwiftProbate user can work with: estates they own plus estates someone has shared with them as a collaborator
  • complete_onboarding — Set up a new estate for the signed-in SwiftProbate user and start generating their personalized probate checklist. SwiftProbate is probate t
  • show_estate_setup — Show the signed-in user a short form, right in the chat, for setting up their estate in SwiftProbate. Submitting it builds their personalize
  • show_my_tasks — Show the signed-in user's next open tasks for one estate as a card in the chat: the same Up Next list their SwiftProbate dashboard shows, up
  • lookup_county_guide — Look up SwiftProbate's published probate guide for one specific US county. SwiftProbate is probate task-management software that helps peopl
  • lookup_institution_guide — Look up SwiftProbate's estate-notification guide for one financial institution: banks, credit unions, brokerages, retirement-plan providers,
  • find_probate_forms — Find the probate court forms SwiftProbate has catalogued for a US state, optionally narrowed to one county and/or keywords. It helps the use
  • get_state_overview — Get SwiftProbate's high-level probate reference facts for one US state. It helps the user understand the shape of probate in that state (thr
  • search — Search SwiftProbate's probate reference data (US state overviews, county probate court guides, financial-institution estate-notification gui
  • fetch — Fetch the full SwiftProbate reference record for an id returned by `search` (a state overview, county court guide, institution notification
  • get_estate_summary — Get a summary of the estate including details, assets, heirs, and task statistics. Use this when the user asks about the estate overview or
  • get_tasks — List the tasks in one estate's probate checklist, in the same order the user sees on their SwiftProbate dashboard. SwiftProbate is probate t
  • get_task_detail — Get full details of a specific task by ID, including its description, status, priority, deadline, notes, and linked documents.
  • get_assets — List every asset in the estate with its type and value. Your Estate Context already lists the assets, so call this only when you need the fu
  • get_asset_detail — Get one asset's full details plus the tasks linked to it, by asset ID. Call this when the user asks about a specific asset's tasks or you ne
  • get_heirs — List every recorded heir with relationship and details. The Heirs context block already lists them, so call this only to refresh after addin
  • get_transactions — Read the estate's financial ledger — money in (receipts), money out (disbursements), and distributions to heirs. Returns: `transactions` (ea
  • get_documents — List the estate's uploaded documents, optionally filtered by asset or task. Your Documents context block already lists them, so call this on
  • get_activity_log — Get the estate's recent activity-log entries (who changed what, and when). Each entry has `who` (the person, and whether they're the owner o
  • create_task — Create a new task in the estate. Use this when the user identifies a new requirement or action item that should be tracked.
  • edit_task — Edit an existing task's title, description, priority, deadline, category, or helpful links. Use when the user wants to modify task details.
  • update_task_status — Update a task's status. Use this when the user asks to mark a task as completed, in progress, etc. Marking a task completed or not_applicabl
  • update_task_notes — Set or update the user notes on a task. Use this when the user wants to add notes to a task.
  • update_task_deadline — Set or clear a task's deadline. Use this when the user wants to set a due date.
  • assign_task — Assign a task to the estate owner or a collaborator who has accepted their invite. Pass assignee_name with the person's name as listed in "P
  • create_asset — Create a new asset in the estate. Use this when the user wants to add a bank account, property, vehicle, insurance policy, other asset, or a
  • update_asset — Update an existing asset's details (name, type, value, jurisdiction, notes, etc.). Use this instead of creating a duplicate when the user wa
  • mark_assets_complete — Record that the user has finished telling you about the estate's assets. Call this the moment they say there is nothing else — "that's every
  • log_transaction — Record a financial transaction in the estate ledger when the user mentions money moving — an expense they paid, income the estate received,
  • update_transaction — Correct an existing ledger transaction when the user wants to fix a mistake — a wrong amount, date, category, payee, who paid, or which heir
  • create_heir — Add a new heir to the estate. Use when the user wants to record a person who may inherit (spouse, child, stepchild, grandchild, parent, sibl
  • update_heir — Update an existing heir's details. Use when the user wants to correct or add information to a recorded heir. Get the heir_id from the pre-lo
  • mark_heirs_complete — Record that the user has finished telling you about the estate's heirs and family. Call this the moment they say that's everyone — "no other
  • update_estate — Update high-level estate details that the user can correct after onboarding. Use this when the user mentions a fact that should be persisted

KitScout test notes

Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.

Similar tools