BoomTax

What BoomTax MCP server does

The BoomTax MCP server gives MCP-compatible AI clients read-only access to filing data in BoomTax. It can find filings by tax year, form type, or status; return filing details and summaries; inspect forms; list payers; and review electronic filing activity. Results are scoped to the authenticated BoomTax account and the filing permissions associated with it.

The available operations are designed for lookup and investigation. They do not create, update, delete, or submit filings. Payer results include a masked payer TIN, while other returned data may contain confidential names, contact details, and filing information.

How it works

The hosted service is available at https://api.boomtax.com/mcp using Streamable HTTP and OAuth with PKCE. Clients authenticate through the browser, using OAuth discovery and Dynamic Client Registration when supported. A request to the endpoint without authentication can return 401; that response is expected and is not, by itself, evidence that the service is unavailable.

A local client is also available from the repository. It forwards the ten read-only tools to the hosted BoomTax service and obtains short-lived OAuth tokens from configured API credentials. Token renewal occurs when needed. The local client requires Node.js 22 or newer and uses HTTPS for non-loopback origins.

Setup and configuration

For the remote connection, add https://api.boomtax.com/mcp in an MCP client that supports Streamable HTTP and OAuth with PKCE, then complete the browser sign-in. BoomTax API access must be enabled on the account. OAuth client registration should use Dynamic Client Registration; Client ID Metadata Documents are not currently supported.

For a local installation, create a read-scoped BoomTax API credential, clone the repository, run npm ci, and start it with node index.js. Set BOOMTAX_CLIENT_ID and BOOMTAX_CLIENT_SECRET. BOOMTAX_API_URL is optional and defaults to https://api.boomtax.com; provide an origin rather than the /mcp path. Keep credentials out of source control and revoke unused credentials in BoomTax.

The hosted endpoint can be configured in Claude Desktop, Claude Code, ChatGPT workspaces that permit custom MCP connections, Codex, Cursor, Windsurf, and VS Code with GitHub Copilot. Remote configurations contain no account secrets; local configurations should inject credentials through secure environment settings.

Tools and capabilities

The ten available tools are:

• list_filings: filter filings by year, form type, and status, including filing system
• get_filing_details: retrieve filing details, payer information, and e-file status
• get_filing_summary: count filings by status and form type
• list_filing_forms: browse paginated form metadata within a filing
• get_form: inspect form metadata, status, and dates
• get_efile_status: review the e-file request and response timeline
• get_efile_errors: retrieve e-file errors and messages
• list_payers: list payers across accessible filings
• get_payer: retrieve payer details with a masked payer TIN
• list_filing_types: check available filing types, tax years, and filing systems

Use list_filing_types when checking current form availability, since available forms can change by tax year.

Limitations and notes

The BoomTax MCP server is read-only, so it is not suitable for workflows that must prepare, change, or submit filings. Access depends on the authenticated account and its permissions. Local startup problems can result from missing credentials, disabled API access, or an unreachable API. Legacy username and password variables are not supported by the current local client.

BoomTax's hosted service remains subject to its service terms and account permissions, while the local client source is MIT licensed. Treat returned filing and payer information as confidential and share it only with authorized assistants.