Can I use Abyssale as a CLI?

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

Can I expose Abyssale through MCP?

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

Where are Abyssale credentials stored?

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

Can I deny write access for Abyssale MCP tools?

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

media

Abyssale CLI for Headless Automation

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

7 functions 6 read 1 write Bearer token auth

Submit Abyssale feedback View package source

Abyssale 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 Abyssale CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Abyssale CLI for Headless Automation
kosmokrator integrations:configure abyssale --set access_token="$ABYSSALE_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call abyssale.abyssale_list_generations '{"page":1,"limit":1,"status":"example_status"}' --json

Discovery Before Execution

Agents and scripts can inspect Abyssale docs and schemas before choosing a function.

kosmo integrations:docs abyssale --json
kosmo integrations:docs abyssale.abyssale_list_generations --json
kosmo integrations:schema abyssale.abyssale_list_generations --json
kosmo integrations:search "Abyssale" --json
kosmo integrations:list --json

Useful Abyssale CLI Functions

Function	Type	Parameters	Description
`abyssale.abyssale_list_generations`	Read	page, limit, status	List image generation jobs from Abyssale. Returns a paginated list of generations, optionally filtered by status (e.g., "finished", "processing", "failed").
`abyssale.abyssale_get_generation`	Read	id	Get details of a specific image generation from Abyssale, including its status, output URLs, and applied modifications.
`abyssale.abyssale_create_generation`	Write	template_id, format_ids, modifications	Generate images from an Abyssale template. Specify the template, one or more output format IDs, and element modifications (text, images, colors) to customize the output.
`abyssale.abyssale_list_templates`	Read	page, limit	List available design templates from Abyssale. Returns a paginated list of templates with their IDs and names.
`abyssale.abyssale_get_template`	Read	id	Get details of a specific Abyssale template, including its available formats, elements, and layers that can be modified.
`abyssale.abyssale_list_formats`	Read	page, limit	List available output formats from Abyssale. Formats define the size and dimensions of generated images (e.g., 1200x628 Facebook post, 1080x1080 Instagram square).
`abyssale.abyssale_get_current_user`	Read	none	Get the profile of the currently authenticated Abyssale user. Useful for verifying API credentials and retrieving account information.

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 Abyssale CLI Pages

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