Skip to content
Klausi
Start for free
Topics

Connect Klausi with Claude & ChatGPT

Use the Model Context Protocol (MCP) to let approved AI clients read or update your Klausi account — with explicit permissions and revocation at any time.

On this page
  1. What MCP does
  2. Connect Claude or Claude Desktop
  3. Connect ChatGPT
  4. Other MCP clients with an access token
  5. What becomes possible
  6. Permissions and actual effects
  7. Risks and safe use
  8. Public tool catalog
  9. Rate limits, errors and support
  10. Revoke access anytime
  11. Security & privacy
  12. Troubleshooting
  13. Official provider documentation

What MCP does

MCP is an open standard through which an AI client calls clearly defined Klausi tools. The model does not receive your entire account automatically: it requests individual tools, within your scopes, when they are relevant to your prompt.

Before you start

  • A Klausi account with access to Settings → Integrations → MCP.
  • A supported AI plan: Claude Free (one custom connector), Pro, Max, Team, or Enterprise; full ChatGPT MCP including write actions currently requires Business or Enterprise/Edu and workspace approval.

Note: Claude and ChatGPT do not look exactly the same for every account. Some menus may therefore have a different name or position. If you cannot find a step, use the official guides linked at the end of this page.

Connect Claude or Claude Desktop

Claude uses Klausi as a remote custom connector with OAuth. The same connector setup applies to Claude on the web and Claude Desktop — do not add this remote server to claude_desktop_config.json.

  1. Open MCP settings in Klausi

    Go to Settings → Integrations → MCP in Klausi. Copy the official endpoint shown below. Only trust the klausi.app domain.

  2. Add the remote connector in Claude

    Open Customize → Connectors → + → Add custom connector. Team and Enterprise owners use Organization settings → Connectors. Enter “Klausi” and the endpoint, then Add.

  3. Connect and approve access

    Under Customize → Connectors, select Klausi and choose Connect. Claude starts Klausi’s OAuth flow. Sign in, review the scopes, grant only what you need, and confirm.

  4. Enable only the tools you need

    In a chat, use + → Connectors to enable Klausi. Review each proposed action — especially write tools — before approving it. Example prompts:

    • List my open tasks for this week, grouped by project.
    • Log 90 minutes on the “Website” project and tell me exactly what you changed.

For mobile use, set up the connection on Claude web first.

Connect ChatGPT

ChatGPT treats a remote MCP server as a custom app. Full MCP, including Klausi write tools, is currently available on ChatGPT web for Business and Enterprise/Edu workspaces. A workspace admin or owner must enable developer mode and approve or publish the app. Pro currently has limited read/fetch access, not the full Klausi workflow.

  1. Enable developer mode

    An admin or owner opens Workspace settings → Apps → Create. Depending on the plan, developer access may also be enabled under Settings → Apps → Advanced Settings or Permissions & Roles → Connected Data.

  2. Create the Klausi app

    Choose Create, enter “Klausi” and the endpoint, then select OAuth when asked for authentication. Choose Scan tools. ChatGPT opens Klausi so you can sign in and approve scopes.

  3. Review and publish

    Check the discovered tools and their write effects. Create the draft, test it in a new chat, and publish it to the intended workspace users. Enterprise/Edu admins can disable individual actions and limit access with RBAC.

  4. Use Klausi in a chat

    Open a new chat, select Klausi from the tools/apps menu, or mention it in your prompt. ChatGPT may request confirmation before write actions. Custom MCP apps are currently web-only; Agent mode does not use them, and Deep research uses read/fetch actions only.

Tool changes need admin review. Enterprise/Edu can refresh actions; Business currently requires recreating and republishing the app.

Other MCP clients with an access token

Use this path only for clients that support Streamable HTTP plus a custom Bearer Authorization header but cannot complete Klausi’s OAuth flow. Claude and ChatGPT should use their connector/app flows above.

  1. Grant consent and create a token

    In Settings → Integrations → MCP, grant consent for the required scopes and create a token. It is displayed only once. Treat it like a password.

  2. Configure the endpoint and header

    Add a remote HTTP MCP server in your client and send the token in the Authorization header. Never put the token in a URL, screenshot, support request, chat prompt, or shared repository.

    Server URL
    https://mcp.klausi.app/mcp
    HTTP header
    Authorization: Bearer <your-token>

  3. Test read-only first

    Restart or reconnect the client, list the available tools, and test a harmless read request before enabling write access.

What becomes possible

The client can combine several tool calls into a workflow, but only within the data and scopes of the signed-in Klausi user.

Tasks & planning
List, create, update and complete tasks; combine them with projects and due dates.
Time tracking
Read entries, start or stop the timer, log time and summarize periods.
Projects & notes
Read or create projects, search notes, create notes and append content.
Clients & CRM
Review clients, pipelines, leads, deals and contacts; create selected CRM records and move deals.
Operations
Read trips, travel expenses, services, project costs and bookings.
Finance overview
Read invoices and finance summaries. Sending, changing and paying invoices is not available.
Client setup and permissions
ClientSetupAvailabilityWrite actions
Claude / Claude DesktopRemote connector + OAuthFree (one), Pro, Max, Team, EnterpriseYes, with Klausi write scope and tool approval
ChatGPTCustom app + OAuth + admin reviewFull MCP: Business, Enterprise/Edu; Pro limitedFull MCP only; provider confirmation may apply
Other clientsOAuth when supported, otherwise Bearer tokenDepends on remote Streamable HTTP supportYes, if the client and Klausi scope allow it

Permissions and actual effects

Grant the smallest scope set that covers the workflow. A provider-side confirmation is an extra safety layer, not a replacement for Klausi scopes.

  • Read — projects, tasks, time, notes, clients, CRM, trips, services, costs and bookings
  • Write — create or update tasks, projects, notes, time entries and selected CRM records
  • Finance read — invoices and finance summary; no invoice write or payment action

Risks and safe use

An MCP connection gives an AI client real access to business data. The most important controls are least privilege, deliberate confirmation and regular review.

Writes are real
Creating a task, logging time or moving a deal changes Klausi immediately. Ask the model to state the intended change first and verify afterward.
Prompt injection
Content from notes, contacts or other connected apps can contain misleading instructions. Do not let untrusted content authorize write actions.
Third-party data
Client and contact data may be sent to the AI provider. Use only accounts and data-processing settings appropriate for your contracts and privacy obligations.
Token exposure
A manual token grants its scopes to whoever holds it. Never paste it into prompts or tickets; revoke it immediately if exposed.
Too many permissions
Start with read, add write only for a concrete workflow, and keep finance access separate. Review active connections regularly.
Provider behavior changes
Client UI, approvals and tool selection can change during beta. Re-check settings after provider updates and test with harmless prompts.

Public tool catalog

Klausi currently exposes these 37 tools through tools/list. Each client receives a JSON schema with required fields, types and allowed values. Results contain model-readable text and, where available, structured data.

Show all 37 tools and inputs
klausi_list_time_entries · read
Inputs: project_id, from, to, limit
klausi_log_time · write
Inputs: idempotency_key, minutes, start_at, end_at, project_id, task_id, description, billable
klausi_start_timer · write
Inputs: idempotency_key, project_id, task_id, description, billable
klausi_stop_timer · write
Inputs: idempotency_key
klausi_list_tasks · read
Inputs: status, project_id, due_before, limit
klausi_create_task · write
Inputs: idempotency_key, title, project_id, due_at, notes
klausi_update_task · write
Inputs: idempotency_key, task_id, title, status, due_at, project_id, notes
klausi_complete_task · write
Inputs: idempotency_key, task_id
klausi_list_projects · read
Inputs: status, client_id, limit
klausi_get_project · read
Inputs: project_id
klausi_create_project · write
Inputs: idempotency_key, name, client_id, status, description
klausi_list_notes · read
Inputs: query, project_id, limit
klausi_get_note · read
Inputs: note_id
klausi_create_note · write
Inputs: idempotency_key, title, body, project_id
klausi_append_to_note · write
Inputs: idempotency_key, note_id, text
klausi_list_clients · read
Inputs: query, status, limit
klausi_list_crm_pipelines · read
Inputs: No input fields
klausi_list_crm_stages · read
Inputs: pipeline_id
klausi_list_crm_organizations · read
Inputs: query, limit
klausi_list_crm_leads · read
Inputs: status, limit
klausi_list_crm_deals · read
Inputs: status, pipeline_id, stage_id, limit
klausi_list_crm_contacts · read
Inputs: query, limit
klausi_create_crm_contact · write
Inputs: idempotency_key, full_name, email, phone, role_title, organization_id
klausi_create_crm_deal · write
Inputs: idempotency_key, title, value, currency, pipeline_id, stage_id, primary_contact_id, organization_id
klausi_move_crm_deal · write
Inputs: idempotency_key, deal_id, stage_id
klausi_log_crm_activity · write
Inputs: idempotency_key, related_type, related_id, subject, type, description
klausi_list_invoices · finance:read
Inputs: status, direction, limit
klausi_get_invoice · finance:read
Inputs: invoice_id
klausi_list_trips · read
Inputs: from, to, status, limit
klausi_get_trip · read
Inputs: trip_id
klausi_list_travel_expenses · read
Inputs: project_id, from, to, limit
klausi_list_services · read
Inputs: query, active_only, client_id, limit
klausi_list_project_costs · read
Inputs: project_id, limit
klausi_list_bookings · read
Inputs: from, to, include_cancelled, limit
klausi_get_booking · read
Inputs: booking_id
klausi_get_time_summary · read
Inputs: from, to, client_id
klausi_get_finance_summary · finance:read
Inputs: No input fields

Hard limits: write tools take effect immediately. Deletion, invoice sending, external sharing, payments and booking changes are not exposed. Financial tools are read-only. Every request is checked for the signed-in user, tenant ownership and scopes.

Rate limits, errors and support

The MCP endpoint allows 120 authenticated requests per minute and returns Retry-After on HTTP 429. OAuth token exchange allows 60 requests per minute per IP; client registration allows 20 per hour per IP. HTTP 401 means a missing, expired or revoked token; 403 means an invalid origin or insufficient scope. JSON-RPC errors identify malformed requests, unsupported protocol versions and tool errors. For reproducible issues, include the time, client, tool name and error code — never the token or customer data.

Contact support

Revoke access anytime

In Settings → Integrations → MCP, revoke a single token or withdraw MCP consent entirely. Withdrawing consent immediately disables all associated tokens and OAuth sessions. Also remove or disable Klausi in the AI provider. If the consent text changes, Klausi requires fresh approval.

Security & privacy

Klausi stores token hashes rather than raw tokens and shows manual tokens once. Tool calls are logged without business content for security and operations. Data returned to Claude or ChatGPT is processed under that provider’s account and data terms and may contain third-party personal data such as client or contact details. See section 3.7 of our privacy policy.

Troubleshooting

The client cannot reach Klausi or tool scanning fails.
Verify the endpoint is exactly https://mcp.klausi.app/mcp, use a remote HTTP connector, and complete the Klausi sign-in and consent flow. Localhost and the Klausi app URL are not MCP endpoints.
The client reports “consent required”, 401 or 403.
Open Settings → Integrations → MCP. Re-approve stale consent for 403, reconnect OAuth for an expired session, or create a new token after revoking a lost one.
ChatGPT shows old tools or a tool schema error.
Ask your admin to review tool changes. Enterprise/Edu can refresh actions; Business must recreate and republish the app.
A write action did not do what I expected.
Check Klausi immediately, correct the record in Klausi if needed, disable the write scope, and report the time, client, tool and non-sensitive error context to support.

Official provider documentation

Provider guidance checked: 31 August 2026

Open MCP settings