other
Freshservice MCP Integration for Codex
Connect Freshservice to Codex through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.
Connect Freshservice 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.
Freshservice MCP Config for Codex
Keep write access denied or ask-based unless the workspace is trusted.
{
"mcpServers": {
"kosmokrator-freshservice": {
"type": "stdio",
"command": "kosmo",
"args": [
"mcp:serve",
"--integration=freshservice",
"--write=deny"
]
}
}
}Run the Gateway Manually
kosmokrator mcp:serve --integration=freshservice --write=denyWhy Use KosmoKrator Here
Expose only Freshservice instead of a broad multi-service tool list.
Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.
Start read-only, then opt into ask or allow for trusted workspaces.
Freshservice Tools Visible to Codex
Codex sees stable MCP tool names generated from the Freshservice integration catalog.
| MCP tool | Source function | Type | Description |
|---|---|---|---|
integration__freshservice__freshservice_list_tickets | freshservice.freshservice_list_tickets | Read | 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. |
integration__freshservice__freshservice_get_ticket | freshservice.freshservice_get_ticket | Read | Get full details of a specific Freshservice ticket by its ID, including description, status, priority, requester, assigned agent, and custom fields. |
integration__freshservice__freshservice_create_ticket | freshservice.freshservice_create_ticket | Write | 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). |
integration__freshservice__freshservice_update_ticket | freshservice.freshservice_update_ticket | Write | Update an existing Freshservice ticket. You can change status, priority, assigned agent, add tags, or modify any writable field. |
integration__freshservice__freshservice_delete_ticket | freshservice.freshservice_delete_ticket | Write | Delete a support ticket from Freshservice. This action permanently removes the ticket and its conversations. |
integration__freshservice__freshservice_list_agents | freshservice.freshservice_list_agents | Read | List all agents (support staff) in the Freshservice account. Returns agent profiles including name, email, and availability. |
integration__freshservice__freshservice_get_agent | freshservice.freshservice_get_agent | Read | Get details of a specific Freshservice agent by their ID, including name, email, role, and availability status. |
integration__freshservice__freshservice_list_assets | freshservice.freshservice_list_assets | Read | List IT assets from Freshservice. Supports pagination. Returns asset summaries including name, asset type, and state. |
integration__freshservice__freshservice_get_asset | freshservice.freshservice_get_asset | Read | Get full details of a specific Freshservice asset by its display ID, including name, type, state, location, and custom fields. |
integration__freshservice__freshservice_get_current_user | freshservice.freshservice_get_current_user | Read | Get the profile of the currently authenticated Freshservice agent. Useful for identifying which agent is performing actions. |