Claude Desktop MCP Connector

Keito’s hosted MCP connector lets Claude Desktop work with your Keito account directly. Use it when you want Claude to look up clients and projects, start or stop timers, log agent work, record LLM usage expenses, and build billing-ready summaries from Keito data.

For this release, the hosted connector is the setup path for almost everyone.

If you want to connect Claude Desktop to Keito, use the hosted remote connector at https://mcp.keito.ai.
If you are on Claude Team or Enterprise, ask an Owner to add the same connector URL for the organization.
If you need a local .mcpb package, contact Keito support. Local desktop extensions are support-managed and are not published as public GitHub downloads.

The hosted connector receives fixes centrally and uses your normal Keito login. You do not copy a Keito API key into Claude Desktop for hosted setup.

Requirements

Before you connect:

You need a Keito account with access to the clients, projects, tasks, and reports you want Claude to use.
Claude Desktop must support connectors for your plan and organization settings.
For Team and Enterprise Claude plans, an Owner may need to add the connector for the organization before members can connect it.
For write actions such as starting timers, creating time entries, or logging expenses, your Keito user needs the corresponding Keito permissions.

Connect The Hosted Keito Connector

Use this path for normal Claude Desktop usage.

Open Claude Desktop.
Go to Settings or Customize → Connectors.
Click + and choose Add custom connector.
Set the connector name to Keito.
Set the connector URL to:

https://mcp.keito.ai

Existing https://mcp.keito.ai/mcp connectors still work, but use the root URL for new setups.

Leave advanced OAuth client settings blank unless Keito support tells you otherwise.
Click Add.
Select Keito in the connector list and click Connect.
Complete the Keito login and consent flow in your browser.
Start a new Claude Desktop chat.
Use the + or Search and tools menu in the composer, open Connectors, and enable Keito for the conversation.

Claude’s remote connector flow is account-based. You do not configure the hosted Keito URL in claude_desktop_config.json. See Claude’s custom connector guide for the current connector UI and plan behavior.

Team And Enterprise Setup

For Claude Team and Enterprise plans, an Owner or Primary Owner can add Keito centrally:

Open Claude organization settings.
Go to Connectors.
Add a custom web connector.
Use https://mcp.keito.ai as the remote MCP server URL.
Save the connector.

After that, each member connects their own Keito account from Customize → Connectors. Claude can only use the Keito data and actions available to that authenticated user.

If You Need A Local MCPB Package

The local MCPB package is not the normal setup path and is not published as a public GitHub release.

Use a local extension only when your organization specifically needs a local Claude Desktop package or cannot use the hosted connector. If that applies to you, contact Keito support and we can provide the right MCPB package and distribution guidance.

After Keito has issued an MCPB package to your organization:

Save the provided .mcpb file to your machine.
Open Claude Desktop.
Go to Settings → Extensions.
Open Advanced settings.
In the extension developer section, click Install Extension….
Select the .mcpb file.
Fill in the required configuration:

Setting	Description
Keito API Key	A Keito API key beginning with `kto_`.
Keito Account ID	Your Keito company or account ID.
Keito API Base URL	Use `https://app.keito.ai/api/v2` unless you are testing another environment.

Restart Claude Desktop if the tools do not appear immediately.

The local extension runs on your machine and uses the API key you configure. The hosted connector uses OAuth instead.

Claude’s desktop extension guide covers the general .mcpb installation flow and extension troubleshooting.

Verify The Connection

After connecting, ask Claude:

Use Keito to show my current user, company, and running timer.

Claude should call Keito tools and return your current Keito context. If it says no timer is running, that is a valid successful response.

You can also ask:

What Keito tools are available in this chat?

If no Keito tools are listed, enable Keito from the conversation’s Search and tools or Connectors menu.

What You Can Use It For

Find Clients, Projects, And Tasks

Use this before logging work or asking for reports.

Use Keito to list my active clients, then show projects for Valueleaf Ltd and the tasks under each project.

Claude can use:

Tool	Purpose
`keito_list_clients`	Find client records available to your account.
`keito_list_projects`	Find active projects and project codes.
`keito_list_tasks`	Find tasks scoped to a project.

Start And Stop A Timer

Use this when you want Claude Desktop to control a Keito timer during a work session.

Start a Keito timer for Valueleaf Ltd, project Website Platform, task Development. Use the notes "Claude Desktop MCP setup docs."

When you finish:

Stop my running Keito timer and add notes summarizing what we completed.

Claude can use:

Tool	Purpose
`keito_start_timer`	Start a running time entry.
`keito_get_running_timer`	Check whether a timer is already running.
`keito_stop_timer`	Stop the current timer or a specified timer.

Log Finished Work

Use this when the work already happened and you want a completed time entry.

Create a Keito time entry for 1.25 hours today on Valueleaf Ltd, project Website Platform, task Documentation. Notes: "Wrote Claude Desktop MCP setup guide and usage examples."

Claude can use keito_create_time_entry for this. It can also use keito_update_time_entry if you ask it to correct a draft entry.

Report On Time And Billing

Use this for weekly reviews, client updates, or invoice preparation.

Use Keito to summarize time for Valueleaf Ltd from 2026-06-01 to today. Break it down by person and project, then flag anything that looks unbilled.

Useful report tools:

Tool	Purpose
`keito_list_time_entries`	Pull detailed time entries with filters.
`keito_report_team_time`	Pull a team time report for a date range.
`keito_list_expenses`	Pull expenses, including LLM usage.

Log LLM Usage Expenses

Use this when you want AI costs attached to the same project as the work.

Log an LLM usage expense in Keito for project Website Platform: model claude-sonnet-4-6, 30000 input tokens, 15000 output tokens. Notes: "Claude Desktop documentation session."

keito_log_llm_usage can calculate the amount from the model and token counts when the model is in Keito’s price table. Use keito_create_expense for general non-LLM expenses.

Prepare Client Updates

Claude is useful for turning Keito data into plain-English updates.

Use Keito to pull this week's time and LLM expenses for Valueleaf Ltd. Draft a client-safe update with total hours, main work areas, LLM costs, and any items that need approval before invoicing.

Ask Claude to show the source totals before it drafts client-facing text.

Good Prompt Patterns

Use precise names when you know them:

Use Keito project "Website Platform" for client "Valueleaf Ltd".

Ask Claude to discover IDs before writing:

First list matching Keito projects for "Volvo". Do not create or update anything until I confirm the project.

Ask for a dry run before destructive or billing-sensitive work:

Prepare the time entries you would create, including project, task, date, duration, and notes. Do not write them until I say "create them".

Use explicit date ranges:

Use 2026-06-01 through 2026-06-17. If a tool defaults missing end dates to today, still show me the date range used.

What Not To Use It For

Do not use the Claude Desktop connector as your only automatic background tracker. It only acts when Claude invokes Keito tools during a conversation. For automatic local coding-session capture, use the Keito Agent Skill or Keito CLI agent workflows.

Avoid leaving broad write tools enabled for research-style conversations where Claude may make many autonomous tool calls. For read-only reporting, keep the workflow to list and report tools.

Do not ask Claude to delete time entries without reviewing the target entry ID and reason first.

Security And Permissions

The hosted connector uses OAuth. Claude does not need your Keito password.
Claude can only access Keito through the permissions granted to your authenticated Keito user.
Review tool approval prompts, especially for write actions.
Disable tools that are not relevant to the current conversation.
The hosted connector is public at https://mcp.keito.ai; a 401 response in a browser is normal because MCP requests require OAuth.
The local MCPB extension uses your configured API key. Treat that key like any other production credential.

Troubleshooting

Symptom	What to check
Keito appears under “Not connected”	Click Connect and complete the browser login flow.
Tools do not appear in a chat	Enable Keito from the +, Search and tools, or Connectors menu for that conversation.
Browser shows `401` at `https://mcp.keito.ai`	That is expected. The endpoint requires OAuth.
Claude says no client or project matched	Ask Claude to list clients/projects first, then use the exact stored name or project ID.
A report looks too broad	Ask Claude to show the exact filters and generated date range before summarizing.
OAuth returns an error	Remove and re-add the connector, then connect again. If it persists, send the request ID to Keito support.
Local extension installed but tools are missing	Restart Claude Desktop and check required extension settings: API key, account ID, and API base URL.
Team member cannot add the connector	A Claude Team or Enterprise Owner may need to add it in organization connector settings first.