other
Cursor CLI for Headless Automation
Use the Cursor CLI for headless automation with headless JSON commands, schema discovery, credentials, and permission controls.
4 functions 4 read 0 write API key auth
Cursor 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 Cursor CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.
Command Shape
# Cursor CLI for Headless Automation
kosmokrator integrations:configure cursor --set api_key="$CURSOR_API_KEY" --enable --read allow --write ask --json
kosmo integrations:call cursor.cursor_list_workspaces '{}' --json Discovery Before Execution
Agents and scripts can inspect Cursor docs and schemas before choosing a function.
kosmo integrations:docs cursor --json
kosmo integrations:docs cursor.cursor_list_workspaces --json
kosmo integrations:schema cursor.cursor_list_workspaces --json
kosmo integrations:search "Cursor" --json
kosmo integrations:list --json Useful Cursor CLI Functions
| Function | Type | Parameters | Description |
|---|---|---|---|
cursor.cursor_list_workspaces | Read | none | List all Cursor workspaces accessible to the authenticated user. Returns workspace IDs you can use with other Cursor tools. |
cursor.cursor_get_workspace | Read | workspace_id | Get details for a specific Cursor workspace by its ID. |
cursor.cursor_list_team_members | Read | workspace_id | List all team members in a Cursor workspace. Returns member names, emails, and roles. |
cursor.cursor_list_extensions | Read | workspace_id | List all extensions installed in a Cursor workspace. Returns extension names, identifiers, and versions. |
Automation Notes
- Use
--jsonfor machine-readable output. - Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
- Configure read/write policy before unattended runs; use
--forceonly for trusted automation. - Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.