Tools
Vercel MCP tools let your AI assistant work with your projects, deployments, logs, and other Vercel resources. Describe what you want to do, and your assistant selects the tools and supplies their parameters.
Before using tools that access your Vercel resources:
- Connect your AI client to Vercel MCP.
- Complete the sign-in flow in your browser with the Vercel account you want to use.
- Authorize your AI client and grant access to the teams you want it to work with.
Adding the server to your client does not complete authorization. Your assistant needs access to the team that owns a project before it can work with that project's deployments or logs. Your existing Vercel permissions still apply.
Ask your assistant to list your teams and projects to check its access. If a team is missing, check that you're signed in to the right account and have granted the connection access to that team.
Your connection's tool list shows the tools you can call and their current parameters. This reference covers 217 catalog tools and 30 workflow or widget tools. Availability depends on server configuration, client support, and team or project scope. Some connections expose a smaller workflow tool list. Tools with the same name can have different parameters on those connections. Follow the schema returned by your connection.
A listed tool still requires the relevant OAuth grant and Vercel permissions. Tools available in one AI client might not be available in another. This reference does not guarantee that every listed tool has approval for every client.
The MCP catalog excludes endpoints that require unsupported credentials or permissions. It does not create AI Gateway API keys, exchange SSO tokens, import KMS private keys, or sign KMS messages or tokens. Use the relevant Vercel dashboard or CLI workflow when MCP does not expose the action.
MCP and CLI use separate authentication. Keep the same team, project, and resource when switching. After an uncertain write, inspect the resource before retrying. A successful CLI request does not prove that your MCP OAuth connection has the same access.
Start with these tools to find your resources, inspect deployments, and troubleshoot errors:
| Tool | What you can do |
|---|---|
list_deployments | List deployments for a project. |
get_deployment | Inspect a deployment's status and details. |
web_fetch_vercel_url | Fetch content from a deployment URL, including protected deployments you can access. |
get_runtime_logs | Read and filter runtime logs for a project or deployment. |
list_projects | Find projects in a team. |
list_teams | Find the teams you can access. |
get_project | Inspect a project's configuration and details. |
get_runtime_errors | Investigate grouped runtime errors and affected routes. |
For example, ask: "Find my project's latest deployment and check its runtime errors." Your assistant can use several tools to complete the request. Include the team and project name so it can find the right resources.
Browse the categories below, or expand a category in the sidebar to find a tool.
Was this helpful?