Laden...
Free tools
Guides
Laden...
Connect Claude to your cashwerk organisation and work in conversation with real customers, projects, hours and invoices — with your permissions, and no more.
The connector exposes cashwerk over the Model Context Protocol (MCP). Claude gets operations that read your organisation's data and — when you want it to — create and change records: find a contact, turn a deal into a quote, summarise the hours booked on a project, mark an invoice as paid.
The operations are generated from the public OpenAPI specification. Each one maps to exactly one API endpoint — there is no second, hidden path into the data, and what the API does not expose, Claude does not see either.
MCP endpoint
https://mcp.cashwerk.io/mcpYou need a cashwerk account on an active paid licence. A connection is made per person and per organisation; no API key is involved.
In Claude, go to Settings → Connectors and add the cashwerk connector. If you enter it yourself, the MCP endpoint URL is the only value you need.
Claude opens the cashwerk sign-in. You sign in with your usual account — your password never reaches Claude.
A consent screen names the requesting assistant and the organisation concerned. Access exists only once you confirm.
From then on the operations are available in the conversation. Before a writing operation, Claude shows what it is about to do.
Other MCP-capable clients — ChatGPT, Cursor, Visual Studio Code, n8n — use the same endpoint. Per-client setup is on the MCP server product page.
The operations cover the modules your licence includes. What you can actually use in a conversation depends on your permissions in cashwerk.
Contacts, companies, deals, pipelines and portfolios: search, read, create, change and link them to each other.
Quotes, order confirmations, invoices, credit notes, cancellation and delivery documents, billing chains, received payments as bookkeeping entries, and e-invoicing.
Projects, tasks, subtasks, boards and columns, assignments, comments and project metrics.
Calendars, appointments, recurring series, availability, plus booking pages and event types.
Time tracking, running timers, work reports, working-time accounts, absences and shift plans.
Folders and files, upload, move, trash, and shares in the share centre.
Read, send and search conversations and messages; the files and links of a conversation.
Materials, services, machines, subcontracts, units and groups, including export.
Users, branches, sectors, tags, tax rates, document layouts, webhooks and data import.
The complete, always-current list follows from the developer documentation. Writing and deleting operations are marked as such in the protocol, so a client can warn before running one.
A connector is not a second account with rights of its own. It is your account, used by an assistant.
Phrase it as you would to a colleague. Claude picks the right operation itself and asks when something is missing.
The examples name records as they are actually stored. Record names are not translated, so they stay German even here — replace them with your own customers, projects and documents.
The connector is entered but the authorisation was never completed. Remove it, add it again, and this time confirm the consent screen all the way through.
The access has expired or was revoked. Sign in again through the connector; that creates a fresh authorisation.
Either your role lacks the permission for that operation, or the organisation's licence does not include the module. Your user's permissions settle the first case; the organisation's owner settles the second.
Almost always the wrong organisation: an authorisation applies to exactly one. Check which account granted it.
The per-minute usage limit is reached. It depends on the plan and is listed on the MCP server product page. Wait briefly and ask for less at a time.
With several organisations, each needs its own authorisation. The consent screen names the organisation before you confirm.
Our support team answers questions about the connector, about permissions, and about an error code. It helps to say which operation you triggered and what came back.
support@cashwerk.io