Can I use Sinch as a CLI?

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

Can I expose Sinch through MCP?

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

Where are Sinch credentials stored?

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

Can I deny write access for Sinch MCP tools?

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

communication

Sinch MCP Integration for Codex

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

7 functions 6 read 1 write API token auth

Submit Sinch feedback View package source

Connect Sinch to Codex

Use KosmoKrator as a local MCP proxy for Codex so coding sessions can reach selected integrations with explicit write policy.

Register kosmo mcp:serve as a local stdio server and choose the integration allowlist. The gateway is local, scoped to this integration, and starts with --write=deny so Codex can inspect read-capable tools without receiving write access by default.

Sinch MCP Config for Codex

Keep write access denied or ask-based unless the workspace is trusted.

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

Run the Gateway Manually

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

Why Use KosmoKrator Here

Scoped tools

Expose only Sinch 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.

Sinch Tools Visible to Codex

Codex sees stable MCP tool names generated from the Sinch integration catalog.

MCP tool	Source function	Type	Description
`integration__sinch__sinch_get_group`	`sinch.sinch_get_group`	Read	Get details for a specific group in your Sinch account.
`integration__sinch__sinch_get_phone_number`	`sinch.sinch_get_phone_number`	Read	Get details for a specific phone number in your Sinch account.
`integration__sinch__sinch_list_batches`	`sinch.sinch_list_batches`	Read	List all message batches in your Sinch account with pagination.
`integration__sinch__sinch_list_groups`	`sinch.sinch_list_groups`	Read	List all groups in your Sinch account with pagination.
`integration__sinch__sinch_list_messages`	`sinch.sinch_list_messages`	Read	List inbound and outbound SMS messages from Sinch. Supports filtering by direction, recipient, sender, and date range.
`integration__sinch__sinch_list_phone_numbers`	`sinch.sinch_list_phone_numbers`	Read	List all rented phone numbers in your Sinch account with pagination.
`integration__sinch__sinch_send_sms`	`sinch.sinch_send_sms`	Write	Send an SMS message to one or more recipients via Sinch. Requires sender phone number, recipient(s), and message body.

Related Sinch Pages

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