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 MCP Integration for Claude Code

Connect Cursor to Claude Code through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

4 functions 4 read 0 write API key auth

Submit Cursor feedback View package source

Connect Cursor to Claude Code

Connect local KosmoKrator integrations to Claude Code through one scoped MCP gateway entry.

Add KosmoKrator as a stdio MCP server in the Claude Code project config and select the integrations that should be visible. The gateway is local, scoped to this integration, and starts with --write=deny so Claude Code can inspect read-capable tools without receiving write access by default.

Cursor MCP Config for Claude Code

Claude Code can launch the local kosmo binary directly from the project MCP config.

{
  "mcpServers": {
    "kosmokrator-cursor": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=cursor",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=cursor --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Cursor instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Cursor Tools Visible to Claude Code

Claude Code sees stable MCP tool names generated from the Cursor integration catalog.

MCP tool	Source function	Type	Description
`integration__cursor__cursor_list_workspaces`	`cursor.cursor_list_workspaces`	Read	List all Cursor workspaces accessible to the authenticated user. Returns workspace IDs you can use with other Cursor tools.
`integration__cursor__cursor_get_workspace`	`cursor.cursor_get_workspace`	Read	Get details for a specific Cursor workspace by its ID.
`integration__cursor__cursor_list_team_members`	`cursor.cursor_list_team_members`	Read	List all team members in a Cursor workspace. Returns member names, emails, and roles.
`integration__cursor__cursor_list_extensions`	`cursor.cursor_list_extensions`	Read	List all extensions installed in a Cursor workspace. Returns extension names, identifiers, and versions.

Related Cursor Pages

Cursor CLIUse direct JSON commands instead of MCP discovery. Cursor MCPFull gateway reference and MCP tool names. KosmoKrator for Claude CodeClient-level gateway setup.