Skip to main content
Glama

fisc

Open-source MCP interoperability layer for professional Canadian tax software.

fisc gives AI agents a vendor-neutral interface for systems such as Taxprep, DT Max, and other professional tax packages through the Model Context Protocol.

Your AI agent
    ↓ MCP
   fisc
    ↓ vendor adapters
Taxprep · DT Max · ...

Why this exists

Canadian accounting firms already trust tax software that encodes years of tax rules, diagnostics, filing workflows, and review behaviour. Agents should not require firms to replace those systems or learn vendor-specific cell IDs.

fisc is the interoperability layer. Coalesc builds above it: engagement state, document intelligence, evidence, approvals, orchestration, review controls, and the reasoning that decides what should happen next.

Open the rails; compete on the workflow and intelligence.

Related MCP server: brasilnfe-mcp

Status

Early development. Do not use fisc to modify production tax returns yet.

The MCP contract supports T1, T2, T3, and T5013 as protocol return types. Only verified concept packs are published.

  • T1 — 30 concepts, each carrying a CRA line number.

  • T2 — 27 concepts keyed on GIFI, because a corporation's financial-statement data reaches the return through the General Index of Financial Information rather than through numbered lines. Labels are CRA's own from RC4088 in both languages, and every code was cross-checked against a real Corporate Taxprep export from a practising firm. 15 balance sheet, 12 income statement.

GIFI is also the join between this layer and papers: a balance read out of an engagement file and a cell written into a corporate return are the same concept when they carry the same code.

npm run verify asserts what type checking cannot — unique codes, the schedule matching the code's range, and French labels that are actually translated.

Taxprep is two products with one name, so there are two adapters.

Adapter

What it talks to

State

ifirm

CCH iFirm Taxprep, the cloud module, over the vendor's Web API

endpoints built from published documentation, never run against a live site

taxprep

Taxprep on the desktop, over the COM automation module

specified, no transport, every operation reports false

Neither should be pointed at a production return yet. The ifirm adapter can read and write cells where a verified cell map exists, and reports set_field and get_field as unsupported until one is loaded — the vocabulary is per-form and per-tax-year, and this repository ships none of it.

MCP tools

Tool

Purpose

get_capabilities

Report the configured adapter, the operations it supports per return type, and what the firm must hold to use it

list_concepts

List verified vendor-neutral concepts for a return type

create_return

Validate or create a tax return

set_field

Validate or write a semantic tax field with optional evidence provenance

get_field

Read a semantic tax field

list_forms

List forms in a return

list_returns

List returns visible to the configured adapter

get_diagnostics

Retrieve vendor validation diagnostics

Mutation tools default to validate rather than commit. An adapter must explicitly support a write operation before fisc should expose it as available.

Support is declared per return type, not per operation. An adapter whose only sanctioned write path is corporate reports set_field: ["t2"] — a single boolean would have forced it to either promise a T1 write it cannot perform or deny a real T2 one.

Safety model

MCP is an interface, not an authorization system. Production deployments must add controls around it.

Before enabling any vendor adapter, read docs/security.md — it covers the validate/commit boundary, why a SIN must never travel through a tool argument, where credentials belong, and the vendor-terms check that has to happen first.

  • Least privilege: use the narrowest vendor permissions available.

  • Validate before commit: writes should be previewed before they are applied.

  • Evidence provenance: material writes can carry a source document reference, page, and checksum.

  • No raw taxpayer secrets in agent prompts: use opaque internal taxpayer references instead of passing SINs through MCP tools.

  • Customer-controlled credentials: vendor credentials should remain in the environment authorized by the customer and vendor terms.

  • No credential sharing in this repository: secrets, tokens, customer data, and vendor SDK binaries do not belong in git.

  • Audit every production mutation: the application using fisc should record actor, engagement, evidence, requested action, approval, and vendor result.

Architecture

fisc separates semantic tax concepts from vendor integrations.

src/
  index.ts                 MCP server and safety defaults
  concepts/                verified vendor-neutral tax concepts
    t2.ts                   T2 concepts keyed on GIFI
  adapters/
    types.ts                common adapter contract, entitlements
    ifirm/                  CCH iFirm Taxprep (cloud, Web API)
    taxprep/                Taxprep desktop (COM), specified only
    dtmax/                  planned

An agent should work with concepts:

await client.callTool("set_field", {
  return_id: "return-123",
  tax_year: 2026,
  concept: "employment_income",
  value: 82400,
  evidence_source_id: "doc-456",
  evidence_page: 1,
  mode: "validate"
});

The adapter is responsible for translating that concept to a verified vendor-native field for the correct tax year.

Why open source

The interoperability contract should not be Coalesc's lock-in.

An open layer makes integrations inspectable, lets firms and vendors contribute adapters, reduces duplicate plumbing across the profession, and makes it easier to verify what an agent is allowed to ask tax software to do.

What is not part of this repository:

  • Coalesc's engagement orchestration and agent policies

  • customer-specific methodology and mappings

  • proprietary review logic and evals

  • customer credentials or data

  • vendor SDK code, binaries, or documentation that cannot legally be redistributed

Adapters are open only where vendor agreements permit it. A public adapter may expose an open contract while loading a separately licensed vendor SDK at runtime.

Vendor access

Each adapter must use a supported integration path and comply with the vendor's terms. Do not scrape professional tax software or bypass authentication controls just to make an adapter work.

Before enabling a vendor adapter in production, verify:

  1. the customer's license permits the integration;

  2. Coalesc is permitted to provide the integration commercially;

  3. the authentication and credential boundary is approved;

  4. multi-tenant use is permitted where applicable;

  5. SDK/API redistribution terms permit any code or artifacts included here.

Adapters declare these prerequisites as entitlements and refuse to start until the operator asserts them in FISC_ENTITLEMENTS. See docs/entitlements.md.

Two of those entitlements are about where fisc runs. Vendor agreements here routinely restrict who may hold a firm's account access information, so adapters are built to run in an environment the customer controls, with the credential read from that environment rather than transported to us.

Naming a vendor to say what an adapter talks to is descriptive. A logo, a "partner" claim, or any implication of certification or endorsement is not — those need the vendor's written permission, separately from permission to build the integration at all.

Contributing

Useful contributions include:

  • adapters for professional tax software;

  • verified T2, T3, T5013 and additional T1 concept mappings;

  • tax-year mapping updates;

  • conformance tests shared across adapters;

  • safer mutation, approval, and provenance patterns.

See CONTRIBUTING.md.

License

Apache License 2.0. Vendor APIs and SDKs remain subject to their own licenses and agreements.

Available Tools

8 tools
create_returnB

Create or validate creation of a tax return. Mutations default to validate-only.

Inputs: tax_year (required), return_type (required), taxpayer_ref (required), mode.

get_capabilitiesA

Describe the configured adapter and supported operations

Inputs: no named parameters.

get_diagnosticsC

Retrieve validation diagnostics for a return

Inputs: return_id (required).

get_fieldC

Read a tax field using a vendor-neutral concept

Inputs: concept (required), tax_year (required), return_id (required).

list_conceptsB

List verified vendor-neutral tax concepts for a return type

Inputs: return_type (required).

list_formsB

List forms in a tax return

Inputs: return_id (required).

list_returnsC

List tax returns visible to the configured vendor adapter

Inputs: tax_year, return_type.

set_fieldB

Set or validate a tax field using a vendor-neutral concept. Mutations default to validate-only.

Inputs: value (required), concept (required), tax_year (required), return_id (required), +5 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct operation: capabilities introspection, concept discovery, return creation, field reads/writes, form/return listing, and diagnostics. No two tools have overlapping responsibilities, so an agent can reliably select the right tool.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (get_, list_, create_, set_). The mix of get_ vs list_ for read operations is standard and distinguishes single-item retrieval from collection listing.

    Tool Count5/5

    Eight tools are well-scoped for the tax-return domain, covering discovery, creation, field manipulation, listing, and diagnostics. Each tool earns its place without unnecessary redundancy or bloat.

    Completeness4/5

    The set supports a validate-first workflow with creation, field access, listings, and diagnostics. It lacks explicit update/delete operations for returns, but set_field covers field-level mutation and deletion may be out of scope for this adapter.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      A sovereign, MIT-licensed MCP server for US tax operations, enabling offline-capable and self-hostable tax workflow management.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      MCP server that exposes Brazilian tax infrastructure as tools, resources, and prompts, enabling AI agents to emit and manage fiscal documents (NF-e, NFC-e, NFS-e, CT-e, MDF-e, DC-e) through natural language.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A standalone MCP server for Indian personal income-tax work (ITR-1/2/3/4 + post-filing notices) with 8 deterministic tools, running fully offline with no API keys.
      66 PyPI
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that connects AI agents to 34,500+ Australian Taxation Office documents, providing cited answers, tax deduction discovery, depreciation scheduling, BAS checklists, and audit risk assessment through 13 specialized tools.
      109 npm
      19
      AGPL 3.0