create_heir — SwiftProbate MCP Tool Mutating
create_heir
(create heir) is one of 32 tools on the
SwiftProbate
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call create_heir from your client
- Claude Code SwiftProbate create_heir run in your project directory
- Claude Desktop SwiftProbate create_heir ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor SwiftProbate create_heir ~/.cursor/mcp.json
- VS Code SwiftProbate create_heir .vscode/mcp.json
- Zed SwiftProbate create_heir ~/.config/zed/settings.json
- Windsurf SwiftProbate create_heir ~/.codeium/windsurf/mcp_config.json
- Cline SwiftProbate create_heir ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI SwiftProbate create_heir ~/.gemini/settings.json
- Grok SwiftProbate create_heir .mcp.json (in your project root)
- ChatGPT SwiftProbate create_heir Settings → Connectors → Advanced → Developer mode
- Claude.ai SwiftProbate create_heir Settings → Connectors → Add custom connector
- LangChain SwiftProbate create_heir pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http probate https://www.swiftprobate.com/api/mcp/estate
Other tools on this server
- list_my_estates
- complete_onboarding
- lookup_county_guide
- lookup_institution_guide
- find_probate_forms
- get_state_overview
- search
- fetch
- get_estate_summary
- get_tasks
- get_task_detail
- get_assets
- get_asset_detail
- get_heirs
- get_transactions
- get_documents
- get_activity_log
- create_task
- edit_task
- update_task_status
- update_task_notes
- update_task_deadline
- assign_task
- create_asset
- update_asset
- mark_assets_complete
- log_transaction
- update_transaction
- update_heir
- mark_heirs_complete
- update_estate
This list was read from the server itself, by connecting to it and calling tools/list on 11 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.