npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@framers/agentos-ext-cloud-vercel

v0.1.5

Published

Vercel cloud deployment extension — deploy projects, manage domains, and configure environment variables via the Vercel REST API.

Readme

Vercel cloud

This pack gives an agent tools to deploy projects from Git repositories, list projects, check deployment status, manage custom domains, and set or list environment variables through the Vercel REST API.

Installation

npm install @framers/agentos-ext-cloud-vercel

Peer dependency: @framers/agentos >=0.10.40.

Usage

import { AgentOS } from '@framers/agentos';

const agentos = await AgentOS.create({
  extensionManifest: {
    packs: [
      {
        package: '@framers/agentos-ext-cloud-vercel',
        options: {
          token: process.env.VERCEL_TOKEN,
          teamId: process.env.VERCEL_TEAM_ID,
        },
      },
    ],
  },
});

Configuration

| Option | Secret id | Environment variable | Required | Default | | --- | --- | --- | --- | --- | | token | vercel.token | VERCEL_TOKEN | Yes | Empty string | | teamId | vercel.teamId | VERCEL_TEAM_ID | No | undefined, personal account scope | | secrets | vercel.token, vercel.teamId | None | No | Context secrets, then an empty object |

Credentials resolve from the corresponding option, the selected secret map, then the environment variable. options.secrets takes precedence over context secrets. A supplied teamId is appended to API requests as a query parameter.

Tools

| Tool | What it does | | --- | --- | | vercelDeploy | Deploys a project from a Git repository URL and creates the project if it does not exist. | | vercelListProjects | Lists account projects with framework, linked Git repository, and latest deployment status. | | vercelGetDeployment | Checks deployment state, URL, and inspector link by deployment ID. | | vercelConfigureDomain | Adds, removes, or lists project domains and checks DNS configuration. | | vercelSetEnvVars | Sets or lists project environment variables for production, preview, and development targets. |

vercelDeploy

| Parameter | Type | Required | Description | | --- | --- | --- | --- | | gitUrl | string | Yes | Git repository URL. | | projectName | string | No | Vercel project name, derived from the repository name if omitted. | | framework | string | No | Framework preset, such as nextjs, vite, or gatsby; auto-detected if omitted. | | buildCommand | string | No | Build command override. | | outputDirectory | string | No | Output directory override, such as dist, .next, or build. | | envVars | object | No | Project environment variables as key-value pairs. | | target | string | No | Deployment target: production or preview; schema default: production. |

vercelListProjects

| Parameter | Type | Required | Description | | --- | --- | --- | --- | | limit | number | No | Maximum number of projects to return. |

vercelGetDeployment

| Parameter | Type | Required | Description | | --- | --- | --- | --- | | deploymentId | string | Yes | Deployment ID or URL to check. |

vercelConfigureDomain

| Parameter | Type | Required | Description | | --- | --- | --- | --- | | projectId | string | Yes | Vercel project ID or name. | | domain | string | Yes | Custom domain, such as example.com or www.example.com. | | action | string | No | add, remove, list, or check; default: add. | | gitBranch | string | No | Git branch to link the domain to. |

vercelSetEnvVars

| Parameter | Type | Required | Description | | --- | --- | --- | --- | | projectId | string | Yes | Vercel project ID or name. | | vars | object | No | Key-value pairs of environment variables to set. | | action | string | No | set or list; default: set. | | target | array of string | No | Variable targets: production, preview, and development; defaults to all listed targets. |

Notes

Activation requires a Vercel API token. It fails if the token is missing or the user-info authentication request fails.

The Git URL parser accepts GitHub, GitLab, and Bitbucket URLs. Deployment reuses a project found by name or attempts to create it when lookup fails. Repository, framework, and build settings are passed when creating a project. Deployment returns its state without waiting for completion; use vercelGetDeployment to check it.

The vercelDeploy schema exposes target, but execution does not forward it. This tool triggers a production deployment even when preview is supplied.

Deployment, project creation, domain addition or removal, and environment variable writes modify remote resources. Domain configuration returns DNS instructions without writing DNS records. After adding a domain, failure to fetch its DNS configuration is ignored.

Setting environment variables requires a nonempty vars object. Writes use encrypted as the variable type and try to patch an existing variable when the API returns ENV_ALREADY_EXISTS with a variable ID. Listing returns the API value or (encrypted) if no value is provided.

Domain removal does not check the HTTP response status. Environment variable writes do not throw for unhandled HTTP errors or failed patch responses, so a successful tool result does not confirm those changes took effect.

License

Apache-2.0