
About
Automate Vercel tasks via Rube MCP (Composio): manage deployments, domains, DNS, env vars, projects, and teams. Always search tools first for current schemas.
name: vercel-automation description: "Automate Vercel tasks via Rube MCP (Composio): manage deployments, domains, DNS, env vars, projects, and teams. Always search tools first for current schemas." risk: critical source: community date_added: "2026-02-27"
Vercel Automation via Rube MCP
Automate Vercel platform operations through Composio's Vercel toolkit via Rube MCP.
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Vercel connection via
RUBE_MANAGE_CONNECTIONSwith toolkitvercel - Always call
RUBE_SEARCH_TOOLSfirst to get current tool schemas
Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitvercel - If connection is not ACTIVE, follow the returned auth link to complete Vercel OAuth
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. Monitor and Inspect Deployments
When to use: User wants to list, inspect, or debug deployments
Tool sequence:
VERCEL_LIST_ALL_DEPLOYMENTSorVERCEL_GET_DEPLOYMENTS- List deployments with filters [Required]VERCEL_GET_DEPLOYMENTorVERCEL_GET_DEPLOYMENT_DETAILS- Get specific deployment info [Optional]VERCEL_GET_DEPLOYMENT_LOGSorVERCEL_GET_RUNTIME_LOGS- View build/runtime logs [Optional]VERCEL_GET_DEPLOYMENT_EVENTS- Get deployment event timeline [Optional]VERCEL_LIST_DEPLOYMENT_CHECKS- View deployment check results [Optional]
Key parameters:
projectId: Filter deployments by projectstate: Filter by deployment state (e.g., 'READY', 'ERROR', 'BUILDING')limit: Number of deployments to returntarget: Filter by environment ('production', 'preview')deploymentIdoridOrUrl: Specific deployment identifier
Pitfalls:
- Deployment IDs and URLs are both accepted as identifiers in most endpoints
- Build logs and runtime logs are separate; use the appropriate tool
VERCEL_GET_DEPLOYMENT_LOGSreturns build logs;VERCEL_GET_RUNTIME_LOGSreturns serverless function logs- Deployment events include status transitions and are useful for debugging timing issues
2. Create and Manage Deployments
When to use: User wants to trigger a new deployment
Tool sequence:
VERCEL_LIST_PROJECTS- Find the target project [Prerequisite]VERCEL_CREATE_NEW_DEPLOYMENT- Trigger a new deployment [Required]VERCEL_GET_DEPLOYMENT- Monitor deployment progress [Optional]
Key parameters:
name: Project name for the deploymenttarget: Deployment target ('production' or 'preview')gitSource: Git repository source with ref/branch infofiles: Array of file objects for file-based deployments
Pitfalls:
- Either
gitSourceorfilesmust be provided, not both - Git-based deployments require proper repository integration
- Production deployments update the production domain alias automatically
- Deployment creation is asynchronous; poll with GET_DEPLOYMENT for status
3. Manage Environment Variables
When to use: User wants to add, list, or remove environment variables for a project
Tool sequence:
VERCEL_LIST_PROJECTS- Find the project ID [Prerequisite]VERCEL_LIST_ENV_VARIABLES- List existing env vars [Required]VERCEL_ADD_ENVIRONMENT_VARIABLE- Add a new env var [Optional]VERCEL_DELETE_ENVIRONMENT_VARIABLE- Remove an env var [Optional]
Key parameters:
projectId: Target project identifierkey: Environment variable namevalue: Environment variable valuetarget: Array of environments ('production', 'preview', 'development')type: Variable type ('plain', 'secret', 'encrypted', 'sensitive')
Pitfalls:
- Environment variable names must be unique per target environment
type: 'secret'variables cannot be read back after creation; only the ID is returned- Deleting an env var requires both
projectIdand the env varid(not the key name) - Changes require a new deployment to take effect
4. Manage Domains and DNS
When to use: User wants to configure custom domains or manage DNS records
Tool sequence:
VERCEL_GET_DOMAIN- Check domain status and configuration [Required]VERCEL_GET_DOMAIN_CONFIG- Get DNS/SSL configuration details [Optional]VERCEL_LIST_PROJECT_DOMAINS- List domains attached to a project [Optional]VERCEL_GET_DNS_RECORDS- List DNS records for a domain [Optional]VERCEL_CREATE_DNS_RECORD- Add a new DNS record [Optional]VERCEL_UPDATE_DNS_RECORD- Modify an existing DNS record [Optional]
Key parameters:
domain: Domain name (e.g., 'example.com')name: DNS record name/subdomaintype: DNS record type ('A', 'AAAA', 'CNAME', 'MX', 'TXT', 'SRV')value: DNS record valuettl: Time-to-live in seconds
Pitfalls
