ClearBooks AI accounting

xyz.clearbooksPublished by clearbooks.xyzv1.5.3Updated Nov 11, 2026

Startup double-entry books: transactions, invoices, bills, payroll, cap table and reports.

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

ClearBooks AI accounting is a remote MCP server that lets an assistant work with a startup's double-entry books: transactions, invoices, bills, payroll, cap…

What you can do
  • Work with double-entry bookkeeping records such as transactions
  • Handle invoices and bills
  • Access payroll and cap table data
  • Produce and review financial reports
  • All actions go through the ClearBooks API using the scopes granted to the API key
When to use it
Useful when you want an assistant to help with a startup's bookkeeping and financial reporting — reviewing transactions, invoices, bills, payroll or cap table data, or pulling reports — without leaving the chat.
Requirements
A remote streamable HTTP endpoint; no local package. Requires a ClearBooks API key (cb_live_...) created in the Developer Portal under API Keys, with the scopes the agent needs, sent in the x-api-key header.
Before you install
The API key is a live financial-data credential sent in the x-api-key header; grant only the scopes needed and keep it out of shared logs. The server touches accounting records, invoices, bills, payroll and cap table data, so assistant actions may read or change sensitive financial information.

Installation

In SourceWeft

  1. Open ClearBooks AI accounting in the dashboard and add it to a workspace.
  2. Connect x-api-key credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/xyz.clearbooks%2Fclearbooks/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "clearbooks-ai-accounting": {
      "type": "http",
      "url": "https://nwuiorqmvkhxjzjrvnxf.supabase.co/functions/v1/mcp-server",
      "headers": {
        "x-api-key": "<YOUR_API_KEY>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.5.3LatestNov 11, 2026

Score

67% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.