Vercel Connect now lets developers configure all 100+ service integrations directly from the CLI using `vercel connect create`, eliminating the previous split workflow where some services required jumping to the dashboard to finish setup.
The command pre-populates brand metadata, auth type, and MCP or discovery URL, then prompts for credentials and creates the connector in one pass. After attaching it to a project, `getToken` with the connector's UID issues a short-lived, scoped token from the provider. The token scoping detail is what makes this worth reading in full: it signals Vercel is treating credential exposure as a first-class concern, not an afterthought.
The connectors directory and CLI reference are live now. If your team manages multiple third-party integrations across projects, the shift to a single terminal-based provisioning flow has immediate operational implications.
[READ ORIGINAL →]