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

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

7 functions 6 read 1 write Bearer token auth

Submit Accelo feedback View package source

Connect Accelo 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.

Accelo MCP Config for Codex

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

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

Run the Gateway Manually

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

Why Use KosmoKrator Here

Scoped tools

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

Accelo Tools Visible to Codex

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

MCP tool	Source function	Type	Description
`integration__accelo__accelo_list_tickets`	`accelo.accelo_list_tickets`	Read	List support tickets in Accelo. Returns a paginated list of tickets, optionally filtered by status.
`integration__accelo__accelo_get_ticket`	`accelo.accelo_get_ticket`	Read	Get details of a specific support ticket in Accelo by its ID.
`integration__accelo__accelo_create_ticket`	`accelo.accelo_create_ticket`	Write	Create a new support ticket in Accelo. Requires a title and body. Optionally associate with a contract and set priority.
`integration__accelo__accelo_list_tasks`	`accelo.accelo_list_tasks`	Read	List tasks in Accelo. Returns a paginated list of tasks, optionally filtered by status.
`integration__accelo__accelo_get_task`	`accelo.accelo_get_task`	Read	Get details of a specific task in Accelo by its ID.
`integration__accelo__accelo_list_projects`	`accelo.accelo_list_projects`	Read	List projects in Accelo. Returns a paginated list of projects, optionally filtered by status.
`integration__accelo__accelo_get_current_user`	`accelo.accelo_get_current_user`	Read	Get the profile of the currently authenticated Accelo user. Use this to verify credentials and see user details.

Related Accelo Pages

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