Can I use Kintone as a CLI?

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

Can I expose Kintone through MCP?

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

Where are Kintone credentials stored?

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

Can I deny write access for Kintone MCP tools?

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

productivity

Kintone CLI for Headless Automation

Use the Kintone CLI for headless automation with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 6 read 1 write Bearer token auth

Submit Kintone feedback View package source

Kintone 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 Kintone CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Kintone CLI for Headless Automation
kosmokrator integrations:configure kintone --set access_token="$KINTONE_ACCESS_TOKEN" --set domain="$KINTONE_DOMAIN" --enable --read allow --write ask --json
kosmo integrations:call kintone.kintone_list_records '{"app":1,"query":"example_query","fields":"example_fields","limit":1,"offset":1}' --json

Discovery Before Execution

Agents and scripts can inspect Kintone docs and schemas before choosing a function.

kosmo integrations:docs kintone --json
kosmo integrations:docs kintone.kintone_list_records --json
kosmo integrations:schema kintone.kintone_list_records --json
kosmo integrations:search "Kintone" --json
kosmo integrations:list --json

Useful Kintone CLI Functions

Function	Type	Parameters	Description
`kintone.kintone_list_records`	Read	app, query, fields, limit, offset	Retrieve records from a Kintone app. Supports filtering with a query string, selecting specific fields, and pagination with limit/offset. Use this to search and list data stored in any Kintone app.
`kintone.kintone_get_record`	Read	app, id	Retrieve a single record from a Kintone app by its record ID. Returns all field values for the record.
`kintone.kintone_create_record`	Write	app, record	Create a new record in a Kintone app. The record parameter is an object keyed by field codes, each containing a "value" property (e.g., {"Title": {"value": "Hello"}, "Number": {"value": 42}}).
`kintone.kintone_list_apps`	Read	limit, offset	List available Kintone apps. Returns app IDs, names, and descriptions to help discover which apps are accessible.
`kintone.kintone_get_app`	Read	id	Get details of a specific Kintone app, including its name, description, and settings.
`kintone.kintone_list_spaces`	Read	limit, offset	List Kintone spaces. Spaces are collaborative workspaces that contain apps, threads, and other resources.
`kintone.kintone_get_current_user`	Read	none	Get the profile of the currently authenticated Kintone user, including name, email, and user settings.

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 Kintone CLI Pages

CI Kintone CLI for CI. Cron Jobs Kintone CLI for cron jobs. Shell Scripts Kintone CLI for shell scripts. Coding Agents Kintone CLI for coding agents.