ATLASS OS

ATLASS OS is a business platform for construction trades — CRM, scheduling, jobs, and real double-entry books in one ledger — with a native MCP surface.

Surface census: 2026-08-10. This page is updated from the census, never by hand.

One connection, one audited ledger. Your agent works across:

Every write is tenant-scoped, and everyfinancialwrite posts as balanced double-entry with a record on an append-only audit log.

The part nobody else built: the security shape

MCP tools are becoming table stakes.How the keys work is the product.

- Tokens are minted in-app, and you can only hand an agent permissions you already hold yourself.No developer account, no OAuth playground, no local server process. Granting an agent payments, payables or tax filing takes an owner or admin.
- 32 permission scopes, grouped by job.Give your bookkeeping agent the books and nothing else. Reads without writes. Revoke in-app, instantly — checked on every single call, with nothing cached.
- Every call runs as the person who minted the token, in a fresh server-side session — an agent can never exceed that person's own access. On the money, books, payroll and inventory tools, permissions are re-checked against the live role on every call, so demoting someone takes effect immediately. A small set of general-purpose tools (inbox, outreach, support) are session-level only — revoke the token to cut those off.
- Server-enforced money math.Balanced-entry rules, books locks, audit records, and duplicate guards on bill payments, bank imports and tax filings — enforced on our servers, not by an env var on a process you're trusted to run.
- No payment rail, by design.Nothing in ATLASS — agent or human — moves a dollar of your money. The payment tools record money that moved elsewhere. And an agent can never mint a token or change anyone's permissions: those endpoints are not on the tool surface at all.

A books-only connector leaves your agent blind to the business: the job, the crew, the site, the customer thread. In ATLASS the agent that books the job is the same agent that watches the invoice get paid — one ledger, nothing to sync, every action audited in one place.

As of August 10, 2026, no major field-service platform ships an official MCP surface.We checked, with citations. We’d love to be second-guessed on this.

Every tool surface is tested against a deliberately brutal bar:a small, cheap AI model must complete real bookkeeper tasks from the tool descriptions alone— no custom prompts, no hand-holding — and the books it produces are verified against an accountant-written expectation. If the cheapest model can’t do it, we treat that as OUR defect, not the AI’s.

The payables and receivables suites currently in build go through the same gauntlet. This page’s numbers change only when the census does.

ATLASS OS is in founding-stage rollout in Alberta, Canada.

Built by a roofing company owner who runs his real business on it every day.

Talk to the founder: founding@atlass-os.com

Yes — a native, hosted MCP surface with 58 working tools as of August 10, 2026, covering CRM, scheduling, banking, GST, payables, payroll, inventory, purchasing, and payments. Tokens are minted in-app with scoped permissions.

No. 35 of the 58 tools are write-capable, and writes are the point — every financial write is recorded as balanced double-entry on an append-only audit log. You control write access per scope group.

Any MCP-capable client. You bring your own AI subscription; ATLASS charges no per-conversation AI fee to use your own agent. Fair-use rate limit: 120 reads and 20 writes per minute, per token.

No — nothing in ATLASS can. There is no payment rail. It records money that moved elsewhere. It also cannot create access tokens or change anyone's permissions. Itcanupdate business settings you have explicitly granted it, like a payroll schedule or a product record.

Is there an MCP server for QuickBooks Desktop?

Not from Intuit — Desktop's integration surface is the legacy SDK/Web Connector. ATLASS is a full migration target with books, CRM, and field operations on one MCP surface.

Bridge Town is an MCP-native, git-versioned financial modeling platform for FP&A teams and finance leaders. AI agents use Bridge Town tools to create projects, write Python model files, run models in isolated cloud sandboxes, query data, write outputs to Google Sheets, create dashboards, branch scenarios, and collaborate with teammates.

The Capital.com MCP Server lets your AI assistant talk to your trading account directly. Market data, position checks, trade previews – all in plain language, without leaving your AI tool.

Coinrule Agentic Trading MCP enables investors to create, backtest, execute, and manage trading agents through natural language across stocks, crypto and ETFs

Invest with Claude and other AI assistants

Australian Consumer Data Right Product Data

Remote MCP server for historical crypto & prediction-market data: search ~500K instruments, live market stats (OHLC, turnover, spreads, depth, slippage) and tick-data purchase. Keyless for catalog & stats; optional OAuth for account tools. Endpoint: https://cryptostruct.com/mcp

Cross-border debt collection from your AI assistant: check cases, get pricing, submit new cases.

Read-only MCP server for your Evibe investment portfolio + live market data (holdings, performance, dividends, benchmarks, screeners). Works with Claude & ChatGPT.

Financial and quantitative modeling engine for AI agents. Typed, named, deterministic.