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 MCP Integration for Vercel AI SDK

Connect Neon to Vercel AI SDK through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 6 read 1 write Bearer token auth

Submit Neon feedback View package source

Connect Neon to Vercel AI SDK

Use KosmoKrator as a local integration gateway for Vercel AI SDK agents and scripts.

Create an MCP client that starts or connects to the KosmoKrator gateway for the selected integration. The gateway is local, scoped to this integration, and starts with --write=deny so Vercel AI SDK can inspect read-capable tools without receiving write access by default.

Neon MCP Config for Vercel AI SDK

Prefer CLI JSON calls when a workflow only needs one deterministic integration operation.

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

Run the Gateway Manually

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

Why Use KosmoKrator Here

Scoped tools

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

Neon Tools Visible to Vercel AI SDK

Vercel AI SDK sees stable MCP tool names generated from the Neon integration catalog.

MCP tool	Source function	Type	Description
`integration__neon__neon_list_projects`	`neon.neon_list_projects`	Read	List all Neon projects in the organization. Returns project IDs, names, region, and status.
`integration__neon__neon_get_project`	`neon.neon_get_project`	Read	Get details for a specific Neon project by ID. Returns full project information including connection strings, branches, and settings.
`integration__neon__neon_create_project`	`neon.neon_create_project`	Write	Create a new Neon project. Requires a name. Optionally specify a region and Postgres version.
`integration__neon__neon_list_branches`	`neon.neon_list_branches`	Read	List all branches in a Neon project. Returns branch IDs, names, status, and parent branch info.
`integration__neon__neon_get_branch`	`neon.neon_get_branch`	Read	Get details for a specific branch in a Neon project. Returns branch configuration, endpoints, and state.
`integration__neon__neon_list_databases`	`neon.neon_list_databases`	Read	List all databases in a Neon project branch. Returns database names, owners, and sizes.
`integration__neon__neon_get_current_user`	`neon.neon_get_current_user`	Read	Get information about the current authenticated Neon user, including email, name, and organization membership.

Related Neon Pages

Neon CLIUse direct JSON commands instead of MCP discovery. Neon MCPFull gateway reference and MCP tool names. KosmoKrator for Vercel AI SDKClient-level gateway setup.