Can I use Neon as a CLI?

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

Can I expose Neon through MCP?

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

Where are Neon credentials stored?

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

Can I deny write access for Neon MCP tools?

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

data

Neon CLI for Headless Automation

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

7 functions 6 read 1 write Bearer token auth

Submit Neon feedback View package source

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

Command Shape

# Neon CLI for Headless Automation
kosmokrator integrations:configure neon --set access_token="$NEON_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call neon.neon_list_projects '{}' --json

Discovery Before Execution

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

kosmo integrations:docs neon --json
kosmo integrations:docs neon.neon_list_projects --json
kosmo integrations:schema neon.neon_list_projects --json
kosmo integrations:search "Neon" --json
kosmo integrations:list --json

Useful Neon CLI Functions

Function	Type	Parameters	Description
`neon.neon_list_projects`	Read	none	List all Neon projects in the organization. Returns project IDs, names, region, and status.
`neon.neon_get_project`	Read	project_id	Get details for a specific Neon project by ID. Returns full project information including connection strings, branches, and settings.
`neon.neon_create_project`	Write	name, region_id, pg_version, branch_name, database_name	Create a new Neon project. Requires a name. Optionally specify a region and Postgres version.
`neon.neon_list_branches`	Read	project_id	List all branches in a Neon project. Returns branch IDs, names, status, and parent branch info.
`neon.neon_get_branch`	Read	project_id, branch_id	Get details for a specific branch in a Neon project. Returns branch configuration, endpoints, and state.
`neon.neon_list_databases`	Read	project_id, branch_id	List all databases in a Neon project branch. Returns database names, owners, and sizes.
`neon.neon_get_current_user`	Read	none	Get information about the current authenticated Neon user, including email, name, and organization membership.

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

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