Read project summaries and deployment metadata through the official Vercel REST API. Uses your scoped access token and an optional connection-bound team ID. Leave team ID blank only for personal-account access. Model input cannot change the team. This subset does not deploy code, trigger builds, change domains or read environment-variable values. One explicit request/page per invocation, without retries or automatic pagination.
What you can do (3)
What you can do
Available commands: 3 (3 read, 0 write). Enable only the commands your application needs.
| Command | Effect |
|---|---|
List accessible projects — vercel.projects.list |
Read |
Read project summary — vercel.projects.get |
Read |
List deployment metadata — vercel.deployments.list |
Read |
Connect and use
Open the integration's connection form to check the available credential source. The source has not been resolved for this documentation export. The instructions below apply when using your own provider account.
Get your provider credentials
Follow these steps for Vercel, then enter the issued values in the connection form below.
- Open Vercel Account Settings → Tokens and create an access token with an expiry and the narrowest appropriate scope. Enter it in Vercel access token. For a team, copy the Team ID from that team's General Settings into Vercel team ID; leave this field blank only for personal-account access. Save the selected read commands and create a scoped Tooluse.net API key for your client. This connection returns project and deployment summaries and excludes environment-variable values and security configuration.
Where to enter credentials
In the integration page, sign in, choose your workspace and open Connect. If a Credentials choice is shown, select Use my credentials. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.
| Connection field | Requirement |
|---|---|
| Vercel access token | Required |
| Vercel team ID (blank for personal account) | Optional |
Open API keys and create a Tooluse.net key for the enabled commands.
Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.
Configure Claude Code, Codex or Cursor once
Permissions and results
If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net's existing permissions. Disabling a connection or revoking a key immediately prevents new calls.
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Your connection's daily allowance and key permissions also apply. Adding a connection does not make a provider request.
Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.
Call from your client
Use the shared MCP configuration. Refresh your client's tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.
Configure Claude Code, Codex or Cursor once
Discover your enabled tools
List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.
curl 'https://api.tooluse.net/v1/tools' \
-H "Authorization: Bearer $TOOLUSE_API_KEY"
Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.
HTTP call
curl 'https://api.tooluse.net/v1/tool-calls' \
-H "Authorization: Bearer $TOOLUSE_API_KEY" \
-H 'Content-Type: application/json' \
-H 'Idempotency-Key: replace-with-a-new-call-id' \
--data '{
"type": "tool_use",
"id": "toolu_example",
"name": "svc_FROM_YOUR_TOOL_LIST",
"input": {
"query": {
"limit": 20
}
}
}'
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Commands
List accessible projects — vercel.projects.list
Read one page of project metadata for the personal account or team bound to this connection. Use the response continuation value explicitly; this does not deploy code or read environment-variable values.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
query |
object | Optional | additionalProperties: false |
|
query.limit |
integer | Optional | Projects on this page | minimum: 1; maximum: 100 |
query.from |
string | Optional | Copy the continuation token from the preceding project response. | minLength: 1; maxLength: 1000 |
Full JSON Schema
Example input
{
"query": {
"limit": 20
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
Read project summary — vercel.projects.get
Read one project summary by ID or name within the connection team. Returns identity, framework, Node.js version and timestamps when available. Environment variables, security configuration and embedded deployment settings are excluded.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
path |
object | Required | additionalProperties: false |
|
path.idOrName |
string | Required | For example prj_... or the exact project name. | minLength: 1; maxLength: 100; pattern: "^[A-Za-z0-9_-]{1,100}$" |
Full JSON Schema
Example input
{
"path": {
"idOrName": "example-project"
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
List deployment metadata — vercel.deployments.list
Read one page of deployment status and metadata, optionally filtered to a project. No deployment, redeployment, build trigger, log streaming or deletion is performed.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
query |
object | Optional | additionalProperties: false |
|
query.limit |
integer | Optional | Deployments on this page | minimum: 1; maximum: 100 |
query.projectId |
string | Optional | Optional project ID within the connection team. | minLength: 1; maxLength: 100; pattern: "^[A-Za-z0-9_-]{1,100}$" |
query.until |
integer | Optional | Use pagination.next from the preceding response, in milliseconds since epoch. | minimum: 0; maximum: 9007199254740991 |
Full JSON Schema
Example input
{
"query": {
"limit": 20,
"projectId": "prj_example"
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
Errors
Check the key's expiry, revocation, workspace and allowed operations.
Reuse the same idempotency key only for the same request.
The connection or provider limit has been reached. Check the receipt before retrying.
Test the connection
Open the integration's commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client's tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.