Home / Servers / Vercel API / get_named_sandbox
Get a named sandbox
An MCP tool from the Vercel API server, hosted on mcp.hjlabs.in.
Get a named sandbox Retrieves a named sandbox by name, including its current sandbox and routes. If the sandbox is stopped and resume is true, a new sandbox will be created from the most recent snapshot. Returns 404 if… [GET /v2/sandboxes/{name}]
Name on the gateway: vercel_api__get_named_sandbox · read-only.
Parameters
| Name | Type | Description |
|---|---|---|
name required | string | Name for the sandbox. Must be unique per project and… |
projectId | string | The project ID or name (required when not using OIDC token). |
resume | boolean | Whether to automatically resume a stopped named sandbox by creating a new… |
teamId | string | The Team identifier to perform the request on behalf of. |
slug | string | The Team slug to perform the request on behalf of. |
How to call it
Through the Smart Gateway, any client can run it by name with call_tool, or let the gateway find it with search_tools:
{
"name": "vercel_api__get_named_sandbox",
"arguments": {
"name": "…"
}
}Or connect the Vercel API server directly, which lists 472 tools including this one:
claude mcp add --transport http hj-vercel-api https://mcp.hjlabs.in/mcp/vercel-api \
--header "Authorization: Bearer YOUR_API_KEY"Try asking
Use the get a named sandbox tool with name set to ….