Home / Servers / Vercel API / update_microfrontends
Update the microfrontends settings
An MCP tool from the Vercel API server, hosted on mcp.hjlabs.in.
Update the microfrontends settings for a project. [PATCH /v1/projects/{projectId}/microfrontends]
Name on the gateway: vercel_api__update_microfrontends · may change things.
Parameters
| Name | Type | Description |
|---|---|---|
projectId required | string | The unique project identifier |
teamId | string | The Team identifier to perform the request on behalf of. |
slug | string | The Team slug to perform the request on behalf of. |
microfrontendsGroupId | string | The unique group identifier to add this microfrontend to |
enabled | boolean | Enable or disable microfrontends for the project |
isDefaultApp | boolean | Whether the application is the default application for the microfrontends group |
defaultRoute | string | The default route used for screenshots and preview links for the project |
routeObservabilityToThisProject | boolean | Whether observability data should be routed to this project or a root project.… |
doNotRouteWithMicrofrontendsRouting | boolean | Whether domains in this project should route as a microfrontend. Can only be… |
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__update_microfrontends",
"arguments": {
"projectId": "…"
}
}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 update the microfrontends settings tool with projectId set to ….