Can I use Vercel as a CLI?

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

Can I expose Vercel through MCP?

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

Where are Vercel credentials stored?

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

Can I deny write access for Vercel MCP tools?

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

productivity

Vercel CLI for Headless Automation

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

7 functions 7 read 0 write API token auth

Submit Vercel feedback View package source

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

Command Shape

# Vercel CLI for Headless Automation
kosmokrator integrations:configure vercel --set token="$VERCEL_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call vercel.vercel_get_current_user '{}' --json

Discovery Before Execution

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

kosmo integrations:docs vercel --json
kosmo integrations:docs vercel.vercel_get_current_user --json
kosmo integrations:schema vercel.vercel_get_current_user --json
kosmo integrations:search "Vercel" --json
kosmo integrations:list --json

Useful Vercel CLI Functions

Function	Type	Parameters	Description
`vercel.vercel_get_current_user`	Read	none	Get the currently authenticated Vercel user profile, including username, email, and plan.
`vercel.vercel_get_deployment`	Read	id, team_id	Get details for a specific Vercel deployment by ID, including status, URL, and build logs.
`vercel.vercel_get_project`	Read	id, team_id	Get details for a specific Vercel project by ID, including framework, domains, and settings.
`vercel.vercel_list_deployments`	Read	project_id, state, target, limit, team_id	List deployments across your Vercel projects. Filter by project, state, or target.
`vercel.vercel_list_domains`	Read	limit, team_id	List all domains configured in Vercel, including verification and DNS status.
`vercel.vercel_list_projects`	Read	limit, team_id	List all Vercel projects. Returns project names, IDs, framework, and deployment status.
`vercel.vercel_list_teams`	Read	limit	List all Vercel teams you belong to, including membership roles and member counts.

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

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