Can I use Taiga as a CLI?

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

Can I expose Taiga through MCP?

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

Where are Taiga credentials stored?

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

Can I deny write access for Taiga MCP tools?

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

productivity

Taiga CLI for Cron Jobs

Use the Taiga CLI for cron jobs with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 6 read 1 write Bearer token auth

Submit Taiga feedback View package source

Taiga CLI for Cron Jobs

Schedule repeatable integration workflows from cron while keeping credentials in KosmoKrator config.

Use the headless CLI from cron when an operation should run without an interactive agent session. The Taiga CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Taiga CLI for Cron Jobs
kosmokrator integrations:configure taiga --set access_token="$TAIGA_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call taiga.taiga_list_projects '{"membership":"example_membership","slug":"example_slug","order_by":"example_order_by","page":1,"page_size":1}' --json

Discovery Before Execution

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

kosmo integrations:docs taiga --json
kosmo integrations:docs taiga.taiga_list_projects --json
kosmo integrations:schema taiga.taiga_list_projects --json
kosmo integrations:search "Taiga" --json
kosmo integrations:list --json

Useful Taiga CLI Functions

Function	Type	Parameters	Description
`taiga.taiga_list_projects`	Read	membership, slug, order_by, page, page_size	List all Taiga projects you have access to. Returns project names, slugs, and descriptions that you can use to query user stories and issues.
`taiga.taiga_get_project`	Read	id	Get detailed information about a specific Taiga project by its ID. Returns project name, slug, description, statuses, and membership details.
`taiga.taiga_list_user_stories`	Read	project, project__slug, status, milestone, assigned_to, tags, order_by, page, page_size	List user stories from Taiga. Filter by project, status, milestone, or assignee. Returns story subjects, descriptions, and statuses.
`taiga.taiga_get_user_story`	Read	id	Get detailed information about a specific Taiga user story by its ID. Returns the full story with subject, description, status, assignee, and points.
`taiga.taiga_create_user_story`	Write	project, subject, description, status, assigned_to, milestone, tags, points	Create a new user story in a Taiga project. Requires project ID and subject. Optionally include description, tags, status, and assignee.
`taiga.taiga_list_issues`	Read	project, project__slug, status, priority, severity, assigned_to, tags, order_by, page, page_size	List issues from Taiga. Filter by project, status, priority, severity, or assignee. Returns issue subjects, descriptions, and statuses.
`taiga.taiga_get_current_user`	Read	none	Get the currently authenticated Taiga user profile. Returns user details like full name, username, and email.

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

CI Taiga CLI for CI. Shell Scripts Taiga CLI for shell scripts. Headless Automation Taiga CLI for headless automation. Coding Agents Taiga CLI for coding agents.