Can I use Cursor as a CLI?

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

Can I expose Cursor through MCP?

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

Where are Cursor credentials stored?

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

Can I deny write access for Cursor MCP tools?

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

other

Cursor CLI for Shell Scripts

Use the Cursor CLI for shell scripts with headless JSON commands, schema discovery, credentials, and permission controls.

4 functions 4 read 0 write API key auth

Submit Cursor feedback View package source

Cursor CLI for Shell Scripts

Call integration functions from shell scripts with stable JSON input and output.

Use shell scripts for small local automations that need one or more integration calls. 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 Shell Scripts
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 --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 Cursor CLI Pages

CI Cursor CLI for CI. Cron Jobs Cursor CLI for cron jobs. Headless Automation Cursor CLI for headless automation. Coding Agents Cursor CLI for coding agents.