Menu
Mattering Automations connector

Vercel MCP nodes for the workflows around your deploys, not just the deploys

Connect one access token and 50 Vercel operations become workflow steps that chain with every other connector: ship a release when an approval task moves, roll production back when a build fails, rotate an environment variable everywhere it lives, and flip a feature flag in Global Config, all in one run with one history.

50 ready-made nodes One credential to connect Works with Claude, ChatGPT, and Matter

What the Vercel MCP connector does

The Vercel connector for Mattering Automations is 50 nodes, 27 reads and 23 actions, covering projects (full create, read, update, delete), deployments (create from git or redeploy, cancel, delete, promote to production, plus build logs, source files, and integration checks), environment variables, account domains and Vercel DNS records, project domain attachment and verification, aliases, Global Config key-value stores, webhook management, team reads, and token auditing. Vercel publishes 273 REST paths; this is the automation-shaped surface curated out of them, not a dump.

The connector carries Vercel's sharp edges so your workflows do not have to. Vercel versions every endpoint individually (v10 projects sits next to v13 deployments), and each node pins the exact version prefix from Vercel's own published OpenAPI document. Team-owned resources need a teamId query parameter, so 48 of the 50 nodes take an optional teamId field, with Vercel: List Teams supplying the id. List pagination differs per family, and each node's field descriptions say which cursor to pass where.

Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. Vercel also operates its own official MCP server, and it is good at what it does. The reason to run Vercel here is placement: these nodes live on the same canvas as your helpdesk, CRM, databases, and task manager, inside scheduled workflows with run history and human approval steps, so a failed build can open a task, a content update can trigger a redeploy, and an incident can roll production back, without glue code.

The risk model is stated plainly. Five nodes permanently destroy data: Vercel: Delete Project, Vercel: Delete Deployment, Vercel: Delete Domain, Vercel: Delete DNS Record, and Vercel: Delete Environment Variable. Each one says so in its description. The traffic-shifting moves are reversible by design: Vercel: Promote Deployment to Production and Vercel: Assign Alias to Deployment both undo by pointing back at the previous deployment. And the registrar's purchase, renewal, and transfer endpoints are deliberately not on the canvas, because they charge real money; Vercel: Check Domain Availability stays because availability is a free read.

One connection, three surfaces

  • Visual automations. Drag Vercel nodes onto the canvas and wire them to triggers, conditions, and other apps.
  • AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
  • The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.

Every Vercel node, ready to drop on the canvas

50 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.

Read and query nodes 27

Vercel: Check Domain Availability

Check whether a domain name is available to register, via Vercel's registrar. A free read: it checks availability only and never purchases anything.

Vercel: Get Alias

Get one alias by its ID or hostname, including which deployment it currently points at.

Vercel: Get Current User

Return the user the access token belongs to: id, email, username, and plan. Free and parameterless, so it doubles as the credential health check: a bad token gets a 403, a good one identifies the account.

Vercel: Get Deployment

Get one deployment's full record by ID or URL hostname: build state, aliases, target environment, regions, timings, and creator. Poll this after a redeploy to wait for readyState READY or ERROR.

Vercel: Get Domain

Get one account domain's record: nameservers (actual and intended), registrar service type, expiry, and verification status.

Vercel: Get Domain Configuration

Check how a domain is configured for Vercel: whether its DNS is misconfigured, which nameservers it uses, and whether it is served by Vercel's edge. The go-to diagnostic when a domain will not verify.

Vercel: Get Environment Variable

Get one environment variable by its ID, with the DECRYPTED value for plain and encrypted types (sensitive-type values cannot be read back). The value lands in the execution record, so wire it straight where it is needed.

Vercel: Get Global Config

Get one Global Config's metadata by ID: slug, owner, digest, size, and item count (not the items themselves).

Vercel: Get Project

Get one project's full record by ID or name: build settings, framework, git link, production target, and latest deployments.

Vercel: Get Team

Get one team's full record by its team ID: slug, name, creation date, and the requesting user's membership.

Vercel: Get Webhook

Get one webhook's configuration by ID: URL, events, and project scope (never the signing secret).

Vercel: List Aliases

List the aliases (custom URLs pointing at deployments) on the account, optionally filtered to one project or domain.

Vercel: List Auth Tokens

List the metadata of all access tokens on the authenticated account: name, creation time, expiry, and scopes. Token VALUES are never returned (they are shown once at creation only), so this is a safe audit read.

Vercel: List DNS Records

List the DNS records of a domain that uses Vercel DNS, with each record's id, type, name, value, and TTL.

Vercel: List Deployment Checks

List the checks registered on a deployment by integrations (end-to-end tests, Lighthouse-style audits) with status, conclusion, and metrics. Read-only: creating checks requires an integration installation, not an access token.

Vercel: List Deployment Events

Fetch a deployment's build log events (stdout, stderr, and lifecycle messages) as JSON, for build-failure diagnostics. Returns a bounded page; live following is not supported on the canvas.

Vercel: List Deployment Files

List the source file tree of a deployment as nested directory/file entries with file IDs. Works for deployments created with uploaded sources; git-built deployments may return 404 because their sources live in the repository.

Vercel: List Deployments

List deployments across the account or filtered to one project, environment, state, or branch, newest first. Each item carries the deployment uid needed by the other deployment nodes.

Vercel: List Domains

List the domains registered to the account or team, with nameserver status, expiry, and verification state.

Vercel: List Environment Variables

List a project's environment variables with key, target environments, type, and metadata. Values come back encrypted unless decrypt=true; variables of type sensitive never return their value at all.

Vercel: List Global Config Items

Read all key-value items in a Global Config: feature flags, settings, allowlists. Reads are metered on paid usage but free-tier Hobby includes 100K reads per month.

Vercel: List Global Configs

List the account's Global Configs (the key-value stores formerly named Edge Config) with id, slug, size, and item count.

Vercel: List Project Domains

List the domains attached to a project with their git branch, redirect target, and verification status.

Vercel: List Projects

List projects in the personal account or a team, newest-updated first, with framework, git link, and latest deployments. Page with the from field using data.pagination.next from the previous response.

Vercel: List Team Members

List the members of a team with their role, email, username, and join date. Supports searching by name or email and filtering by role.

Vercel: List Teams

List every team the token's user belongs to, with each team's id, slug, name, and the user's role. The team id here is what the teamId field on the other Vercel nodes expects.

Vercel: List Webhooks

List the account's webhooks with their target URL, subscribed events, and project scope. Signing secrets are not included (they are returned once at creation).

Action nodes 23

Vercel: Add Domain

Register an EXISTING domain you already own with the Vercel platform (method add), so it can be attached to projects and managed via Vercel DNS. This never buys a domain and incurs no charge; purchase and transfer-in are deliberately not on the canvas.

Vercel: Add Domain to Project

Attach a domain to a project, optionally scoped to a git branch or set up as a redirect to another of the project's domains. If the domain's DNS is not pointed at Vercel yet, the response includes verification instructions and verified stays false until DNS checks pass.

Vercel: Assign Alias to Deployment

Point an alias hostname at a specific deployment. If the alias already exists it is atomically switched over (the manual blue-green / rollback move); assigning it back to the previous deployment reverses it. The hostname must be a domain on the account or a *.vercel.app name you control.

Vercel: Cancel Deployment

Cancel a deployment that is still queued or building. The deployment ends in state CANCELED; production keeps serving whatever was live before. A finished deployment cannot be canceled (redeploy or promote another instead).

Vercel: Create DNS Record

Add a DNS record to a domain on Vercel DNS: A, AAAA, ALIAS, CAA, CNAME, HTTPS, MX, SRV, TXT, or NS. The API validates the value against the type (an A record needs an IPv4 address, and so on) and rejects fields that do not belong to the chosen type.

Vercel: Create Deployment

Create a deployment from existing sources: redeploy a previous deployment (deploymentId) or deploy a commit from the project's linked git repository (gitSource). Consumes build minutes and counts against the deployments-per-day limit (100/day on Hobby); target=production ships to the production URL once ready. From-scratch file uploads are not supported on the canvas.

Vercel: Create Environment Variable

Add an environment variable to a project for one or more target environments. Existing deployments are unaffected; the new value applies from the next deployment. Set upsert=true to overwrite an existing variable with the same key and target instead of failing.

Vercel: Create Project

Create a new project, optionally linked to a git repository and pre-seeded with environment variables. Creating a project does not deploy anything by itself; a linked repository deploys on its next push.

Vercel: Create Webhook

Create a webhook that POSTs platform events (deployment created/succeeded/error, project created, domain created, and more) to your URL. The response includes the signing secret EXACTLY ONCE: store it immediately, it cannot be fetched again.

Vercel: Delete Alias

Delete an alias by ID or hostname. Traffic to that hostname stops resolving to the deployment immediately; re-assigning the same hostname restores it. Mind that deleting a live production alias takes that URL offline until reassigned.

Vercel: Delete DNS Record

Delete a DNS record from a domain on Vercel DNS. Whatever the record pointed at (mail routing, a subdomain, a verification TXT) stops resolving as caches expire, and the API has no undo: recreate the record to restore it.

Vercel: Delete Deployment

Permanently delete a deployment by ID (or by URL via the url field, which then takes precedence). Its unique URL stops serving and its build logs go with it; there is no undelete on the API. Deleting the current production deployment takes the production site down until another is promoted.

Vercel: Delete Domain

Remove a domain from the Vercel account entirely. Its Vercel-DNS records and project attachments stop working immediately and the records are not recoverable (re-adding the domain starts from scratch). Ownership at the registrar is unaffected.

Vercel: Delete Environment Variable

Delete an environment variable by ID. The stored value is gone for good (and a sensitive-type value was never readable), so capture it first if you might need it back. Existing deployments keep running with the value they were built with.

Vercel: Delete Project

Permanently delete a project by ID or name, including its deployments, environment variables, and domain attachments. There is no undo on the API: the project and its deployment history are gone. Returns 204 with an empty body on success.

Vercel: Delete Webhook

Delete a webhook by ID; deliveries stop immediately. Recreating it later issues a NEW signing secret, so the receiver's verification key must be updated too. Returns 204 with an empty body.

Vercel: Promote Deployment to Production

Point production traffic at an existing successful deployment (staged promote / instant rollback pattern). Production domains switch to this deployment without a rebuild; promoting the previous deployment again reverses it. Returns 201 with an empty body; the switch itself completes asynchronously.

Vercel: Remove Domain from Project

Detach a domain from a project. The domain itself stays on the account (this is not domain deletion) and can be re-attached, but traffic to it stops resolving to this project immediately.

Vercel: Update DNS Record

Edit an existing DNS record by its record ID. Only the fields you fill are sent. DNS caches mean changes take up to the old TTL to propagate.

Vercel: Update Environment Variable

Edit an existing environment variable by ID. Only the fields you fill are sent, so an update can change just the value while keeping key, type, and targets. Applies from the next deployment.

Vercel: Update Global Config Items

Batch upsert or delete key-value items in a Global Config (flip feature flags, update settings). Changes propagate to reads within seconds. Writes are metered and rate-limited: Hobby includes 100 writes per month (then 250/month hard cap), paid plans 100 writes per hour.

Vercel: Update Project

Update a project's settings. Only the fields you fill are sent, so untouched settings keep their values. Build-setting changes apply from the next deployment onward.

Vercel: Verify Project Domain

Trigger a verification check for a project domain that is pending verification (after adding the TXT record or pointing DNS). Returns the domain with its updated verified flag and any still-missing verification steps.

Connecting Vercel takes one credential

Vercel issues personal access tokens from the dashboard under Settings, on the Tokens page. A token is one opaque value sent as a standard Bearer authorization header, and the connector builds that header for you, so the credential form is a single field holding the token. At creation you pick the token's scope (your full account, meaning your personal account plus every team you belong to, or a single team, or a single project) and an optional expiration. The value is shown exactly once: Vercel cannot display it again later. One quirk worth knowing before you debug anything: a bad or missing token gets a 403 with code forbidden, not the 401 most APIs return.

1

In the Vercel dashboard, open Settings and go to the Tokens page. Create a token, name it for the automation it will drive, and choose its scope and expiration. A token scoped to a single team or project cannot reach anything outside that scope, so match the scope to where the work lives; a Full Account token reaches your personal account and every team you belong to.

2

Copy the token immediately. It is displayed once at creation and cannot be retrieved again; losing it means creating a new one.

3

In Mattering Automations, open Connectors, click Add Connector, choose Vercel, and paste the token into the single credential field. Do not paste the word Bearer or a header name; the connector adds the scheme itself.

4

Click Test Connection. Mattering calls Vercel's user endpoint, the same read as Vercel: Get Current User: it is free, takes no parameters, identifies the account the token belongs to, and echoes no secret material. Then all 50 Vercel nodes appear in the canvas palette. If you work in a team, run Vercel: List Teams first, because its team id is what the teamId field on the other nodes expects.

Common uses for the Vercel MCP

Deploy on approval instead of on push

Vercel: Create Deployment ships a release from the project's linked git repository or redeploys a previous deployment by id, so a deploy can wait for a human: an approval task in Mattering Productivity moves, the workflow fires, and target production sends it to the production URL once the build is ready. Vercel: Get Deployment polls the build state until readyState reaches READY or ERROR, which is the gate every step after the deploy should branch on.

Instant rollback and blue-green switches

Vercel: Promote Deployment to Production points production traffic at any existing successful deployment without a rebuild, which makes rollback a single node: save the current deployment's uid before you ship, and promote it back if the new build misbehaves. Vercel: Assign Alias to Deployment is the finer-grained version of the same move, atomically switching one hostname between deployments, and re-assigning the previous deployment reverses it.

Rotate environment variables everywhere at once

Vercel: Create Environment Variable with upsert set, and Vercel: Update Environment Variable for edits by id, turn a key rotation into a loop over projects instead of an afternoon of clicking. Two honest caveats the nodes state themselves: changes apply from the next deployment, not to what is already running, so chain a redeploy after the write; and sensitive-type values are write-only by design, so nothing can read them back later, including you.

Feature flags and settings in Global Config

Vercel: Update Global Config Items batch-upserts or deletes key-value items in a Global Config (the store formerly named Edge Config), and changes propagate to reads within seconds, which makes it the kill switch surface: an incident workflow can flip a flag off without a deploy. Vercel: List Global Config Items reads the current state first so the write changes exactly what you meant. Writes are metered, so schedule them rather than looping them.

Domain onboarding end to end

Vercel: Add Domain registers a domain you already own with the platform, Vercel: Add Domain to Project attaches it, Vercel: Create DNS Record fills in the records if the domain uses Vercel DNS, and Vercel: Verify Project Domain retriggers verification once DNS is pointed. When a domain will not verify, Vercel: Get Domain Configuration is the diagnostic, reporting whether DNS is misconfigured and which nameservers are actually in use. None of this buys anything: purchase and transfer are deliberately not on the canvas.

Build failure triage that opens a ticket, not a tab

Vercel: List Deployments filtered to state ERROR finds broken builds on a schedule, Vercel: List Deployment Events pulls the build log as JSON for the failing one, and the same workflow can open a task in Mattering Productivity with the log attached, or post to your chat connector. Vercel: List Deployment Checks adds the integration test and audit results where you run them, and Vercel: Cancel Deployment clears a stuck queued build while production keeps serving whatever was live.

Example: A production deploy that rolls itself back

Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.

1

Trigger: an approval task moving to Done in Mattering Productivity, or a schedule for a nightly release window.

2

Vercel: List Deployments filtered to the project's READY production deployments records the current deployment's uid as the rollback target before anything ships.

3

Vercel: Create Deployment deploys the linked repository's branch with target production. On the Hobby plan this counts against the 100 deployments per day limit.

4

Vercel: Get Deployment polls the new deployment until readyState is READY or ERROR.

5

A condition branches on the result. On ERROR: Vercel: List Deployment Events fetches the build log, Vercel: Promote Deployment to Production points production back at the saved uid, and a task opens in Mattering Productivity with the log attached.

6

On READY, a notification with the deployment URL closes the loop, and the workflow stores the new uid as the next run's rollback target.

Vercel MCP questions, answered

What Vercel operations are supported?

50 nodes: identity and token auditing (current user, token metadata), teams (list, get, members, read-only), projects (list, get, create, update, delete), environment variables (list, get decrypted, create, update, delete), project domains (list, add, remove, verify), deployments (list, get, create from git or redeploy, cancel, delete, promote to production, build log events, source files, integration checks), account domains (list, get, configuration diagnostic, add, delete, registrar availability check), Vercel DNS records (list, create, update, delete), aliases (list, get, assign, delete), Global Config (list configs, get, read items, batch update items), and webhook management (list, get, create, delete). Global Config is the store formerly named Edge Config; the current API paths use global-config while responses still carry edgeConfigId, and the nodes handle that. Deliberately not shipped: registrar purchases and transfers, from-scratch file-upload deployments, log drains, firewall configuration, the marketplace and integrations surface, and check creation and management, which belongs to CI integrations rather than workflow automation.

Vercel runs its own official MCP server. Why use this one?

Both are real, and we are not going to pretend otherwise. Vercel operates an official remote MCP server at mcp.vercel.com with OAuth sign-in, and its tools search Vercel's documentation, manage projects and deployments, analyze deployment logs, and query Web Analytics; it supports Claude, ChatGPT, Cursor, and other reviewed clients. If all you want is an assistant talking to Vercel on its own, that is a good answer. This connector solves a different problem: the nodes live on one canvas with every other connector in Mattering, so a single scheduled workflow can watch builds, roll production back, open a task in your project tracker, and post to chat, with shared run history and a human approval step in the middle. It also covers surfaces the workflow angle needs, such as DNS records, aliases, environment variable writes, Global Config items, and webhook management. Placement and the workflow surface are the reasons to pick it.

Does this work with Claude, ChatGPT, or other AI assistants?

Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively. The 27 read nodes are the safest surface to hand an agent, since listing deployments, reading build logs, and checking domain configuration change nothing; keep the five delete nodes and the production traffic moves behind an approval step rather than free agent access.

What credential does it need?

One Vercel personal access token, created in the dashboard under Settings on the Tokens page and sent as a standard Bearer authorization header, which the connector builds for you. The token's scope is chosen at creation: your full account (your personal account plus every team you belong to), a single team, or a single project. The value is shown exactly once and cannot be retrieved again. Two things to know when debugging: Vercel returns 403 with code forbidden for a bad token, not 401, and a token scoped to the wrong place is the first thing to check when a request is denied, because a team-scoped or project-scoped token cannot reach anything outside its scope.

Can it actually deploy my site?

Yes, in the two shapes automations actually use: Vercel: Create Deployment redeploys a previous deployment by id, or deploys a commit from the project's linked git repository, and target production ships it to the production URL once the build succeeds. What it does not do is create a deployment from raw uploaded files, because the canvas has no way to produce a file tree upload; that shape stays in the CLI and git integrations where it belongs. Deploys consume build minutes and count against Vercel's deployment limits, which on the Hobby plan are 100 per day.

What are the rate limits?

Vercel publishes a per-action rate limit table in its limits documentation rather than one global number. The ones most likely to matter here: creating deployments is limited to 100 per day and 100 per hour on Hobby and 6000 per day on Pro; environment variable creates and updates to 120 per minute; DNS record creates and updates to 50 per minute; alias creation to 120 per 10 minutes; and Global Config writes are metered monthly on Hobby (100 included) and 100 per hour on paid plans. Exceeding a fixed limit returns 429 with a rate_limited error, and some newer endpoints use ramping dynamic quotas instead of fixed windows, which return rate_limit_exceeded. Reads are far looser (deployment listing alone allows 1000 per minute), so polling and reporting workflows have room.

Does it work on Vercel's free Hobby plan?

Yes, with an honest caveat about what Hobby is for. Access tokens are an account feature, so a Hobby account can create one and drive every node, and the reads cost nothing. But Vercel's fair use guidelines restrict the Hobby plan to personal, non-commercial use, so it is the right place to evaluate the connector and automate a personal project, not to run production automations for a business or a client; that work belongs on a paid Vercel plan. Hobby also carries the tightest operational limits on this surface, including 100 deployments per day and 100 Global Config writes per month included.

Which nodes are destructive, and how do I keep an agent from breaking production?

Exactly five nodes permanently destroy data, and each says so in its description: Vercel: Delete Project takes the project's deployment history and configuration with it, Vercel: Delete Deployment removes a deployment and its build logs with no undelete, Vercel: Delete Domain drops the domain's DNS records unrecoverably (registrar ownership is unaffected), Vercel: Delete DNS Record has no undo beyond recreating the record, and Vercel: Delete Environment Variable discards the stored value for good. The traffic moves are reversible: Vercel: Promote Deployment to Production and Vercel: Assign Alias to Deployment both undo by pointing back at the previous deployment, and Vercel: Cancel Deployment never touches what is currently serving. The practical setup: give agents the read nodes freely, put the five deletes and anything with target production behind a human approval step, and keep destructive automations pointed at a throwaway project while you build them.

50 nodes waiting on the canvas

Put Vercel to work inside your workspace

Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.

All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Vercel is a product of its respective owner; Mattering is an independent platform.

Start Free Explore our Products