Give your AI
Access to Klausi.
Connect Claude & co. to your Klausi data via the Model Context Protocol. Your AI reads time, projects, and finances — and creates tasks, time entries, or notes.
Free · consent required · revocable anytime
The AI connection in numbers
Your AI works with your data. By your rules.
Questions, tools, connection, control — four building blocks that connect Claude & co. to your Klausi.
01Ask
Your AI asks. Klausi delivers.
Your AI client calls a Klausi tool and gets the answer from your real data — time, projects, finances. Instead of copy-paste from five tools.
02Tools
37 tools. Clearly bounded.
Reading across eleven areas, targeted writing only for time, tasks, projects, notes, and CRM. Deleting, sending invoices, and external shares are deliberately not possible.
03Connection
One click. Or one token.
Clients with a connector directory like claude.ai connect via OAuth 2.1 with PKCE — all others via an access token from settings. Both stay revocable at any time.
04Control
Separate opt-in. Every call traceable.
MCP only runs after a separate, explicit consent — your revocation immediately invalidates all tokens. The audit log records data-minimized: tool, scope, and status, never the values.
MCP active — with your consent.
Separate opt-in · revocable anytimeAudit log · data-minimized
read✓ okwrite✓ okfinance:read✓ okTool, scope, status — never the values.
Feature overview
What your AI can do. And what it deliberately can’t.
Time & timers
- Read entries and summary
- Log time to projects
- Start and stop timers
Tasks & projects
- Read, create, update, complete tasks
- Read projects and details (incl. total time)
- Create new projects
Notes & CRM
- Read notes in full text, create, append
- Read deals, leads, contacts, and pipelines
- Create contacts and deals, move deals
Read only
- Finance & invoices — dedicated “finance:read” scope
- Clients, trips, and travel expenses
- Services, project costs, bookings, reports
Your control
- Separate opt-in under Art. 6(1)(a) GDPR
- Revocation immediately invalidates all tokens
- Audit log: tool, scope, status — never the values
Deliberate limits
- No deleting via the connection
- No issuing or sending invoices
- No external shares
AI that knows your business
Your AI works
with your data.
Instead of copy-paste from five tools, your AI reaches straight into Klausi — reading what’s there and entering what you allow.
- No retyping between AI and Klausi
- You grant, you revoke — anytime
Belongs together
One AI. Your whole system.
The connection comes alive with the areas that provide your data.
Frequent questions
Questions about the AI connection.
What is the MCP connection?
MCP (Model Context Protocol) is an open standard that lets AI clients like Claude work with external data securely. It lets your AI work directly with your Klausi data — instead of you copying everything back and forth.
Which AI clients work?
Any client that speaks MCP. Clients with a connector directory (e.g. claude.ai) connect via one-click OAuth; all others via an access token you paste.
Can the AI delete things or send invoices?
No. The connection is deliberately limited to reading and targeted creating/updating (time, tasks, projects, notes, CRM). Deleting, issuing or sending invoices, and external shares are intentionally not possible.
Do I have to consent — and can I take it back?
Yes. MCP is a separate, explicit opt-in and can be revoked in settings at any time. A revocation immediately invalidates all your access tokens.
What does the AI connection cost?
Nothing extra. The MCP connection is included in every plan — including the free one.
What about client data and privacy?
Your data lives on EU servers, and every tool call is logged in data-minimized form (tool, scope, and parameter names only). If you pass third-party data to an AI client, you remain the controller — choose your client deliberately.