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 MCP Integration for LangChain

Connect Wildix to LangChain through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

6 functions 6 read 0 write Bearer token auth

Submit Wildix feedback View package source

Connect Wildix to LangChain

Bridge LangChain agents to local KosmoKrator integration tools through MCP or headless CLI calls.

Use the MCP gateway when the agent should discover tools, or wrap kosmo integrations:call for fixed chains. The gateway is local, scoped to this integration, and starts with --write=deny so LangChain can inspect read-capable tools without receiving write access by default.

Wildix MCP Config for LangChain

Keep the gateway scoped to the integration and operation class needed by the chain.

{
  "mcpServers": {
    "kosmokrator-wildix": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=wildix",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=wildix --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Wildix instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Wildix Tools Visible to LangChain

LangChain sees stable MCP tool names generated from the Wildix integration catalog.

MCP tool	Source function	Type	Description
`integration__wildix__wildix_list_calls`	`wildix.wildix_list_calls`	Read	List call records from the Wildix PBX. Supports pagination and optional date range filtering to narrow results by period.
`integration__wildix__wildix_get_call`	`wildix.wildix_get_call`	Read	Get detailed information about a specific call record by its ID.
`integration__wildix__wildix_list_extensions`	`wildix.wildix_list_extensions`	Read	List PBX extensions configured in the Wildix system. Supports pagination.
`integration__wildix__wildix_get_extension`	`wildix.wildix_get_extension`	Read	Get detailed information about a specific PBX extension by its ID.
`integration__wildix__wildix_list_users`	`wildix.wildix_list_users`	Read	List users configured in the Wildix PBX system. Supports pagination.
`integration__wildix__wildix_get_current_user`	`wildix.wildix_get_current_user`	Read	Get the profile of the currently authenticated Wildix user (the user associated with the configured access token).

Related Wildix Pages

Wildix CLIUse direct JSON commands instead of MCP discovery. Wildix MCPFull gateway reference and MCP tool names. KosmoKrator for LangChainClient-level gateway setup.