
PolyAccounts accounting
io.github.andrewblountPublished by GitHub account andrewblountv1.0.2Updated Oct 24, 2026
Company-scoped accounting reads, writes and workflows. Supervised synthetic evaluation only.
Overview
Lets an assistant read, create, update and soft-delete company-scoped accounting records, or explore a synthetic demo company.
- What you can do
- PolyAccounts exposes company-scoped accounting reads, writes and documented workflows such as expense review, financial review, month-end close and trust reconciliation. Tools include accounting_context, expense_changes, ledger_entries and profit_loss, with stable evidence IDs and exact decimal arithmetic. Writes use revisions, idempotency keys and durable receipts, and soft deletion preserves history. A read-only synthetic demo with four tools and two review prompts is also included.
- When to use it
- Use it to evaluate agent-driven accounting workflows against a synthetic sandbox company or an approved workspace, for example reviewing expense changes or tracing ledger evidence. It is intended for supervised synthetic evaluation, not for real customer books or statutory accounting.
- Requirements
- Node.js 20 or later for the stdio connector, or an MCPB-compatible desktop client for the demo. The hosted connector needs a company credential issued by an administrator, supplied through the extension's sensitive configuration field or the POLYACCOUNTS_TOKEN_FILE environment variable. The remote option uses Streamable HTTP with OAuth 2.1 and one administrator approval. The demo needs no account, API key or network connection.
Installation
In SourceWeft
- Open PolyAccounts accounting in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
PolyAccounts agent kit
Accounting for companies that work with AI agents.
Evaluate exact balances and traceable ledger evidence before connecting a company. This repository contains only public connector code and invented demonstration data.
PolyAccounts is in early access. Evaluate with synthetic data in a sandbox or an approved workspace. Do not use this release for real customer books or statutory accounting. Reads are not metered. Limits and quotas: https://polyaccounts.com/limits.
Workflows
Reusable, model-agnostic procedures in workflows/: expense review,
financial review, matter billing cycle for law
firms, month-end close, and trust three-way
reconciliation.
Install the demo
Download polyaccounts-demo.mcpb and open it in an MCPB-compatible client. For Claude Desktop, use Settings, Extensions, Advanced settings, Install Extension. Review the extension before installing. No account, database, API key or network connection is needed after installation.
For a stdio client, use this pinned configuration.
Windows clients that cannot launch npx directly can install the package once and
configure node with the absolute path to demo.mjs. Client settings differ.
Ask a useful question
What changed in expenses this month? Show the entries.
The synthetic company is Juniper Studio. Its clock is August 31, 2026. “This month” always means August compared with July, regardless of today's date. Expenses rise from USD 1200.0000 to USD 1850.0000, a USD 650.0000 change. Software accounts for 500.0000 and fees for 150.0000. Workspace costs do not change.
Use accounting_context, expense_changes and ledger_entries. Each category
includes stable evidence IDs. profit_loss includes both sides of postings.
The fixture uses exact integer arithmetic and returns decimal strings.
Run the working example without a model or external service.
The example starts the real MCP stdio process, retrieves the report and verifies all seven expense entries through the connection. It fails if an evidence ID is missing or the expected change does not reconcile. Inspect the evidence in a browser.
Connect with full accounting access
Download polyaccounts-hosted.mcpb for the hosted connector. In an approved workspace, an administrator opens Settings, For AI agents, and issues a company credential. Enter it in the extension's sensitive configuration field. The client can read and write that company's accounting data.
Or run the included standalone bridge with a protected token file.
Keep credentials out of prompts, logs, screenshots, source control and issue reports. Use operating-system file permissions or a secret manager. The hosted bridge talks only to the configured HTTPS API and refuses redirects. Credentials can be revoked.
Start with accounting_context and confirm the company. Discover tools and operation
schemas before acting. Record updates use revisions. Every write uses one stable
idempotency key and a durable receipt. An uncertain result must be reconciled before
trying a different action. Soft deletion preserves history. Approval, period and
payment controls still apply. Recording a payment does not move bank funds.
The demo-only expense_changes tool is not in the hosted catalog. For hosted expense
reviews, retrieve both periods and every ledger page, then aggregate exact values.
Do not sum rounded display amounts or infer business causes without evidence.
- Full setup and accounting contract
- Generated hosted tools
- Supported workflows
- Expense review workflow
- Financial review workflow
- Early-access pricing
- Request an integration evaluation
Privacy Policy
The demo reads only its bundled fixture, makes no network calls and writes no files. The hosted connector sends requested accounting operations to the company API and returns results to your chosen client. That client or its model provider may process the results under its own terms. Review the PolyAccounts privacy policy. Support issues must contain only synthetic examples. Report credential or security issues privately to [email protected], not in a public GitHub issue.
The demo stores no accounting inputs or usage data and has no telemetry. Its fixture is bundled in the installation. Your MCP client may retain conversations according to its own settings. The hosted service retains company records and write receipts under its privacy policy. Contact [email protected] with privacy requests.
This kit is MIT licensed. The license covers this repository, not the hosted service. Directory acceptance and recommendations are not guaranteed.
Source: README.md at commit 270046b
Tools
0Version history
1- v1.0.2LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts