Skip to content
TaxComposer

Bookkeeping API and MCP

Add tax preparation to bookkeeping software with API and MCP

A useful tax integration starts with the records already in your product. TaxComposer can sit behind a structured application workflow, an assistant workflow, or both.

By TaxComposer · Updated · 2 min read

Use REST for a workflow your app controls

Use the REST contract when your application owns the screens, validation handling and job processing. Keep the preparation key on your server. Read the current OpenAPI document and endpoint-specific access requirements instead of assuming one key can perform every browser-owned action.

Start with capability discovery. A form being named in a catalog does not mean production submission is available, and one product environment may expose different blockers from another.

GET https://taxcomposer.com/openapi.json
GET https://taxcomposer.com/v1/returns/catalog

Source: TaxComposer API Documentation ↗

Use MCP when an assistant guides the work

Connect a compatible client to https://taxcomposer.com/agent/mcp using the supported account authorization flow. Discover tools for that connection and use the returned schemas. Tools in a different endpoint or authorization context may have different names and permissions.

TaxComposer’s hosted return tools use the taxcomposer_return_ prefix. Do not copy older iris_ tool names into a hosted OAuth example. The MCP protocol version must be negotiated with the server; a newer specification does not imply every new feature is implemented.

Source: TaxComposer MCP connections ↗

Build one reviewable sequence

Pull or import authorized vendor and paid-transaction records. Review candidate recipients, request missing W-9 information with permission, and reconcile the proposed reporting totals. Prepare a draft only after the business, recipient and amounts have been confirmed.

Retain the source references, draft ID, revision and hash. Display validation findings and unresolved rules in your own interface. Neither an assistant response nor a successful save is a filing acknowledgment.

Source: TaxComposer developer workflow guide ↗

Keep filing availability explicit

The current return workflow is preparation and testing, with production blockers exposed in results. For MeF returns, check the form’s capabilities for available mappings, validators and a qualified submission adapter. IRIS simulation is a separate, explicitly confirmed action.

A good integration lets the user resume the same draft without recollecting private information or accidentally creating a second filing. Build retries and status reconciliation into the first version.

Source: TaxComposer API Documentation ↗

Primary sources

Sources checked November 12, 2026. Use the instructions for your reporting year and circumstances.

Your next step

Connect your bookkeeping workflow.

Use the current API contract and discover the tools available to your MCP connection.

API Documentation →Connect with MCP →

TaxComposer is production-ready for IRS IRIS e-filing. Prepare for free and pay $1 per form when you file.