Probate help for US executors: county courts, court forms, bank guides, and your estate checklist.
Connect Remote server
claude mcp add --transport http probate https://www.swiftprobate.com/api/mcp/estate
{
"mcpServers": {
"probate": {
"url": "https://www.swiftprobate.com/api/mcp/estate"
}
}
}
{
"servers": {
"probate": {
"type": "http",
"url": "https://www.swiftprobate.com/api/mcp/estate"
}
}
}
Settings > Connectors > Add custom connector
URL: https://www.swiftprobate.com/api/mcp/estate
Tools 34 found in our last check
list_my_estatesList the estates the signed-in SwiftProbate user can work with: estates they own plus estates someone has shared with them as a collaborator. SwiftProbate is probate task-management software that helps executors and families organize and track the probate process. This tool requ…
complete_onboardingSet up a new estate for the signed-in SwiftProbate user and start generating their personalized probate checklist. SwiftProbate is probate task-management software that helps executors and families understand and organize the steps of settling an estate; the checklist is general…
show_estate_setupShow the signed-in user a short form, right in the chat, for setting up their estate in SwiftProbate. Submitting it builds their personalized probate checklist (the same as complete_onboarding, without asking the questions one by one). Use this when the user agrees to set up an…
show_my_tasksShow 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 to five tasks with due dates, which ones are overdue, and which are waiting on another task. Users who can edit the estate can tick a task…
lookup_county_guideLook up SwiftProbate's published probate guide for one specific US county. SwiftProbate is probate task-management software that helps people understand and organize the probate process; this tool returns general reference information, not legal advice, and SwiftProbate is not a…
lookup_institution_guideLook up SwiftProbate's estate-notification guide for one financial institution: banks, credit unions, brokerages, retirement-plan providers, life insurers, and similar companies. It helps an executor or family member understand how that institution handles a death notification a…
find_probate_formsFind the probate court forms SwiftProbate has catalogued for a US state, optionally narrowed to one county and/or keywords. It helps the user see which forms exist for their jurisdiction and where to get the official versions. SwiftProbate is probate task-management software, no…
get_state_overviewGet SwiftProbate's high-level probate reference facts for one US state. It helps the user understand the shape of probate in that state (thresholds, deadlines, typical timeline) as general information from probate task-management software. It is not legal advice; SwiftProbate is…
searchSearch SwiftProbate's probate reference data (US state overviews, county probate court guides, financial-institution estate-notification guides, and court-form listings) with one free-text query. This is one half of a search/fetch pair: search returns short result items, and you…
fetchFetch the full SwiftProbate reference record for an id returned by `search` (a state overview, county court guide, institution notification guide, or a jurisdiction's forms).
get_estate_summaryGet a summary of the estate including details, assets, heirs, and task statistics. Use this when the user asks about the estate overview or general status.
get_tasksList the tasks in one estate's probate checklist, in the same order the user sees on their SwiftProbate dashboard. SwiftProbate is probate task-management software that helps executors organize and track the steps of settling an estate; tasks are general guidance, not legal advi…
get_task_detailGet full details of a specific task by ID, including its description, status, priority, deadline, notes, and linked documents.
get_assetsList 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 full set fresh (e.g. right after creating or updating one) or the context block was truncated. For one asset's linked tasks, use get_asset_de…
get_asset_detailGet 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 need details beyond what the Assets context block shows. Get the asset_id from that context block.
get_heirsList every recorded heir with relationship and details. The Heirs context block already lists them, so call this only to refresh after adding or updating an heir, or when that block was truncated.
get_transactionsRead the estate's financial ledger — money in (receipts), money out (disbursements), and distributions to heirs. Returns: `transactions` (each with `paid_by` already resolved to the actual payer's NAME — use it as-is, never assume the executor paid — plus its linked `asset_id`,…
get_documentsList the estate's uploaded documents, optionally filtered by asset or task. Your Documents context block already lists them, so call this only to refresh after an upload or to filter to a specific asset's or task's documents. To read a document's contents, use read_document inst…
get_activity_logGet the estate's recent activity-log entries (who changed what, and when). Each entry has `who` (the person, and whether they're the owner or a collaborator) and `via` (the SwiftProbate app, Grace, or ChatGPT acting for them). Call this when the user asks what has changed recent…
create_taskCreate a new task in the estate. Use this when the user identifies a new requirement or action item that should be tracked.
edit_taskEdit an existing task's title, description, priority, deadline, category, or helpful links. Use when the user wants to modify task details.
update_task_statusUpdate 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_applicable (not required) is the customer's decision: only do it when they have said so, and pass their words in customer_words. To restore a task m…
update_task_notesSet or update the user notes on a task. Use this when the user wants to add notes to a task.
update_task_deadlineSet or clear a task's deadline. Use this when the user wants to set a due date.
assign_taskAssign 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 "People on this estate" (a first name works when it's unique); the result says who it was assigned to, or why it couldn't be (pending invite,…
create_assetCreate 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 debt the estate owes. A same-named asset does NOT block creation (two accounts at the same institution are legitimate) — but if you create…
update_assetUpdate an existing asset's details (name, type, value, jurisdiction, notes, etc.). Use this instead of creating a duplicate when the user wants to modify an asset — including when it was saved under the wrong type: change asset_type here rather than deleting and recreating it, w…
mark_assets_completeRecord that the user has finished telling you about the estate's assets. Call this the moment they say there is nothing else — "that's everything", "that's the only asset", "nothing else to add". This is what turns "Has real property" and the estate size in your Estate Context f…
log_transactionRecord a financial transaction in the estate ledger when the user mentions money moving — an expense they paid, income the estate received, a debt payment, or a distribution to an heir. Examples: "I paid $4,200 for the funeral", "the estate got a $1,300 tax refund", "my brother…
update_transactionCorrect an existing ledger transaction when the user wants to fix a mistake — a wrong amount, date, category, payee, who paid, or which heir/asset it relates to. Find the transaction's ID with get_transactions first. This is a PARTIAL update: pass transaction_id plus ONLY the fi…
create_heirAdd a new heir to the estate. Use when the user wants to record a person who may inherit (spouse, child, stepchild, grandchild, parent, sibling, or other relative). Call once the customer has confirmed how the person is related to the DECEASED — any wording is accepted. "My brot…
update_heirUpdate 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-loaded Heirs context block.
mark_heirs_completeRecord 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 children", "there's no spouse", "that's all the heirs". This is what turns "Surviving spouse" and "Minor children" in your Estate Context…
update_estateUpdate high-level estate details that the user can correct after onboarding. Use this when the user mentions a fact that should be persisted (e.g. "actually there is a will", "the will is in the safe deposit box", "the case number is 2026-001234"). NOT for who the heirs are or w…
Details
| Endpoint | https://www.swiftprobate.com/api/mcp/estate (Streamable HTTP) |
| First published | 11 Oct 2026 |
| Last updated | 11 Oct 2026 |
| Registry name | com.swiftprobate/probate |
More productivity servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
