Can I use Baserow as a CLI?

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

Can I expose Baserow through MCP?

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

Where are Baserow credentials stored?

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

Can I deny write access for Baserow MCP tools?

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

database

Baserow MCP Integration for Cursor

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

7 functions 4 read 3 write Bearer token auth

Submit Baserow feedback View package source

Connect Baserow to Cursor

Expose selected local integrations to Cursor through KosmoKrator without configuring each service as its own MCP server.

Create or update .cursor/mcp.json with a KosmoKrator stdio server entry. The gateway is local, scoped to this integration, and starts with --write=deny so Cursor can inspect read-capable tools without receiving write access by default.

Baserow MCP Config for Cursor

Use the same KosmoKrator install and integration credentials that power terminal and headless runs.

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

Run the Gateway Manually

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

Why Use KosmoKrator Here

Scoped tools

Expose only Baserow 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.

Baserow Tools Visible to Cursor

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

MCP tool	Source function	Type	Description
`integration__baserow__baserow_create_row`	`baserow.baserow_create_row`	Write	Create a new row in a Baserow database table. Provide field data as a JSON object mapping field names to values.
`integration__baserow__baserow_delete_row`	`baserow.baserow_delete_row`	Write	Delete a row from a Baserow database table. This action is permanent and cannot be undone.
`integration__baserow__baserow_get_current_user`	`baserow.baserow_get_current_user`	Read	Get the currently authenticated Baserow user profile. Returns user details including name, email, and workspace memberships.
`integration__baserow__baserow_get_row`	`baserow.baserow_get_row`	Read	Get a single row from a Baserow database table by its row ID. Returns all field values for the row.
`integration__baserow__baserow_list_databases`	`baserow.baserow_list_databases`	Read	List all databases (applications) in the Baserow workspace. Returns database names, IDs, and types for navigation.
`integration__baserow__baserow_list_tables`	`baserow.baserow_list_tables`	Read	List rows in a Baserow database table. Supports pagination and optional filters to narrow results by field values.
`integration__baserow__baserow_update_row`	`baserow.baserow_update_row`	Write	Update an existing row in a Baserow database table. Provide field data as a JSON object with field names and new values. Only specified fields are updated.

Related Baserow Pages

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