Help · MCP

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.

All help articles

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 → Apps → MCP.
A supported AI plan: Claude 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.

Recommended

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.

Open MCP settings in Klausi

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

Settings › Apps › MCP

Connection endpoint

https://mcp.klausi.app/mcp

Schematic example view. Labels can differ by language, plan and rollout.

Add the remote connector in Claude

Open Settings → Connectors → Add custom connector. On Team or Enterprise, an Owner must add it under Organization connectors first. Enter “Klausi” and the server URL, then choose Add.

Claude · Add custom connector

Server URL

https://mcp.klausi.app/mcpAdd

Schematic example view. Labels can differ by language, plan and rollout.

Connect and approve access

In a chat, open Search and tools, select Klausi and choose Connect. Claude starts Klausi’s OAuth flow. Sign in, review the scopes, grant only what you need, and confirm.

Klausi · Approve access

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

Allow & connect

Schematic example view. Labels can differ by language, plan and rollout.

Enable only the tools you need

Use Search and tools to enable Klausi for the conversation. 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.

Mobile note: after adding Klausi via Claude on the web, the connector can also be used on iOS or Android. New remote connectors cannot be added directly on mobile.

ChatGPT

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.

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.

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.

ChatGPT · Create app

Klausi · https://mcp.klausi.app/mcpScan tools

OAuth37 tools

Schematic example view. Labels can differ by language, plan and rollout.

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.

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.

ChatGPT stores an approved snapshot of the tools and inputs. If Klausi adds or changes tools later, an admin must refresh the actions and review the diff before publishing the update.

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.

Grant consent and create a token

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

Klausi · Token created

klausi_mcp_8120d7a1b2c3…Copy

Shown only once — copy it now.

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.

{
  "mcpServers": {
    "klausi": {
      "url": "https://mcp.klausi.app/mcp",
      "headers": {
        "Authorization": "Bearer klausi_mcp_…"
      }
    }
  }
}

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	Availability	Write actions
Claude / Claude Desktop	Remote connector + OAuth	Pro, Max, Team, Enterprise	Yes, with Klausi write scope and tool approval
ChatGPT	Custom app + OAuth + admin review	Full MCP: Business, Enterprise/Edu; Pro limited	Full MCP only; provider confirmation may apply
Other clients	OAuth when supported, otherwise Bearer token	Depends on remote Streamable HTTP support	Yes, 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.

ReadRead — projects, tasks, time, notes, clients, CRM, trips, services, costs and bookings

WriteWrite — create or update tasks, projects, notes, time entries and selected CRM records

FinanceFinance 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_entriesread

Inputs: project_id, from, to, limit

klausi_log_timewrite

Inputs: minutes, start_at, end_at, project_id, task_id, description, billable

klausi_start_timerwrite

Inputs: project_id, task_id, description

klausi_stop_timerwrite

Inputs: No input fields

klausi_list_tasksread

Inputs: status, project_id, due_before, limit

klausi_create_taskwrite

Inputs: title, project_id, due_at, notes

klausi_update_taskwrite

Inputs: task_id, title, status, due_at, project_id, notes

klausi_complete_taskwrite

Inputs: task_id

klausi_list_projectsread

Inputs: status, client_id, limit

klausi_get_projectread

Inputs: project_id

klausi_create_projectwrite

Inputs: name, client_id, status, description

klausi_list_notesread

Inputs: query, project_id, limit

klausi_get_noteread

Inputs: note_id

klausi_create_notewrite

Inputs: title, body, project_id

klausi_append_to_notewrite

Inputs: note_id, text

klausi_list_clientsread

Inputs: query, status, limit

klausi_list_crm_pipelinesread

Inputs: No input fields

klausi_list_crm_stagesread

Inputs: pipeline_id

klausi_list_crm_organizationsread

Inputs: query, limit

klausi_list_crm_leadsread

Inputs: status, limit

klausi_list_crm_dealsread

Inputs: status, pipeline_id, stage_id, limit

klausi_list_crm_contactsread

Inputs: query, limit

klausi_create_crm_contactwrite

Inputs: full_name, email, phone, role_title, organization_id

klausi_create_crm_dealwrite

Inputs: title, value, currency, pipeline_id, stage_id, primary_contact_id, organization_id

klausi_move_crm_dealwrite

Inputs: deal_id, stage_id

klausi_log_crm_activitywrite

Inputs: related_type, related_id, subject, type, description

klausi_list_invoicesfinance:read

Inputs: status, direction, limit

klausi_get_invoicefinance:read

Inputs: invoice_id

klausi_list_tripsread

Inputs: from, to, status, limit

klausi_get_tripread

Inputs: trip_id

klausi_list_travel_expensesread

Inputs: project_id, from, to, limit

klausi_list_servicesread

Inputs: query, active_only, client_id, limit

klausi_list_project_costsread

Inputs: project_id, limit

klausi_list_bookingsread

Inputs: from, to, include_cancelled, limit

klausi_get_bookingread

Inputs: booking_id

klausi_get_time_summaryread

Inputs: from, to, client_id

klausi_get_finance_summaryfinance: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.

Revoke access anytime

In Settings → Apps → 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 → Apps → 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.

A workspace admin must refresh the Klausi app actions, review the tool diff and republish the app. ChatGPT does not automatically adopt server-side tool changes.

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: 8 August 2026

Open MCP settings