Can I use Wildix as a CLI?

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

Can I expose Wildix through MCP?

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

Where are Wildix credentials stored?

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

Can I deny write access for Wildix MCP tools?

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

communication

Wildix CLI for AI Agents

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

6 functions 6 read 0 write Bearer token auth

Submit Wildix feedback View package source

Wildix CLI Setup

Wildix can be configured headlessly with `kosmokrator integrations:configure wildix`.

# 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 wildix --set access_token="$WILDIX_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmokrator integrations:doctor wildix --json
kosmokrator integrations:status --json

Credentials

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

Key	Env var	Type	Required	Label
`access_token`	`WILDIX_ACCESS_TOKEN`	Secret `secret`	yes	Access Token
`url`	`WILDIX_URL`	URL `url`	no	API Base URL

Call Wildix Headlessly

Use the generic call form when another coding CLI or script needs a stable universal interface.

kosmo integrations:call wildix.wildix_list_calls '{
  "limit": 1,
  "page": 1,
  "date_from": "example_date_from",
  "date_to": "example_date_to"
}' --json

Use the provider shortcut form for shorter human-facing commands.

kosmo integrations:wildix wildix_list_calls '{
  "limit": 1,
  "page": 1,
  "date_from": "example_date_from",
  "date_to": "example_date_to"
}' --json

Agent Discovery Commands

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

kosmo integrations:docs wildix --json
kosmo integrations:docs wildix.wildix_list_calls --json
kosmo integrations:schema wildix.wildix_list_calls --json
kosmo integrations:search "Wildix" --json
kosmo integrations:list --json

All CLI Functions

Every function below can be called headlessly. The generic form is stable across all integrations; the provider shortcut is shorter but specific to Wildix.

`wildix.wildix_list_calls`

Read read

List call records from the Wildix PBX. Supports pagination and optional date range filtering to narrow results by period.

Parameters: limit, page, date_from, date_to

Generic CLI call

kosmo integrations:call wildix.wildix_list_calls '{"limit":1,"page":1,"date_from":"example_date_from","date_to":"example_date_to"}' --json

Provider shortcut

kosmo integrations:wildix wildix_list_calls '{"limit":1,"page":1,"date_from":"example_date_from","date_to":"example_date_to"}' --json

`wildix.wildix_get_call`

Read read

Get detailed information about a specific call record by its ID.

Parameters: id

Generic CLI call

kosmo integrations:call wildix.wildix_get_call '{"id":"example_id"}' --json

Provider shortcut

kosmo integrations:wildix wildix_get_call '{"id":"example_id"}' --json

`wildix.wildix_list_extensions`

Read read

List PBX extensions configured in the Wildix system. Supports pagination.

Parameters: limit, page

Generic CLI call

kosmo integrations:call wildix.wildix_list_extensions '{"limit":1,"page":1}' --json

Provider shortcut

kosmo integrations:wildix wildix_list_extensions '{"limit":1,"page":1}' --json

`wildix.wildix_get_extension`

Read read

Get detailed information about a specific PBX extension by its ID.

Parameters: id

Generic CLI call

kosmo integrations:call wildix.wildix_get_extension '{"id":"example_id"}' --json

Provider shortcut

kosmo integrations:wildix wildix_get_extension '{"id":"example_id"}' --json

`wildix.wildix_list_users`

Read read

List users configured in the Wildix PBX system. Supports pagination.

Parameters: limit, page

Generic CLI call

kosmo integrations:call wildix.wildix_list_users '{"limit":1,"page":1}' --json

Provider shortcut

kosmo integrations:wildix wildix_list_users '{"limit":1,"page":1}' --json

`wildix.wildix_get_current_user`

Read read

Get the profile of the currently authenticated Wildix user (the user associated with the configured access token).

Parameters: none

Generic CLI call

kosmo integrations:call wildix.wildix_get_current_user '{}' --json

Provider shortcut

kosmo integrations:wildix wildix_get_current_user '{}' --json

Function Schemas

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

`wildix.wildix_list_calls`

List call records from the Wildix PBX. Supports pagination and optional date range filtering to narrow results by period.

Operation: Read read
Schema command: kosmo integrations:schema wildix.wildix_list_calls --json

Parameter	Type	Required	Description
`limit`	integer	no	Maximum number of call records to return (default: 25).
`page`	integer	no	Page number for pagination (default: 1).
`date_from`	string	no	Start date for filtering calls (ISO 8601, e.g. "2026-01-01").
`date_to`	string	no	End date for filtering calls (ISO 8601, e.g. "2026-01-31").

`wildix.wildix_get_call`

Get detailed information about a specific call record by its ID.

Operation: Read read
Schema command: kosmo integrations:schema wildix.wildix_get_call --json

Parameter	Type	Required	Description
`id`	string	yes	The unique identifier of the call record.

`wildix.wildix_list_extensions`

List PBX extensions configured in the Wildix system. Supports pagination.

Operation: Read read
Schema command: kosmo integrations:schema wildix.wildix_list_extensions --json

Parameter	Type	Required	Description
`limit`	integer	no	Maximum number of extensions to return (default: 25).
`page`	integer	no	Page number for pagination (default: 1).

`wildix.wildix_get_extension`

Get detailed information about a specific PBX extension by its ID.

Operation: Read read
Schema command: kosmo integrations:schema wildix.wildix_get_extension --json

Parameter	Type	Required	Description
`id`	string	yes	The unique identifier of the extension.

`wildix.wildix_list_users`

List users configured in the Wildix PBX system. Supports pagination.

Operation: Read read
Schema command: kosmo integrations:schema wildix.wildix_list_users --json

Parameter	Type	Required	Description
`limit`	integer	no	Maximum number of users to return (default: 25).
`page`	integer	no	Page number for pagination (default: 1).

`wildix.wildix_get_current_user`

Get the profile of the currently authenticated Wildix user (the user associated with the configured access token).

Operation: Read read
Schema command: kosmo integrations:schema wildix.wildix_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.