Perceptdot Vercel
io.github.perceptdot/vercel
12 toolsSTDIOregistry active
Summary
Connects Claude to Vercel's deployment platform with a focus on tracking AI agent activity and measuring return on investment. You'd reach for this when you want your AI assistant to monitor deployments, analyze performance metrics, or understand how automation impacts your Vercel projects. The ROI measurement angle suggests it tracks which agent actions actually move the needle on your deployments, though the specifics of what data it surfaces aren't detailed in the source. Best suited for teams running AI workflows on Vercel who need visibility into whether their automation is paying off.
Keep your Mac awake while Claude Code and 40+ AI agents run. Sleeps when they're idle.
One time payment $9 →
Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →
Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →
On Capafy, your Skill runs online 24/7 as an agent product, and you get paid every time someone uses it.
Start earning →
Tools
Public tool metadata for what this MCP can expose to an agent.
12 tools
search_vercel_documentationSearch the Vercel documentation. Use this tool to answer any questions about Vercel’s platform, features, and best practices, including: - Core Concepts: Projects, Deployments, Git Integration, Preview Deployments, Environments - Frontend & Frameworks: Next.js, SvelteKit, Nuxt...2 params
Search the Vercel documentation. Use this tool to answer any questions about Vercel’s platform, features, and best practices, including: - Core Concepts: Projects, Deployments, Git Integration, Preview Deployments, Environments - Frontend & Frameworks: Next.js, SvelteKit, Nuxt...
Parameters* required
topicstringTopic to focus the documentation search on (e.g., 'routing', 'data-fetching').
tokensnumberMaximum number of tokens to include in the result. Default is 2500.default: 2500
deploy_to_vercelDeploy the current project to Vercel
Deploy the current project to Vercel
No parameter schema in public metadata yet.
list_projectsList all Vercel projects for a user (with a max of 50). Use this to help discover the Project ID of the project that the user is working on.1 params
List all Vercel projects for a user (with a max of 50). Use this to help discover the Project ID of the project that the user is working on.
Parameters* required
teamIdstringThe team ID to get the deployment events for. Alternatively the team slug can be used.
Team IDs start with "team_".
If you do not know the team ID or slug, it can be found through these mechanism:
- Read the file .vercel/project.json if it exists and extract the orgId
- Use the `list_teams` tool
get_projectGet a specific project in Vercel2 params
Get a specific project in Vercel
Parameters* required
teamIdstringThe team ID to get the deployment events for. Alternatively the team slug can be used.
Team IDs start with "team_".
If you do not know the team ID or slug, it can be found through these mechanism:
- Read the file .vercel/project.json if it exists and extract the orgId
- Use the `list_teams` tool
projectIdstringThe project ID to get the deployment events for. Alternatively the project slug can be used.
Project IDs start with "prj_".
If you do not know the project ID or slug, it can be found through these mechanism:
- Read the file .vercel/project.json if it exists and extract the projectId
- Use the `list_projects` tool
list_deploymentsList all deployments for a project4 params
List all deployments for a project
Parameters* required
sincenumberGet deployments created after this timestamp.
untilnumberGet deployments created before this timestamp.
teamIdstringThe team ID to list deployments for.
projectIdstringThe project ID to list deployments for.
get_deploymentGet a specific deployment by ID or URL.2 params
Get a specific deployment by ID or URL.
Parameters* required
teamIdstringThe team ID to get the deployment events for. Alternatively the team slug can be used.
Team IDs start with "team_".
If you do not know the team ID or slug, it can be found through these mechanism:
- Read the file .vercel/project.json if it exists and extract the orgId
- Use the `list_teams` tool
idOrUrlstringThe unique identifier or hostname of the deployment.
get_deployment_build_logsGet the build logs of a deployment by deployment ID or URL. Can be used to investigate why a deployment failed. It can work as an infinite stream of logs or as a JSON endpoint depending on the input parameters.3 params
Get the build logs of a deployment by deployment ID or URL. Can be used to investigate why a deployment failed. It can work as an infinite stream of logs or as a JSON endpoint depending on the input parameters.
Parameters* required
limitnumberMaximum number of log lines to return. Defaults is 100.default: 100
teamIdstringThe team ID to get the deployment events for. Alternatively the team slug can be used.
Team IDs start with "team_".
If you do not know the team ID or slug, it can be found through these mechanism:
- Read the file .vercel/project.json if it exists and extract the orgId
- Use the `list_teams` tool
idOrUrlstringThe unique identifier or hostname of the deployment.
get_runtime_logsGet runtime logs for a project or deployment. Runtime logs show application output (console.log, errors, etc.) from serverless functions and edge functions during execution. Supports filtering by environment, log level, status code, source, time range, and full-text search. Us...12 params
Get runtime logs for a project or deployment. Runtime logs show application output (console.log, errors, etc.) from serverless functions and edge functions during execution. Supports filtering by environment, log level, status code, source, time range, and full-text search. Us...
Parameters* required
levelarrayFilter by log level(s). Can specify multiple levels.
limitnumberMaximum number of log entries to return. Defaults to 50, max 1000.
querystringFull-text search query to filter logs.
sincestringStart time - ISO format or relative time (e.g., "1h", "30m", "7d"). Defaults to 24 hours ago.
untilstringEnd time - ISO format or relative time. Defaults to now.
sourcearrayFilter by source type(s). Can specify multiple sources.
teamIdstringThe team ID to get the deployment events for. Alternatively the team slug can be used.
Team IDs start with "team_".
If you do not know the team ID or slug, it can be found through these mechanism:
- Read the file .vercel/project.json if it exists and extract the orgId
- Use the `list_teams` tool
projectIdstringThe project ID to get runtime logs for.
requestIdstringFilter by specific request ID.
statusCodestringFilter by HTTP status code (e.g., "500", "4xx").
environmentstringFilter by environment: "production" or "preview".one of
production · previewdeploymentIdstringFilter logs to a specific deployment ID or URL.
get_access_to_vercel_urlCreates a temporary shareable link that bypasses authentication for protected Vercel deployments. When you encounter a Vercel deployment URL (like https://myapp-abc123.vercel.app), you might receive a 403 (Forbidden) error when trying to access it. This tool generates a specia...1 params
Creates a temporary shareable link that bypasses authentication for protected Vercel deployments. When you encounter a Vercel deployment URL (like https://myapp-abc123.vercel.app), you might receive a 403 (Forbidden) error when trying to access it. This tool generates a specia...
Parameters* required
urlstringThe full URL of the Vercel deployment (e.g. "https://myapp.vercel.app").
web_fetch_vercel_urlFetches a Vercel deployment URL and returns the response. This is useful if another web fetch tool returns 401 (Unauthorized) or 403 (Forbidden) for a Vercel URL. Supports accessing deployments protected with Vercel Authentication which the user of this MCP server has access to.1 params
Fetches a Vercel deployment URL and returns the response. This is useful if another web fetch tool returns 401 (Unauthorized) or 403 (Forbidden) for a Vercel URL. Supports accessing deployments protected with Vercel Authentication which the user of this MCP server has access to.
Parameters* required
urlstringThe full URL of the Vercel deployment including the path (e.g. "https://myapp.vercel.app/my-page").
list_teamsList the user's teams. Use this to help discover the Team ID of the teams that the user is part of.
List the user's teams. Use this to help discover the Team ID of the teams that the user is part of.
No parameter schema in public metadata yet.
check_domain_availability_and_priceCheck if domain names are available for purchase and get pricing information1 params
Check if domain names are available for purchase and get pricing information
Parameters* required
namesarrayArray of domain names to check availability for (e.g., ["example.com", "test.org"])
Featured
Keep your Mac awake while Claude Code and 40+ AI agents run. Sleeps when they're idle.
One time payment $9 →Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →On Capafy, your Skill runs online 24/7 as an agent product, and you get paid every time someone uses it.
Start earning →Categories
Registryactive
Package@perceptdot/vercel
TransportSTDIO
UpdatedJun 1, 2026
