Claude Kick connectorWhat Claude can do in your Kick account.
The Claude Kick connector exposes 39 tools. 19 read your ledgers, transactions and reports, 20 change something in your books, and 0 are left undocumented. Below: what Claude finds, what it can post, the preview you confirm first, and where sources differ.
Verified Trustpilot reviews · AI, automation & growth agency
What changes once Claude can work in your Kick books
Instead of filtering transaction lists, exporting reports and copying figures into a chat, a bookkeeper asks Claude in plain words and Claude works in Kick itself. It reads transactions, rules, ledgers and reports across the workspaces you allowed, and when a change is needed it prepares it, shows you a preview, and only applies it once you confirm.
Clean up uncategorized spending. An accountant asks for every unreviewed Stripe transaction from last quarter: Claude finds them with transactions_query, proposes a category, and applies it through transactions_act after you approve the preview.
Stop doing the same fix twice. When the same vendor keeps landing in the wrong place, rules_act creates a categorization rule, and rules_query first shows which transactions it would match.
Answer a client question with numbers. reports_query runs a profit and loss, a balance sheet, a cash flow statement or six other reports, so Claude can explain a quarter in the conversation.
What it does not do: Kick says permanent deletion is not available, only marking transactions for deletion, and account merges are not offered either. Some tools depend on the capabilities of your Kick subscription. Nothing runs on its own: no rule fires because Claude is connected, and no report is sent at month end; Claude acts only while it answers you. For scheduled jobs, the Integrations hub lists automation platforms.
Five words before you connect
The vocabulary around this connector, in one minute.
- Connector
- A link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named capability a connector gives Claude. Claude picks the ones it needs on its own, and the directory sheet lists them by name.
- Authorization
- The sign-in screen of the service, where you grant the access Claude will use. Given once per person, and it can be withdrawn.
- Approval
- The confirmation Claude waits for before an action that changes your account, shown in the conversation when it matters.
- MCP
- The common standard connectors are built on: it lets an assistant such as Claude talk to an outside service like Kick.
Connect Kick to Claude in three steps
- 01
Find Kick in Claude
Open Claude's settings, go to Customize then Connectors, and look the connector up in the list. On a Team or Enterprise workspace, an Owner or Primary Owner enables it for the organization before members can each connect with their own login.
- 02
Sign in to Kick
Click Connect on its row and log in to Kick in the window it opens. If the connection breaks later, Disconnect it and connect again from the same row; access can also be withdrawn from the Kick side.
- 03
Choose what you authorize
Read the authorization screen before you accept: it belongs to Kick, not to Claude, and it sets what the access covers. Kick's guide says this is where you pick all your workspaces or only selected ones.
The 39 tools, split by what they do
Kick gives Claude 39 tools: 19 that read your account, 20 that change something in it.
Nineteen tools read, twenty change your books. Names stay exactly as Claude shows them.
- 19 read
- 20 write
What Claude reads (19)
19 toolsNineteen tools that look up data, run reports or load guidance, leaving your books as they are.
financial_accounts_query
Lists the bank and payment accounts connected to a workspace, so Claude knows where transactions come from before it goes further.
transactions_query
Finds transactions, opens one in detail, summarizes a set of them and surfaces candidates for matching. Its reach stops at the workspaces granted during authorization.
categories_query
Lists or searches the categories of a workspace, browses Kick's global category library and returns spending statistics per category.
classes_query
Lists and searches the classes in a workspace and returns spending statistics or transaction counts per class, the extra dimension used to split activity.
counterparties_query
Lists the counterparties of a workspace or finds one by name, the vendors, customers and other parties transactions are attached to.
rules_query
Lists categorization rules and their groups, previews which transactions a rule would catch and shows which ones a rule already touched.
accounting_query
Lists accounts in the chart of accounts, all accounts of a workspace, the ledgers it holds and the ledger of a given entity.
opening_balances_query
Shows the opening balances recorded for a ledger, or the one for a specific account, the starting figures every later report builds on.
journals_query
Looks up a journal entry and lists the manual journals of a workspace, the entries booked by hand.
documents_query
Searches the documents stored in a workspace and returns the metadata of one. To open the file itself, Claude then turns to documents_download.
documents_download
Returns a temporary download link for one stored document, so you can open the actual file rather than its description.
entities_query
Lists the entities of a workspace, finds one by name and reads its address. An entity is one of the businesses whose books the workspace holds.
activity_query
Shows recent activity in a workspace, detailed logs and the details of one event, so you can trace who did what and when.
tasks_query
Lists the tasks in a workspace, the items a team keeps open on a set of books.
reports_query
Runs one of nine reports: profit and loss, balance sheet, cash flow statement, trial balance, chart of accounts, account transactions, expenses by vendor, owner cash flow and top transactions.
context_browse
Lists the workspaces your login can reach, each with a summary of its entities. Kick advises calling it before any work inside a workspace.
context_resolve
Turns the name of a workspace, an entity or a ledger into the identifiers the other Kick tools need, so you can talk about clients by name.
list_kick_skills
Lists the skill guides Kick publishes for its tools, step-by-step workflows that document query syntax and common pitfalls.
load_kick_skill
Loads one Kick skill guide by name so Claude follows Kick's own instructions for a domain, such as the right attributes to use.
What Claude changes (20)
20 toolsTwenty tools that change something in Kick. Kick documents a preview for every one of them: Claude shows the change, you confirm or cancel.
transactions_act
Asks you firstUpdates a transaction or many at once, splits one, creates manual transactions, and marks entries for deletion or cancels that mark.
transactions_transfer_matches_act
Asks you firstPairs two transactions as a transfer between accounts, or undoes a pairing made earlier, so money moving between your own accounts is not counted as income or spending.
transactions_document_links_act
Asks you firstAttaches a stored document to a transaction or removes that link, so each expense carries its proof.
categories_act
Asks you firstCreates, renames or deletes categories in a workspace, reshaping the list transactions are sorted into.
classes_act
Asks you firstSets up, renames or drops classes, the tags used to split activity by region, office or line of business.
counterparties_act
Asks you firstCreates, updates or deletes counterparties, merges two duplicates into one, and copies one from Kick's global list into the workspace.
rules_act
Asks you firstCreates rules and rule groups, updates or deletes rules, and changes the order in which rules apply.
accounting_act
Asks you firstCreates, updates, enables, disables or deletes entries in the chart of accounts, one at a time or in bulk.
account_groups_act
Asks you firstAdds, renames or removes account groups, the headings that organize the chart of accounts into families.
opening_balances_act
Asks you firstSets or updates the opening balance of an account, fills several at once, or removes one, the figures a set of books starts from.
journals_act
Asks you firstCreates one or several manual journal entries, updates them or deletes them, for adjustments that do not come from a bank feed.
documents_act
Asks you firstUploads a document into Kick through a two-step flow, so a receipt or an invoice lands in the workspace's files.
entities_act
Asks you firstCreates an entity, updates its details or address, and saves its tax locations, the settings that describe each business in a workspace.
activity_undo
Asks you firstReverts a change made earlier in the workspace.
tasks_act
Asks you firstOpens, edits or deletes tasks in a workspace, the to-do items a team uses to coordinate work on the books.
bills_create
Asks you firstRecords new bills, the supplier invoices you owe, in a workspace.
bills_update
Asks you firstEdits or removes bills in batches, limited to bills that were created through this connector.
invoices_create
Asks you firstRecords new customer invoices in a workspace.
invoices_update
Asks you firstChanges or removes invoices in batches, but only those that were created through this connector.
organization_clients_create
Asks you firstCreates a new client organization workspace for an accounting firm.
What Claude checks with you first
By default, Claude stops and asks before each action it takes on an account for someone. Kick adds its own layer: every change starts as a preview.
Kick's documentation says all its write tools are preview-first: the first call returns a description of the change with a one-time token, and the change only happens when the same request comes back with that token. Kick also states that the connector is read-only by default and asks for explicit confirmation before any change. On Team and Enterprise, owners decide whether members may skip repeated prompts and can limit a connector for the whole organization; nobody overrides that from a personal account.
Which plans include it
None of the 819 sheets in the official directory states its plan availability. That answer is published nowhere by Anthropic, connector by connector.
Anthropic's general rule: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, and desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner opens a connector for the organization before members can each connect. Kick's own guide names Claude plans for this connector; the limits section sets it against Anthropic's rule. The directory sheet on your account shows the current state.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you, so nothing happens when a bank feed imports new transactions or a period closes.
Only Kick documents this connector; neither the Claude help center nor Anthropic's developer docs has a page about it. The partner badge is not a security audit, and Anthropic says on every sheet that it neither chooses a publisher's tools nor guarantees their behaviour. Kick also warns that instructions hidden in outside documents, emails or transaction memos can try to steer an assistant. It also asks you to enable the connector in each conversation where you want to use it.
Which Claude plans can use the Kick connector?
- Claude help center, general connector rule ↗September 2026Remote connectors are open to all users; on Team and Enterprise, an Owner has to enable each one first.
- Kick's guide to connecting Claude ↗Read October 2026The publisher says directory connectors, Kick included, are available on Free, Pro, Max, Team and Enterprise.
What this page followsThe two point the same way, but they are not the same voice: Anthropic's rule covers every connector, while Kick's line speaks for this one and comes from the publisher, not Anthropic. Neither is outdated. Check the directory sheet on your own account before relying on either.
Need help connecting Kick to Claude?
A person reads every message.
