MCP 0.9.0 / OAUTH

Give your agent a bounded connection to the books.

Add one remote MCP server. Sign in to VisiBooks, choose the entities it can reach, and approve the work it may perform. No API key to paste into a chat.

VISIBOOKS / STREAMABLE HTTPLIVE
https://mcp.visibooks.app/mcp
TRANSPORTHTTP
AUTHOAUTH
TOOLS28
01
ADD THE SERVER

Use the endpoint in your existing agent client.

02
APPROVE ACCESS

Sign in, select entities, and review authority.

03
START OPERATING

Give the agent its bookkeeping operating prompt.

Client setup

Use the agent interface you already know.

OAuth is the default path. The agent never sees your VisiBooks password, and you choose entity access during approval.

Agent client

Claude

Web, desktop, mobile, and Cowork

REMOTE CONNECTOR
  1. 01

    Open Customize → Connectors in Claude.

  2. 02

    Choose + → Add custom connector. Name it VisiBooks.

  3. 03

    Paste the endpoint, add the connector, then choose Connect.

  4. 04

    Sign in to VisiBooks and approve the entities Claude may reach.

Custom remote connectors are available on Claude plans; Free accounts are limited to one custom connector.
OFFICIAL CLIENT INSTRUCTIONS ↗

OAuth + bounded authority

Connecting is not surrendering control.

The authorization screen creates a dedicated agent identity. Every operation is attributed to it, and access can be paused or revoked without changing your VisiBooks password.

OPEN AGENT CONTROL →
Default execution policy
LIVEObserve books

Read balances, pending work, documents, close readiness, and audit activity.

REVIEWBusiness context

Ask owner questions and remember explicit answers with visible provenance.

DIRECTCategorize transactions

Routine categorization can post directly; the tool contract requires a dry-run preview first.

REVIEWJournal entries and corrections

Journals, reversals, and closing entries wait in the review queue before posting.

STOPPause or revoke

Disable one agent or all agent work for an entity from Control.

When the agent is wrong

The ledger keeps the correction honest.

Posted entries are never silently edited. The agent proposes a reversal with its rationale, a human reviews it, and the correction becomes another traceable entry.

01DETECT

Invariant or review finds the problem.

02PROPOSE

Agent names the entry and rationale.

03REVIEW

Owner sees the exact reversing lines.

04REVERSE

History stays intact and balanced.

The actual tool surface

28 bookkeeping tools. No mystery actions.

This is the tool list advertised by the deployed VisiBooks MCP server—not an illustrative roadmap.

SERVER VERSION 0.9.0

Orient + verify

Understand the entity, test its integrity, and see what remains.

list_entitiesget_snapshotcheck_invariantsget_close_readinessget_reconciliation_statusget_account_activity

Owner context

Ask only when business intent matters, then remember the answer with provenance.

get_business_contextask_ownerrecord_owner_decision

Banking

Resolve bank work without duplicating or hiding ledger activity.

list_pending_transactionscategorize_transactionspropose_automationget_match_candidatesmatch_transactiontransfer_linkimport_transactionsdedupe_feedsignore_pre_ledgerattach_feed

Documents + payables

Find incoming documents, record decisions, and settle the subledger.

list_invoice_documentsreview_documentallocate_invoice_documentapply_vendor_payment

Controlled journals + audit

Propose consequential entries and inspect every agent operation.

propose_journal_entrypropose_reversalpropose_closing_entrylist_proposalsget_agent_activity

Starter operating prompt

Tell the agent how to keep the books.

Paste this into the accounting project or reusable instruction surface in your agent. If your client supports scheduled or recurring work, use the same prompt for that run.

VISIBOOKS-OPERATOR.TXT
You are the bookkeeping operator for this business. Use VisiBooks as the accounting system of record.

At the start of each run:
1. Call list_entities if the connection spans more than one entity.
2. Call check_invariants before changing the ledger.
3. Call get_snapshot and get_close_readiness to understand current work.
4. Call get_business_context before asking the owner or repeating a judgment that may already be remembered.

Operating rules:
- Preserve double-entry accounting and the existing chart of accounts.
- Match an existing entry before creating new ledger activity.
- Preview every tool that supports dry_run before executing it.
- Use direct categorization only when the evidence is clear.
- Propose journal entries, reversals, and closing entries for human review.
- Never treat a missing document or unknown business purpose as permission to guess.
- When missing business context changes the accounting, use ask_owner with a stable context key instead of guessing.
- If I answer directly in this conversation, use record_owner_decision and identify this conversation in source_note. Never infer an owner answer.
- Do not repeat judgment already handled by an existing deterministic rule or mapping.
- After repeated owner-confirmed decisions establish a safe pattern, use propose_automation to queue a narrow deterministic rule for my approval.

End each run with:
- Books current through [date]
- Work completed
- Decisions that need the owner
- Blocked items and the condition that will unblock them
- Reconciliation and close readiness

Ready to authorize

Create the books. Then connect the agent.

Start free with one manual entity. Move to live bank feeds when the operating model works for you.