English Français العربية

Tax Regulations

Official registry Government and legal

Tax Regulations MCP — US Treasury / IRS regulations (26 CFR, 'Treas. Reg.').

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http tax-regulations 'https://gateway.pipeworx.io/tax-regulations/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "tax-regulations": {
            "type": "http",
            "url": "https://gateway.pipeworx.io/tax-regulations/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. mcp-tax-regulations
  2. Tools
  3. Quick Start
  4. No MCP client? Call it over HTTP
  5. Standalone (no gateway account)
  6. Using with ask_pipeworx
  7. More
  8. License

mcp-tax-regulations

Tax Regulations MCP — US Treasury / IRS regulations (26 CFR, 'Treas. Reg.').

Part of Pipeworx — an MCP gateway connecting AI agents to 1679+ live data sources.

Tools

ToolDescription
tax_regulationGet the full text of one Treasury Regulation / IRS regulation — a US federal tax regulation codified in 26 CFR — by its citation. Returns the exact regulatory wording currently in force. Answers "what does Treas. Reg. 1.170A say", "what is the IRS regulation for X", "the Treasury Regulation on X", "read 26 CFR 1.61-1", "the income tax regulation for X". Forgiving citation input: "1.170A-1", "26 CFR 1.61-1", "Treas. Reg. 1.501(c)(3)-1", "§1.170A-1", even "1.170A-1(b)" (trailing paragraph stripped). Tax citations are dotted — the part is the number BEFORE the first dot: "1.170A-1" -> part 1, section 170A-1; "301.7701-1" -> part 301. Covers 26 CFR part 1 income tax regulations (gross income, deductions, credits, charitable contributions 1.170A, exempt organizations 1.501(c)(3)-1, depreciation, capital gains), part 301 procedure & administration, parts 20 & 25 estate & gift tax, part 31 employment tax — the whole of Title 26. Pass a whole part (e.g. "1") to get a (large) section list. Example: tax_regulation({ citation: "1.170A-1" }) -> charitable contribution deduction; tax_regulation({ citation: "Treas. Reg. 1.61-1" }) -> gross income defined. Keyless.
tax_searchKeyword search across federal tax regulations — US Treasury / IRS regulations in 26 CFR. Answers "what tax regulations cover X", "the IRS regulation / Treasury Regulation about X", "find the federal tax rule for X". Great for topics: charitable contribution deduction, gross income, business expense deduction, depreciation and MACRS, capital gains and losses, section 501(c)(3) exempt organizations, S corporations, partnerships, like-kind exchanges, employment tax, estate and gift tax, foreign tax credit, retirement plans. Returns matching Treasury Regulations with citation (26 CFR / Treas. Reg.), heading, excerpt, and source URL. Example: tax_search({ query: "charitable contribution deduction" }); tax_search({ query: "depreciation", limit: 15 }). Keyless.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "tax-regulations": {
      "url": "https://gateway.pipeworx.io/tax-regulations/mcp"
    }
  }
}
What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/tax-regulations/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1679+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/tax_regulation \
  -H 'Content-Type: application/json' \
  -d '{"citation":"1.170A-1"}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/tax_regulation. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "tax-regulations": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-tax-regulations"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-tax-regulations

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Tax Regulations data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Frequently asked questions

What is Tax Regulations?

Tax Regulations MCP — US Treasury / IRS regulations (26 CFR, 'Treas. Reg.').

How do I install Tax Regulations?

It runs as a remote server. In Claude Code: claude mcp add --transport http tax-regulations 'https://gateway.pipeworx.io/tax-regulations/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Tax Regulations need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Tax Regulations open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Tax Regulations?

It is published by pipeworx-io. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.