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 MCP Integration for Codex

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

7 functions 7 read 0 write API token auth

Submit Vercel feedback View package source

Connect Vercel to Codex

Use KosmoKrator as a local MCP proxy for Codex so coding sessions can reach selected integrations with explicit write policy.

Register kosmo mcp:serve as a local stdio server and choose the integration allowlist. The gateway is local, scoped to this integration, and starts with --write=deny so Codex can inspect read-capable tools without receiving write access by default.

Vercel MCP Config for Codex

Keep write access denied or ask-based unless the workspace is trusted.

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

Run the Gateway Manually

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

Why Use KosmoKrator Here

Scoped tools

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

Vercel Tools Visible to Codex

Codex sees stable MCP tool names generated from the Vercel integration catalog.

MCP tool	Source function	Type	Description
`integration__vercel__vercel_get_current_user`	`vercel.vercel_get_current_user`	Read	Get the currently authenticated Vercel user profile, including username, email, and plan.
`integration__vercel__vercel_get_deployment`	`vercel.vercel_get_deployment`	Read	Get details for a specific Vercel deployment by ID, including status, URL, and build logs.
`integration__vercel__vercel_get_project`	`vercel.vercel_get_project`	Read	Get details for a specific Vercel project by ID, including framework, domains, and settings.
`integration__vercel__vercel_list_deployments`	`vercel.vercel_list_deployments`	Read	List deployments across your Vercel projects. Filter by project, state, or target.
`integration__vercel__vercel_list_domains`	`vercel.vercel_list_domains`	Read	List all domains configured in Vercel, including verification and DNS status.
`integration__vercel__vercel_list_projects`	`vercel.vercel_list_projects`	Read	List all Vercel projects. Returns project names, IDs, framework, and deployment status.
`integration__vercel__vercel_list_teams`	`vercel.vercel_list_teams`	Read	List all Vercel teams you belong to, including membership roles and member counts.

Related Vercel Pages

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