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 Headless Automation

Use the Wildix CLI for headless automation with headless JSON commands, schema discovery, credentials, and permission controls.

6 functions 6 read 0 write Bearer token auth

Submit Wildix feedback View package source

Wildix CLI for Headless Automation

Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers.

Use headless automation when another tool needs a stable local command surface. The Wildix CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Wildix CLI for Headless Automation
kosmokrator integrations:configure wildix --set access_token="$WILDIX_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call wildix.wildix_list_calls '{"limit":1,"page":1,"date_from":"example_date_from","date_to":"example_date_to"}' --json

Discovery Before Execution

Agents and scripts can inspect Wildix docs and schemas 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

Useful Wildix CLI Functions

Function	Type	Parameters	Description
`wildix.wildix_list_calls`	Read	limit, page, date_from, date_to	List call records from the Wildix PBX. Supports pagination and optional date range filtering to narrow results by period.
`wildix.wildix_get_call`	Read	id	Get detailed information about a specific call record by its ID.
`wildix.wildix_list_extensions`	Read	limit, page	List PBX extensions configured in the Wildix system. Supports pagination.
`wildix.wildix_get_extension`	Read	id	Get detailed information about a specific PBX extension by its ID.
`wildix.wildix_list_users`	Read	limit, page	List users configured in the Wildix PBX system. Supports pagination.
`wildix.wildix_get_current_user`	Read	none	Get the profile of the currently authenticated Wildix user (the user associated with the configured access token).

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related Wildix CLI Pages

CI Wildix CLI for CI. Cron Jobs Wildix CLI for cron jobs. Shell Scripts Wildix CLI for shell scripts. Coding Agents Wildix CLI for coding agents.