Potencialize seu agente
O comando do próprio publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
npx -y @nightsquawktech/[email protected]O Claude Code não tem link de instalação para um comando local. Copie o comando abaixo e execute-o em um terminal.
claude mcp add nightsquawktech-kimai-mcp-server -- npx -y @nightsquawktech/kimai-mcp-server@0.3.0Execute em um terminal.
{ "mcpServers": { "nightsquawktech-kimai-mcp-server": { "command": "npx", "args": [ "-y", "@nightsquawktech/[email protected]" ] } }}claude_desktop_config.json
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirAn MCP (Model Context Protocol) server for Kimai, connecting your self-hosted time tracking to AI tools.
bash (macOS/Linux):
KIMAI_BASE_URL="https://example.kimai.cloud"
KIMAI_API_TOKEN="replace-with-api-token"
claude mcp add kimai \
--env KIMAI_BASE_URL="$KIMAI_BASE_URL" \
--env KIMAI_API_TOKEN="$KIMAI_API_TOKEN" \
-- npx -y @nightsquawktech/kimai-mcp-server
PowerShell (Windows):
$KIMAI_BASE_URL = "https://example.kimai.cloud"
$KIMAI_API_TOKEN = "replace-with-api-token"
claude mcp add kimai `
--env "KIMAI_BASE_URL=$KIMAI_BASE_URL" `
--env "KIMAI_API_TOKEN=$KIMAI_API_TOKEN" `
-- npx -y @nightsquawktech/kimai-mcp-server
Or put the mcp.json block in .cursor/mcp.json, then verify with:
agent mcp list
(The Cursor CLI manages configured servers but has no mcp add; install is via the button or mcp.json.)
bash (macOS/Linux):
KIMAI_BASE_URL="https://example.kimai.cloud"
KIMAI_API_TOKEN="replace-with-api-token"
code --add-mcp '{"name":"kimai","command":"npx","args":["-y","@nightsquawktech/kimai-mcp-server"],"env":{"KIMAI_BASE_URL":"'"$KIMAI_BASE_URL"'","KIMAI_API_TOKEN":"'"$KIMAI_API_TOKEN"'"}}'
PowerShell (Windows):
$KIMAI_BASE_URL = "https://example.kimai.cloud"
$KIMAI_API_TOKEN = "replace-with-api-token"
$config = @{
name = "kimai"
command = "npx"
args = @("-y", "@nightsquawktech/kimai-mcp-server")
env = @{
KIMAI_BASE_URL = $KIMAI_BASE_URL
KIMAI_API_TOKEN = $KIMAI_API_TOKEN
}
} | ConvertTo-Json -Compress
code --add-mcp $config
bash (macOS/Linux):
KIMAI_BASE_URL="https://example.kimai.cloud"
KIMAI_API_TOKEN="replace-with-api-token"
codex mcp add kimai \
--env KIMAI_BASE_URL="$KIMAI_BASE_URL" \
--env KIMAI_API_TOKEN="$KIMAI_API_TOKEN" \
-- npx -y @nightsquawktech/kimai-mcp-server
PowerShell (Windows):
$KIMAI_BASE_URL = "https://example.kimai.cloud"
$KIMAI_API_TOKEN = "replace-with-api-token"
codex mcp add kimai `
--env "KIMAI_BASE_URL=$KIMAI_BASE_URL" `
--env "KIMAI_API_TOKEN=$KIMAI_API_TOKEN" `
-- npx -y @nightsquawktech/kimai-mcp-server
Or add it to ~/.codex/config.toml under [mcp_servers.kimai].
Every environment variable the server reads, with recommended values:
{
"mcpServers": {
"kimai": {
"command": "npx",
"args": ["-y", "@nightsquawktech/kimai-mcp-server"],
"env": {
"KIMAI_BASE_URL": "https://example.kimai.cloud",
"KIMAI_API_TOKEN": "replace-with-api-token",
"KIMAI_TIMEOUT_MS": "30000"
}
}
}
}
File locations: .mcp.json in your project root (Claude Code), claude_desktop_config.json (Claude Desktop), .cursor/mcp.json (Cursor).
Kimai credentials: generate an API token in your Kimai user profile. The token inherits that user's permissions, so use a dedicated Kimai user with the smallest role that covers what you need.
kimai_create_timesheet, kimai_update_timesheet, kimai_stop_timesheet, kimai_restart_timesheet, kimai_duplicate_timesheet. There is no env gate; each call is guarded instead:
authorization_confirmed: true and an authorization_note (8+ characters) recording the user's explicit approval. The tool descriptions instruct the model to call them only after a human authorizes the edit.kimai-mcp-backups in the OS temp directory, so edits can be audited and manually reverted.[!IMPORTANT] The authorization fields are a guardrail, not a security boundary. The env vars in your MCP config are real credentials, and an AI agent with shell access can bypass the MCP tools and call the Kimai API directly with them. If you need hard read-only, enforce it at the source: give the token's Kimai user a role without timesheet edit permissions.
kimai_get_server_info Kimai version, plugins, and timesheet config
kimai_get_current_user The user behind the API token
kimai_list_users List users
kimai_get_user Get one user
kimai_list_customers List customers
kimai_get_customer Get one customer
kimai_list_projects List projects, optionally filtered by customer
kimai_get_project Get one project
kimai_list_activities List activities, optionally filtered by project
kimai_get_activity Get one activity
kimai_list_tags Find tags by name
kimai_list_timesheets List timesheets with user/customer/project/date/tag filters
kimai_get_timesheet Get one timesheet entry
kimai_list_active_timesheets Currently running timesheets
kimai_list_recent_timesheets Recent timesheet entries
kimai_create_timesheet Create a timesheet entry (write, requires authorization fields)
kimai_update_timesheet Update a timesheet entry (write, requires authorization fields)
kimai_stop_timesheet Stop a running timesheet (write, requires authorization fields)
kimai_restart_timesheet Restart a stopped timesheet (write, requires authorization fields)
kimai_duplicate_timesheet Duplicate a timesheet entry (write, requires authorization fields)
kimai_list_teams List teams
kimai_get_team Get one team
kimai_list_invoices List invoices
kimai_get_invoice Get one invoice
kimai_list_expenses List expenses (expenses plugin)
kimai_get_expense Get one expense (expenses plugin)
kimai_list_tasks List tasks (tasks plugin)
kimai_get_task Get one task (tasks plugin)
31 operations covered across 28 tools.
Contributions and issues are welcome. Please open an issue first before submitting a PR.
AGPL-3.0: free for personal and open-source use. Organizations that cannot comply with the AGPL can purchase a commercial license, and hosted/managed versions are available. See COMMERCIAL.md or contact [email protected].
For copyright concerns or takedown requests, contact [email protected].
Kimai MCP server for Claude, Cursor, and AI agents: 16 tools covering the entire Kimai API. 13 curated time-tracking tools plus a 91-endpoint catalog, with per-call authorization, pre-write backups, c
{ "mcpServers": { "nightsquawktech-kimai-mcp-server": { "command": "npx", "args": [ "-y", "@nightsquawktech/[email protected]" ] } }}Visão geral
Kimai MCP server for Claude, Cursor, and AI agents: 16 tools covering the entire Kimai API. 13 curated time-tracking tools plus a 91-endpoint catalog, with per-call authorization, pre-write backups, cascade snapshots, and an environment gate on deletes.
Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
@nightsquawktech/kimai roda localmente via stdio.
Última verificação: 2026-11-16. Kimai MCP server for Claude, Cursor, and AI agents: 16 tools covering the entire Kimai API. 13 curated time-tracking tools plus a 91-endpoint catalog, with per-call authorization, pre-write backups, cascade snapshots, and an environment gate on deletes.