Can I use Weave as a CLI?

Yes. KosmoKrator exposes a Weave CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Weave through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Weave tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Weave credentials stored?

Weave credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Weave MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

data

Weave CLI for AI Agents

Use the Weave CLI from KosmoKrator to call Weave tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.

Weave CLI Setup

Weave can be configured headlessly with `kosmokrator integrations:configure weave`.

Install, configure, and verify

# Install KosmoKrator first if it is not available on PATH.
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

# Configure and verify this integration.
kosmokrator integrations:configure weave --set access_token="$WEAVE_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmokrator integrations:doctor weave --json
kosmokrator integrations:status --json

Credentials

Authentication type: Bearer token bearer_token. Configure credentials once, then reuse the same stored profile from scripts, coding CLIs, Lua, and MCP.

Key	Env var	Type	Required	Label
`access_token`	`WEAVE_ACCESS_TOKEN`	Secret `secret`	yes	Access Token
`url`	`WEAVE_URL`	URL `url`	no	Weave API URL

Command Patterns

The generic command is stable across every integration. The provider shortcut is shorter for humans.

Generic CLI call

kosmo integrations:call weave.weave_list_patients '{"limit":1,"page":1,"query":"example_query"}' --json

Provider shortcut

kosmo integrations:weave weave_list_patients '{"limit":1,"page":1,"query":"example_query"}' --json

Discovery

These commands return structured output for coding agents that need to inspect capabilities before choosing a function.

Discovery commands

kosmo integrations:docs weave --json
kosmo integrations:docs weave.weave_list_patients --json
kosmo integrations:schema weave.weave_list_patients --json
kosmo integrations:search "Weave" --json
kosmo integrations:list --json

Automation Contexts

The same configured command surface works in these environments. The command does not change unless the host wrapper, credentials, or permissions change.

CI Run integration calls from CI jobs with JSON output, explicit credentials, and predictable exit status. Cron Jobs Schedule repeatable integration workflows from cron while keeping credentials in KosmoKrator config. Shell Scripts Call integration functions from shell scripts with stable JSON input and output. Headless Automation Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers. Coding Agents Let coding agents discover schemas and execute integration functions through CLI commands or MCP.

CLI Functions

Every function below can be called headlessly. Commands are highlighted, copyable, and scroll horizontally when payloads are long.

`weave.weave_list_patients`

Search and list patients from Weave. Returns patient records with names, contact info, and metadata. Use the query parameter to search by name, phone, or email.

Read read

Parameters: limit, page, query

Generic call

kosmo integrations:call weave.weave_list_patients '{"limit":1,"page":1,"query":"example_query"}' --json

Shortcut

kosmo integrations:weave weave_list_patients '{"limit":1,"page":1,"query":"example_query"}' --json

`weave.weave_get_patient`

Retrieve a single patient by ID. Returns full patient details including demographics and contact information.

Read read

Parameters: id

Generic call

kosmo integrations:call weave.weave_get_patient '{"id":"example_id"}' --json

Shortcut

kosmo integrations:weave weave_get_patient '{"id":"example_id"}' --json

`weave.weave_list_appointments`

List appointments from Weave with optional date range filtering. Returns appointment records with patient info, scheduled times, and status.

Read read

Parameters: startDate, endDate, limit

Generic call

kosmo integrations:call weave.weave_list_appointments '{"startDate":"example_startDate","endDate":"example_endDate","limit":1}' --json

Shortcut

kosmo integrations:weave weave_list_appointments '{"startDate":"example_startDate","endDate":"example_endDate","limit":1}' --json

`weave.weave_get_appointment`

Retrieve a single appointment by ID. Returns full details including patient info, scheduled time, duration, and status.

Read read

Parameters: id

Generic call

kosmo integrations:call weave.weave_get_appointment '{"id":"example_id"}' --json

Shortcut

kosmo integrations:weave weave_get_appointment '{"id":"example_id"}' --json

`weave.weave_list_messages`

List patient messages from Weave with optional type filtering. Returns message records with sender, recipient, content previews, and status.

Read read

Parameters: limit, page, type

Generic call

kosmo integrations:call weave.weave_list_messages '{"limit":1,"page":1,"type":"example_type"}' --json

Shortcut

kosmo integrations:weave weave_list_messages '{"limit":1,"page":1,"type":"example_type"}' --json

`weave.weave_get_message`

Retrieve a single message by ID. Returns full message content, sender, recipient, timestamps, and delivery status.

Read read

Parameters: id

Generic call

kosmo integrations:call weave.weave_get_message '{"id":"example_id"}' --json

Shortcut

kosmo integrations:weave weave_get_message '{"id":"example_id"}' --json

`weave.weave_get_current_user`

Get the currently authenticated Weave user profile. Returns user details including name, email, role, and organization info.

Read read

Parameters: none

Generic call

kosmo integrations:call weave.weave_get_current_user '{}' --json

Shortcut

kosmo integrations:weave weave_get_current_user '{}' --json

Function Schemas

Use these parameter tables when building CLI payloads without calling integrations:schema first.

weave.weave_list_patients 3 parameters

Schema command

kosmo integrations:schema weave.weave_list_patients --json

Parameter	Type	Required	Description
`limit`	integer	no	Maximum number of patients to return (default: 25).
`page`	integer	no	Page number for pagination, 1-based (default: 1).
`query`	string	no	Search query to filter patients by name, phone, or email.

weave.weave_get_patient 1 parameters

Schema command

kosmo integrations:schema weave.weave_get_patient --json

Parameter	Type	Required	Description
`id`	string	yes	The unique patient identifier.

weave.weave_list_appointments 3 parameters

Schema command

kosmo integrations:schema weave.weave_list_appointments --json

Parameter	Type	Required	Description
`startDate`	string	no	Start date for the range (ISO 8601, e.g. "2025-01-01").
`endDate`	string	no	End date for the range (ISO 8601, e.g. "2025-01-31").
`limit`	integer	no	Maximum number of appointments to return (default: 25).

weave.weave_get_appointment 1 parameters

Schema command

kosmo integrations:schema weave.weave_get_appointment --json

Parameter	Type	Required	Description
`id`	string	yes	The unique appointment identifier.

weave.weave_list_messages 3 parameters

Schema command

kosmo integrations:schema weave.weave_list_messages --json

Parameter	Type	Required	Description
`limit`	integer	no	Maximum number of messages to return (default: 25).
`page`	integer	no	Page number for pagination, 1-based (default: 1).
`type`	string	no	Filter by message type (e.g. "sms", "email").

weave.weave_get_message 1 parameters

Schema command

kosmo integrations:schema weave.weave_get_message --json

Parameter	Type	Required	Description
`id`	string	yes	The unique message identifier.

weave.weave_get_current_user 0 parameters

Schema command

kosmo integrations:schema weave.weave_get_current_user --json

Parameter	Type	Required	Description
No parameters.

Permissions

Headless calls still follow the integration read/write permission policy. Configure read/write defaults with integrations:configure. Add --force only for trusted automation that should bypass that policy.