vercel-automation
"Automate Vercel tasks via Rube MCP (Composio): manage deployments, domains, DNS, env vars, projects, and teams. Always search tools first for current schemas." requires: mcp: [rube]
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- 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." requires: mcp: [rube]
03 SKILL.md 正文
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:
- Domain must be added to the Vercel account before DNS management
- SSL certificates are auto-provisioned but may take time for new domains
- CNAME records at the apex domain are not supported; use A records instead
- MX records require priority values
5. Manage Projects
When to use: User wants to list, inspect, or update project settings
Tool sequence:
VERCEL_LIST_PROJECTS- List all projects [Required]VERCEL_GET_PROJECT- Get detailed project information [Optional]VERCEL_UPDATE_PROJECT- Modify project settings [Optional]
Key parameters:
idOrName: Project ID or name for lookupname: Project name for updatesframework: Framework preset (e.g., 'nextjs', 'vite', 'remix')buildCommand: Custom build command overriderootDirectory: Root directory if not repo root
Pitfalls:
- Project names are globally unique within a team/account
- Changing framework settings affects subsequent deployments
rootDirectoryis relative to the repository root
6. Team Management
When to use: User wants to view team info or list team members
Tool sequence:
VERCEL_LIST_TEAMS- List all teams the user belongs to [Required]VERCEL_GET_TEAM- Get detailed team information [Optional]VERCEL_GET_TEAM_MEMBERS- List members of a specific team [Optional]
Key parameters:
teamId: Team identifierlimit: Number of results per pagerole: Filter members by role
Pitfalls:
- Team operations require appropriate team-level permissions
- Personal accounts have no teams; team endpoints return empty results
- Member roles include 'OWNER', 'MEMBER', 'DEVELOPER', 'VIEWER'
Common Patterns
ID Resolution
Project name -> Project ID:
1. Call VERCEL_LIST_PROJECTS
2. Find project by name in response
3. Extract id field for subsequent operations
Domain -> DNS Records:
1. Call VERCEL_GET_DNS_RECORDS with domain name
2. Extract record IDs for update/delete operations
Pagination
- Use
limitparameter to control page size - Check response for pagination tokens or
nextfields - Continue fetching until no more pages are indicated
Known Pitfalls
Deployment States:
- States include: INITIALIZING, ANALYZING, BUILDING, DEPLOYING, READY, ERROR, CANCELED, QUEUED
- Only READY deployments are live and serving traffic
- ERROR deployments should be inspected via logs for failure details
Environment Variables:
- Secret type vars are write-only; values cannot be retrieved after creation
- Env vars are scoped to environments (production, preview, development)
- A redeployment is needed for env var changes to take effect
Rate Limits:
- Vercel API has rate limits per endpoint
- Implement backoff on 429 responses
- Batch operations where possible to reduce API calls
Quick Reference
| Task | Tool Slug | Key Params |
|---|---|---|
| List projects | VERCEL_LIST_PROJECTS | limit |
| Get project details | VERCEL_GET_PROJECT | idOrName |
| Update project | VERCEL_UPDATE_PROJECT | idOrName, name, framework |
| List deployments | VERCEL_LIST_ALL_DEPLOYMENTS | projectId, state, limit |
| Get deployment | VERCEL_GET_DEPLOYMENT | idOrUrl |
| Create deployment | VERCEL_CREATE_NEW_DEPLOYMENT | name, target, gitSource |
| Deployment logs | VERCEL_GET_DEPLOYMENT_LOGS | deploymentId |
| Runtime logs | VERCEL_GET_RUNTIME_LOGS | deploymentId |
| List env vars | VERCEL_LIST_ENV_VARIABLES | projectId |
| Add env var | VERCEL_ADD_ENVIRONMENT_VARIABLE | projectId, key, value, target |
| Delete env var | VERCEL_DELETE_ENVIRONMENT_VARIABLE | projectId, id |
| Get domain | VERCEL_GET_DOMAIN | domain |
| Get domain config | VERCEL_GET_DOMAIN_CONFIG | domain |
| List DNS records | VERCEL_GET_DNS_RECORDS | domain |
| Create DNS record | VERCEL_CREATE_DNS_RECORD | domain, name, type, value |
| Update DNS record | VERCEL_UPDATE_DNS_RECORD | domain, recordId |
| List project domains | VERCEL_LIST_PROJECT_DOMAINS | projectId |
| List teams | VERCEL_LIST_TEAMS | (none) |
| Get team | VERCEL_GET_TEAM | teamId |
| Get team members | VERCEL_GET_TEAM_MEMBERS | teamId, limit |
04 同仓库更多 Skills
web-performance-optimization
Optimize website and web application performance including loading speed, Core Web Vitals, bundle size, caching strategies, and runtime performance
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
wcag-audit-patterns
Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing accessible design patterns.
ui-ux-pro-max
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.
stitch-ui-design
Expert guide for creating effective prompts for Google Stitch AI UI design tool. Use when user wants to design UI/UX in Stitch, create app interfaces, generate mobile/web designs, or needs help crafting Stitch prompts. Covers prompt structure, specificity techniques, iteration strategies, and design-to-code workflows for Stitch by Google.
scroll-experience
Expert in building immersive scroll-driven experiences - parallax storytelling, scroll animations, interactive narratives, and cinematic web experiences. Like NY Times interactives, Apple product pages, and award-winning web experiences. Makes websites feel like experiences, not just pages. Use when: scroll animation, parallax, scroll storytelling, interactive story, cinematic website.