calculate_shared_expenses — Partly Exact Split MCP Tool
calculate_shared_expenses
(calculate shared expenses) is one of 1 tool on the
Partly Exact Split
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call calculate_shared_expenses from your client
- Claude Code Partly Exact Split calculate_shared_expenses run in your project directory
- Claude Desktop Partly Exact Split calculate_shared_expenses ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Partly Exact Split calculate_shared_expenses ~/.cursor/mcp.json
- VS Code Partly Exact Split calculate_shared_expenses .vscode/mcp.json
- Zed Partly Exact Split calculate_shared_expenses ~/.config/zed/settings.json
- Windsurf Partly Exact Split calculate_shared_expenses ~/.codeium/windsurf/mcp_config.json
- Cline Partly Exact Split calculate_shared_expenses ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Partly Exact Split calculate_shared_expenses ~/.gemini/settings.json
- Grok Partly Exact Split calculate_shared_expenses .mcp.json (in your project root)
- ChatGPT Partly Exact Split calculate_shared_expenses Settings → Connectors → Advanced → Developer mode
- Claude.ai Partly Exact Split calculate_shared_expenses Settings → Connectors → Add custom connector
- LangChain Partly Exact Split calculate_shared_expenses pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http exact-split https://partly-exact-split.paul-brousses.workers.dev/mcp
This list was read from the server itself, by connecting to it and calling tools/list on 11 November 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.