The federal cap on deducting state and local tax
One command on the State and local tax server, callable over MCP as get_salt_capabilities. Every result carries the method it used, the rule pack it was pinned to, what is still missing and whether coverage was complete, for a licensed professional to review.
What it needs, and why
This command takes no arguments: it reports what the server covers. Which calculators taxagent-salt exposes, what it will not compute, and the rule pack its figures are pinned to. Reading the registry before promising anything is the difference between a refusal and a plausible wrong answer.
Requests it answers
- “What does this server know about state tax?”
- “Which state packs are bound in this deployment?”
An agent with these skills loaded picks the command from phrasing like that, asks for whatever input is missing, and reports the figures with the method that produced them.
Run it
scripts/mcp_server.sh --server saltThe same command is exposed by taxagent-salt, so Claude, Claude Code, Codex, Cursor and any other MCP client can call it directly. Analysis only. No tool in this server places orders, modifies custodian records or files returns. This server holds no client data: every figure arrives in the call and nothing is stored. Results are estimates over those figures, not a return and not tax advice. No state's own income tax is computed. No state pack is bound in this deployment, and the cap limits a federal deduction rather than telling you what a state charges.
Limits it inherits from taxagent-salt
- Any state's own income tax. No state pack is bound in this deployment, and the cap is a federal deduction limit, not what a state charges.
- Residency, domicile, part-year allocation and reciprocity.
- Pass-through entity tax workarounds, which are a state question.
- Whether itemizing beats the standard deduction at all.
The server, its other 2 commands and what it deliberately leaves alone are on the State and local tax page.