Komari MCP integration for AI agents.
Connect AI agents to Komari through 71 structured actions, including get client, add client, batch delete clipboard, and clear all records. Review authentica…
- ACTION CONTRACTS
- 71
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Komari integration exposes
The Komari Agent App exposes 71 provider-backed actions for developer tools and infrastructure work. Its current contract lets an authorized agent get one client without returning its enrollment token, create a komari client. the response contains its enrollment token, and delete multiple clipboard entries. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Komari account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Komari capabilities.
Showing 12 of 71 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_clientREADGet one client without returning its enrollment token.
INPUTS: uuid
add_clientWRITECreate a Komari client. The response contains its enrollment token.
INPUTS: name
batch_delete_clipboardHIGH IMPACTDelete multiple clipboard entries.
INPUTS: ids
clear_all_recordsREVIEWPermanently delete all load and ping records.
add_load_notificationWRITECreate a load notification rule.
INPUTS: clients / name / metric / threshold / ratio
add_ping_taskWRITECreate a ping task.
INPUTS: clients / default_on / name / target / type
cancel_metric_migrationHIGH IMPACTCancel the active metric-store migration.
clear_recordsREVIEWPermanently delete all load records.
create_clipboardWRITECreate a clipboard entry.
delete_all_sessionsHIGH IMPACTRevoke all login sessions.
delete_clipboardHIGH IMPACTDelete a clipboard entry.
INPUTS: id
delete_load_notificationHIGH IMPACTDelete load notification rules.
INPUTS: id
INPUT CONTRACTS
Know what the action needs before it runs.
get_client
uuidREQUIRED- The client UUID.
add_client
nameOPTIONAL- Optional client name.
batch_delete_clipboard
idsREQUIRED- Clipboard IDs.
add_load_notification
clientsREQUIRED- Client UUIDs.
nameOPTIONAL- Rule name.
metricREQUIRED- Metric name.
thresholdREQUIRED- Trigger threshold.
ratioREQUIRED- Required time ratio from zero to one.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Client
Get one client without returning its enrollment token. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_clientControl Add Client
Create a Komari client. The response contains its enrollment token. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
add_clientVerify with Add Client
Create a Komari client. The response contains its enrollment token. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
add_clientSAFETY BOUNDARY
Operate Komari with explicit limits
- Authorize Komari with API key and grant only the provider access required by the selected actions.
- 27 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `batch_delete_clipboard`, `cancel_metric_migration`, and `delete_all_sessions` as high-impact operations and require an explicit approval boundary.
- The sampled contract declares provider scopes including `admin:addClient`, `admin:addLoadNotification`, `admin:addPingTask`, and `admin:batchDeleteClipboard`; verify the complete action contract before execution.
- After a call, inspect the structured result and execution record before reporting that the Komari task completed successfully.
CONNECTION MODEL
API key
The API key configured in the Komari dashboard. Komari accepts it as a Bearer token and currently grants administrator-level API access, so use a dedicated secret and restrict exposed actions in OpenConnector.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 34
- WRITE SIGNALS
- 17
- HIGH IMPACT
- 10
- REVIEW SIGNALS
- 10
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Komari.