Can I use Accelo as a CLI?

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

Can I expose Accelo through MCP?

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

Where are Accelo credentials stored?

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

Can I deny write access for Accelo MCP tools?

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

productivity

Accelo CLI for AI Agents

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

7 functions 6 read 1 write Bearer token auth

Submit Accelo feedback View package source

Accelo CLI Setup

Accelo can be configured headlessly with `kosmokrator integrations:configure accelo`.

# 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 accelo --set access_token="$ACCELO_ACCESS_TOKEN" --set deployment="$ACCELO_DEPLOYMENT" --enable --read allow --write ask --json
kosmokrator integrations:doctor accelo --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`	`ACCELO_ACCESS_TOKEN`	Secret `secret`	yes	Access Token
`deployment`	`ACCELO_DEPLOYMENT`	Text `string`	yes	Deployment Name
`url`	`ACCELO_URL`	URL `url`	no	Custom Base URL

Call Accelo Headlessly

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

kosmo integrations:call accelo.accelo_list_tickets '{
  "limit": 1,
  "page": 1,
  "status": "example_status"
}' --json

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

kosmo integrations:accelo accelo_list_tickets '{
  "limit": 1,
  "page": 1,
  "status": "example_status"
}' --json

Agent Discovery Commands

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

kosmo integrations:docs accelo --json
kosmo integrations:docs accelo.accelo_list_tickets --json
kosmo integrations:schema accelo.accelo_list_tickets --json
kosmo integrations:search "Accelo" --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 Accelo.

`accelo.accelo_list_tickets`

Read read

List support tickets in Accelo. Returns a paginated list of tickets, optionally filtered by status.

Parameters: limit, page, status

Generic CLI call

kosmo integrations:call accelo.accelo_list_tickets '{"limit":1,"page":1,"status":"example_status"}' --json

Provider shortcut

kosmo integrations:accelo accelo_list_tickets '{"limit":1,"page":1,"status":"example_status"}' --json

`accelo.accelo_get_ticket`

Read read

Get details of a specific support ticket in Accelo by its ID.

Parameters: id

Generic CLI call

kosmo integrations:call accelo.accelo_get_ticket '{"id":1}' --json

Provider shortcut

kosmo integrations:accelo accelo_get_ticket '{"id":1}' --json

`accelo.accelo_create_ticket`

Write write

Create a new support ticket in Accelo. Requires a title and body. Optionally associate with a contract and set priority.

Parameters: title, body, contract_id, priority

Generic CLI call

kosmo integrations:call accelo.accelo_create_ticket '{"title":"example_title","body":"example_body","contract_id":1,"priority":1}' --json

Provider shortcut

kosmo integrations:accelo accelo_create_ticket '{"title":"example_title","body":"example_body","contract_id":1,"priority":1}' --json

`accelo.accelo_list_tasks`

Read read

List tasks in Accelo. Returns a paginated list of tasks, optionally filtered by status.

Parameters: limit, page, status

Generic CLI call

kosmo integrations:call accelo.accelo_list_tasks '{"limit":1,"page":1,"status":"example_status"}' --json

Provider shortcut

kosmo integrations:accelo accelo_list_tasks '{"limit":1,"page":1,"status":"example_status"}' --json

`accelo.accelo_get_task`

Read read

Get details of a specific task in Accelo by its ID.

Parameters: id

Generic CLI call

kosmo integrations:call accelo.accelo_get_task '{"id":1}' --json

Provider shortcut

kosmo integrations:accelo accelo_get_task '{"id":1}' --json

`accelo.accelo_list_projects`

Read read

List projects in Accelo. Returns a paginated list of projects, optionally filtered by status.

Parameters: limit, page, status

Generic CLI call

kosmo integrations:call accelo.accelo_list_projects '{"limit":1,"page":1,"status":"example_status"}' --json

Provider shortcut

kosmo integrations:accelo accelo_list_projects '{"limit":1,"page":1,"status":"example_status"}' --json

`accelo.accelo_get_current_user`

Read read

Get the profile of the currently authenticated Accelo user. Use this to verify credentials and see user details.

Parameters: none

Generic CLI call

kosmo integrations:call accelo.accelo_get_current_user '{}' --json

Provider shortcut

kosmo integrations:accelo accelo_get_current_user '{}' --json

Function Schemas

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

`accelo.accelo_list_tickets`

List support tickets in Accelo. Returns a paginated list of tickets, optionally filtered by status.

Operation: Read read
Schema command: kosmo integrations:schema accelo.accelo_list_tickets --json

Parameter	Type	Required	Description
`limit`	integer	no	Number of tickets to return per page (default: 25, max: 100).
`page`	integer	no	Page number for pagination (1-based).
`status`	string	no	Filter tickets by status (e.g. "open", "closed", "resolved").

`accelo.accelo_get_ticket`

Get details of a specific support ticket in Accelo by its ID.

Operation: Read read
Schema command: kosmo integrations:schema accelo.accelo_get_ticket --json

Parameter	Type	Required	Description
`id`	integer	yes	The Accelo ticket ID.

`accelo.accelo_create_ticket`

Create a new support ticket in Accelo. Requires a title and body. Optionally associate with a contract and set priority.

Operation: Write write
Schema command: kosmo integrations:schema accelo.accelo_create_ticket --json

Parameter	Type	Required	Description
`title`	string	yes	The ticket title or subject.
`body`	string	yes	The ticket description or body content.
`contract_id`	integer	no	Optional contract ID to associate with the ticket.
`priority`	integer	no	Priority level (e.g. 1–5, where 1 is highest).

`accelo.accelo_list_tasks`

List tasks in Accelo. Returns a paginated list of tasks, optionally filtered by status.

Operation: Read read
Schema command: kosmo integrations:schema accelo.accelo_list_tasks --json

Parameter	Type	Required	Description
`limit`	integer	no	Number of tasks to return per page (default: 25, max: 100).
`page`	integer	no	Page number for pagination (1-based).
`status`	string	no	Filter tasks by status (e.g. "open", "completed", "in_progress").

`accelo.accelo_get_task`

Get details of a specific task in Accelo by its ID.

Operation: Read read
Schema command: kosmo integrations:schema accelo.accelo_get_task --json

Parameter	Type	Required	Description
`id`	integer	yes	The Accelo task ID.

`accelo.accelo_list_projects`

List projects in Accelo. Returns a paginated list of projects, optionally filtered by status.

Operation: Read read
Schema command: kosmo integrations:schema accelo.accelo_list_projects --json

Parameter	Type	Required	Description
`limit`	integer	no	Number of projects to return per page (default: 25, max: 100).
`page`	integer	no	Page number for pagination (1-based).
`status`	string	no	Filter projects by status (e.g. "open", "completed", "in_progress").

`accelo.accelo_get_current_user`

Get the profile of the currently authenticated Accelo user. Use this to verify credentials and see user details.

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