Can I use Freshservice as a CLI?

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

Can I expose Freshservice through MCP?

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

Where are Freshservice credentials stored?

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

Can I deny write access for Freshservice MCP tools?

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

other

Freshservice CLI for Headless Automation

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

10 functions 7 read 3 write API key auth

Submit Freshservice feedback View package source

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

Command Shape

# Freshservice CLI for Headless Automation
kosmokrator integrations:configure freshservice --set api_key="$FRESHSERVICE_API_KEY" --set domain="$FRESHSERVICE_DOMAIN" --enable --read allow --write ask --json
kosmo integrations:call freshservice.freshservice_list_tickets '{"page":1,"per_page":1,"filter":"example_filter"}' --json

Discovery Before Execution

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

kosmo integrations:docs freshservice --json
kosmo integrations:docs freshservice.freshservice_list_tickets --json
kosmo integrations:schema freshservice.freshservice_list_tickets --json
kosmo integrations:search "Freshservice" --json
kosmo integrations:list --json

Useful Freshservice CLI Functions

Function	Type	Parameters	Description
`freshservice.freshservice_list_tickets`	Read	page, per_page, filter	List support tickets from Freshservice. Supports pagination and predefined filters (e.g., new_and_my_open, watching, spam, deleted). Returns ticket summaries including subject, status, priority, and requester.
`freshservice.freshservice_get_ticket`	Read	ticket_id	Get full details of a specific Freshservice ticket by its ID, including description, status, priority, requester, assigned agent, and custom fields.
`freshservice.freshservice_create_ticket`	Write	subject, description, email, priority	Create a new support ticket in Freshservice. Requires a subject and description. Optionally specify the requester email and priority (1=Low, 2=Medium, 3=High, 4=Urgent).
`freshservice.freshservice_update_ticket`	Write	ticket_id, subject, description, priority, status, responder_id, tags	Update an existing Freshservice ticket. You can change status, priority, assigned agent, add tags, or modify any writable field.
`freshservice.freshservice_delete_ticket`	Write	ticket_id	Delete a support ticket from Freshservice. This action permanently removes the ticket and its conversations.
`freshservice.freshservice_list_agents`	Read	page	List all agents (support staff) in the Freshservice account. Returns agent profiles including name, email, and availability.
`freshservice.freshservice_get_agent`	Read	agent_id	Get details of a specific Freshservice agent by their ID, including name, email, role, and availability status.
`freshservice.freshservice_list_assets`	Read	page	List IT assets from Freshservice. Supports pagination. Returns asset summaries including name, asset type, and state.
`freshservice.freshservice_get_asset`	Read	asset_id	Get full details of a specific Freshservice asset by its display ID, including name, type, state, location, and custom fields.
`freshservice.freshservice_get_current_user`	Read	none	Get the profile of the currently authenticated Freshservice agent. Useful for identifying which agent is performing actions.

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

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