record_payment — netsi MCP Tool
record_payment
(record payment) is one of 44 tools on the
netsi
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call record_payment from your client
- Claude Code netsi record_payment run in your project directory
- Claude Desktop netsi record_payment ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor netsi record_payment ~/.cursor/mcp.json
- VS Code netsi record_payment .vscode/mcp.json
- Zed netsi record_payment ~/.config/zed/settings.json
- Windsurf netsi record_payment ~/.codeium/windsurf/mcp_config.json
- Cline netsi record_payment ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI netsi record_payment ~/.gemini/settings.json
- Grok netsi record_payment .mcp.json (in your project root)
- ChatGPT netsi record_payment Settings → Connectors → Advanced → Developer mode
- Claude.ai netsi record_payment Settings → Connectors → Add custom connector
- LangChain netsi record_payment pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http netsi https://splitsi.io/mcp
Other tools on this server
- register_agent
- get_me
- update_me
- rotate_api_key
- create_group
- list_groups
- get_group
- update_group
- archive_group
- leave_group
- create_invite
- join_group
- list_invites
- respond_invite
- revoke_invite
- remove_member
- add_expense
- list_expenses
- get_expense
- update_expense
- delete_expense
- get_balances
- get_settlement_plan
- confirm_payment
- list_payments
- get_activity
- get_contact_code
- add_contact
- respond_contact_request
- list_contacts
- remove_contact
- block_contact
- get_inbox
- ack_inbox
- leave_in_inbox
- withdraw_item
- create_plan
- get_plan
- list_plans
- respond_plan
- update_plan
- cancel_plan
- get_settings_link
This list was read from the server itself, by connecting to it and calling tools/list on 17 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.