Summary
Connects to Vercel's platform APIs to manage deployments and monitor logs directly from your MCP client. You get build and runtime application log access without switching to the dashboard, plus deployment management operations. Built by PulseMCP with their focus on minimizing tool chain steps and conversational turns, which means fewer round trips to check deployment status or debug production issues. Reach for this when you're iterating on Vercel projects and want to monitor deploys or investigate errors without context switching. Uses stdio transport and requires Vercel API credentials.
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"])
PulseMCP's MCP Servers
We build reliable servers thoughtfully designed for MCP Client-powered workflows.
Design principles
You can have confidence that any Pulse-branded MCP server was built with these north stars in mind:
- Purpose-built. LLM-powered MCP clients offer uniquely new user interaction patterns that necessitate a different layer of abstraction than the REST API's from a pre-AI era. We thoughtfully scope drawing lines like building a new server, versus incorporating a new feature in another server. Or deciding where one slew of REST API endpoints might be better packaged as a single Tool call. And more.
- Easy set up. Many MCP servers die before ever getting a chance to be used. We offer guides and a frustration-free experience to get going with our MCP servers inside your favorite MCP clients.
- Time savings. By minimizing the number of tool chain steps or conversational turns you need to accomplish a task, our MCP servers will save you (and your agents) time waiting for a task to be completed.
- Inference cost savings. By minimizing the number of tokens you need to consume to a accomplish a task, our MCP servers will save you on your LLM inference bills.
- Reliability. You should have confidence that you can deploy our servers in a production application serving mass market consumers or business clients.
- Future-proof. We sit on the bleeding edge of the MCP specification, working to push the ecosystem forward. As such, you can be sure that if you commit to baking our server into your workflow, it will self-improve over time to take advantage of the latest and greatest MCP features.
Servers Available
Productionized Servers
These are PulseMCP-branded servers that we intend to maintain indefinitely as our own offerings.
The MCP Registry column controls whether the server is published to the official MCP Registry (com.pulsemcp/<server-name>) by the publish-mcp-registry.yml workflow.
| Name | Description | Local Status | Remote Status | MCP Registry | Target Audience | Notes |
|---|---|---|---|---|---|---|
| pulse-fetch | Pull internet resources into context | 0.3.3 | Not Started | Yes | Agent-building frameworks (e.g. fast-agent, Mastra, PydanticAI) and MCP clients without built-in fetch | Supports Firecrawl and BrightData integrations; HTML noise stripping; Resource caching; LLM extraction |
| pulse-subregistry | Browse the PulseMCP Sub-Registry | 0.0.8 | Not Started | Yes | Developers discovering MCP servers from the PulseMCP Sub-Registry | Search and pagination; Version selection; Integrates with PulseMCP Sub-Registry API |
| image-diff | Programmatic image comparison | 0.1.3 | Not Started | Yes | Developers comparing design mocks against UI implementations | Pixel-level diff with clustering; Heatmap visualization; Anti-aliasing detection; Auto-alignment for different-sized images |
| svg-tracer | Bitmap-to-SVG vector tracing | 0.1.3 | Not Started | Yes | Developers converting bitmap images to SVG vector graphics | Supports PNG, JPG, WebP, BMP, GIF, TIFF; Alpha channel preprocessing; Target size scaling; Customizable tracing parameters |
Experimental Servers
These are high-quality servers that we may discontinue if the official provider creates and maintains a better MCP server.
| Name | Description | Local Status | Remote Status | MCP Registry | Target Audience | Notes |
|---|---|---|---|---|---|---|
| agent-orchestrator | Agent parallelization system for agentic coding and ops | 0.8.8 | Not Started | No | PulseMCP team for agent orchestration | Requires AGENT_ORCHESTRATOR_BASE_URL and API_KEY; Internal use only |
| appsignal | AppSignal application performance monitoring and error tracking | 0.5.4 | Not Started | Yes | Developers using AppSignal for application monitoring | Requires AppSignal API key; NOT officially affiliated with AppSignal |
| claude-code-agent | Claude Code Agent MCP Server for managing Claude Code CLI sessions | 0.0.8 | Not Started | No | Developers building AI-powered automation workflows | Requires Claude Code CLI installed locally |
| dynamodb | AWS DynamoDB table and item operations with fine-grained access | 0.2.7 | Not Started | Yes | Developers using AWS DynamoDB | Requires AWS credentials; Fine-grained tool access control |
| remote-filesystem | Remote filesystem operations on cloud storage (GCS) | 0.1.5 | Not Started | Yes | Developers needing cloud storage integration | Requires GCS credentials; Full CRUD operations; Published as remote-filesystem-mcp-server |
| s3 | AWS S3 bucket and object management | 0.0.5 | Not Started | Yes | Developers needing S3 storage integration | Requires AWS credentials; Fine-grained tool access control; Published as s3-aws-mcp-server |
| fetchpet | Fetch Pet insurance claims management | 0.1.8 | Not Started | Yes | Pet owners with Fetch Pet insurance | Requires Fetch Pet username and password; NOT officially affiliated with Fetch Pet |
| fly-io | Fly.io cloud platform app and machine management | 0.1.7 | Not Started | Yes | Developers deploying applications to Fly.io | Requires FLY_IO_API_TOKEN; NOT officially affiliated with Fly.io |
| gcs | Google Cloud Storage bucket and object management | 0.1.14 | Not Started | Yes | Developers needing GCS storage integration | Requires GCS credentials; Fine-grained tool access control; Published as gcs-google-mcp-server |
| google-flights | Google Flights search, date grids, and airport lookup | 0.2.5 | Not Started | Yes | Users searching for flights via Google Flights | No API key required; Uses protobuf-encoded HTTP requests; Published as google-flights-mcp-server; NOT officially affiliated with Google |
| gmail | Gmail integration for email access | 0.4.11 | Not Started | Yes | Gmail users (personal or Google Workspace) | Supports OAuth2 (personal) and service account (Workspace); NOT officially affiliated with Google |
| google-calendar | Google Calendar Workspace integration for calendar management | 0.0.13 | Not Started | Yes | Google Workspace organizations needing Calendar integration | Requires service account with domain-wide delegation; NOT officially affiliated with Google |
| good-eggs | Good Eggs grocery shopping automation | 0.1.10 | Not Started | Yes | Users of Good Eggs grocery delivery service | Requires Good Eggs username and password; NOT officially affiliated with Good Eggs |
| onepassword | 1Password credential and secrets management via CLI | 0.5.4 | Not Started | Yes | Developers using 1Password for secrets management | Requires 1Password CLI and service account token; NOT officially affiliated with 1Password |
| hatchbox | Hatchbox Rails hosting platform management | 0.1.3 | Not Started | Yes | Rails developers using Hatchbox for hosting | Requires Hatchbox API key and deploy key |
| langfuse | Readonly Langfuse LLM trace and observation analysis | 0.1.3 | Not Started | Yes | Developers using Langfuse for LLM observability | Requires Langfuse API keys; Published as langfuse-observability-mcp-server; NOT officially affiliated with Langfuse |
| monarch-money | Monarch Money personal finance management (read + mutate) | 0.0.9 | Not Started | Yes | Monarch Money users tracking accounts, transactions, net worth, and budgets | Requires Monarch credentials; tool-group filtering for write protection; NOT officially affiliated with Monarch Money |
| playwright-stealth | Browser automation with Playwright and optional stealth mode | 0.2.3 | Not Started | Yes | Developers needing browser automation with anti-bot bypass | Optional stealth mode via STEALTH_MODE env var |
| pointsyeah | Award flight search across 20+ airline loyalty programs | 0.2.9 | Not Started | Yes | Travelers optimizing credit card points for flights | Optional PointsYeah refresh token (can be set at runtime); NOT officially affiliated with PointsYeah |
| proctor | Proctor exam runner for testing MCP servers | 0.1.9 | Not Started | Yes | PulseMCP team for MCP server testing | Requires PROCTOR_API_KEY; Internal use only |
| pulsemcp-cms-admin | Internal API for managing PulseMCP newsletter content | 0.10.4 | Not Started | No | PulseMCP team for content management | Requires PULSEMCP_ADMIN_API_KEY; Internal use only |
| serpapi-hotels | Google Hotels search, details, and reviews via SerpAPI | 0.0.4 | Not Started | Yes | Users searching for hotels via Google Hotels | Requires SerpAPI key; NOT officially affiliated with SerpAPI or Google |
| slack | Slack workspace messaging and collaboration integration | 0.0.7 | Not Started | Yes | Teams using Slack for team communication | Requires Slack Bot Token; NOT officially affiliated with Slack |
| ssh | SSH remote server management with agent authentication | 0.1.5 | Not Started | Yes | Developers needing SSH access to remote servers | Supports SSH agent for passphrase-protected keys |
| twist | Twist team messaging and collaboration platform integration | 0.2.3 | Not Started | Yes | Teams using Twist for asynchronous communication | Requires Twist API bearer token and workspace ID |
| vercel | Vercel deployment management and runtime log retrieval | 0.1.3 | Not Started | Yes | Developers using Vercel for deployment and hosting | Requires Vercel API token; Published as vercel-platform-mcp-server; NOT officially affiliated with Vercel |
| google-docs | MCP server for Google Docs integration with OAuth2 and service account support | 0.1.4 | Not Started | Yes | TBD | TBD |
Contributing
See CONTRIBUTING.md.
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 →Configuration
VERCEL_TOKEN*secretVercel API token for authentication.
VERCEL_TEAM_IDTeam ID for team-scoped operations.
VERCEL_TEAM_SLUGTeam URL slug for team-scoped operations.
VERCEL_ENABLED_TOOLGROUPSComma-separated list of tool groups to enable (readonly, readwrite).
Categories
Registryactive
Packagevercel-platform-mcp-server
TransportSTDIO
AuthRequired
UpdatedMay 18, 2026
