calculate_net_salary — Refnusa MCP Tool
calculate_net_salary
(calculate net salary) is one of 32 tools on the
Refnusa
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call calculate_net_salary from your client
- Claude Code Refnusa calculate_net_salary run in your project directory
- Claude Desktop Refnusa calculate_net_salary ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Refnusa calculate_net_salary ~/.cursor/mcp.json
- VS Code Refnusa calculate_net_salary .vscode/mcp.json
- Zed Refnusa calculate_net_salary ~/.config/zed/settings.json
- Windsurf Refnusa calculate_net_salary ~/.codeium/windsurf/mcp_config.json
- Cline Refnusa calculate_net_salary ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Refnusa calculate_net_salary ~/.gemini/settings.json
- Grok Refnusa calculate_net_salary .mcp.json (in your project root)
- ChatGPT Refnusa calculate_net_salary Settings → Connectors → Advanced → Developer mode
- Claude.ai Refnusa calculate_net_salary Settings → Connectors → Add custom connector
- LangChain Refnusa calculate_net_salary pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http refnusa https://refnusa.dev/mcp
Other tools on this server
- list_datasets
- get_holidays
- check_holiday
- get_ump
- get_ump_history
- get_umk
- get_umk_history
- get_wilayah
- get_postal_code
- reverse_postal_code
- get_pph21_ter
- get_ptkp
- get_prayer_times
- get_bpjs_rates
- get_bank_codes
- get_fuel_prices
- list_food_commodities
- get_food_prices_latest
- get_food_price_series
- get_passport_fees
- search_kbli
- get_kbli
- get_tax_rates
- get_ojol_tariffs
- get_zakat
- get_het_prices
- list_stat_indicators
- get_stat_values
- get_stat_series
- validate_nik
- validate_plate
This list was read from the server itself, by connecting to it and calling tools/list on 18 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.